| // ==UserScript== | |
| // @name Medium Paywall Bypass (Manual Button + Badge + Fallback + Offline) | |
| // @namespace Violentmonkey Scripts | |
| // @run-at document-start | |
| // @match *://*.medium.com/* | |
| // @match *://medium.com/* | |
| // @match *://*/* | |
| // @grant none | |
| // @version 3.5 | |
| // @inject-into content |
| blueprint: | |
| name: Frigate LLM Notification (v0.5-dev) | |
| author: whag | |
| description: "Basic requirements:<br /> - Home Assistant with an MQTT broker setup. | |
| <br /> - Frigate integration with MQTT setup. <br /> Link: https://github.com/blakeblackshear/frigate-hass-integration | |
| <br /> - LLM Vision integration with provider setup. <br /> Link: https://github.com/valentinfrlch/ha-llmvision | |
| <br /> - Optional Downloader integration. (Ensure the Use Downloader Input is | |
| Set Accordingly) <br /> Link: https://www.home-assistant.io/integrations/downloader/<br | |
| /><br />\nInformation:<br /> - Only suitable for one Frigate camera, use multiple | |
| instances of this automation for multiple cameras if required. <br /> - LLM Vision |
I need help setting up custom agents for Claude Code. Please help me install the agents from this GitHub gist: https://gist.github.com/Danm72/7cdd172f818505b221988916ebdc9371
Here's what needs to be done:
| description | tools | model | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4.1 Do Epic Shit Mode v1 |
|
GPT-4.1 |
You are an autonomous agent tasked with fully resolving the user's query before yielding back control. Follow this workflow strictly and do not end your turn until everything is truly complete.
Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.
Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1
| <div class="container container--mobile"> | |
| <div class="glass-container glass-container--rounded glass-container--large"> | |
| <div class="glass-filter"></div> | |
| <div class="glass-overlay"></div> | |
| <div class="glass-specular"></div> | |
| <div class="glass-content"> | |
| <div class="player"> | |
| <div class="player__thumb"> | |
| <img class="player__img" src="https://images.unsplash.com/photo-1619983081593-e2ba5b543168?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3wzMjM4NDZ8MHwxfHJhbmRvbXx8fHx8fHx8fDE3NDk1NzAwNDV8&ixlib=rb-4.1.0&q=80&w=400" alt=""> | |
| <div class="player__legend"> |
Git and AI agent conversations face the same fundamental challenge: managing branching threads of work that must be merged back together.
The key insight: Think of git as if it only had commit messages, no file changes. This is exactly what AI conversation management needs - a way to branch, merge, and rebase pure conversation history. The vocabulary and mental models from git can illuminate context management for AI agents.
| /** | |
| * My Portable RAG | |
| * $ pnpm add sqlite-vec @ai-sdk/google ai | |
| * SQLite Vector Search + Google AI Embeddings | |
| * | |
| * Required environment variables: | |
| * GOOGLE_GENERATIVE_AI_API_KEY=your-api-key | |
| * | |
| * Usage: | |
| * # Index text content |
