{
 "version": "v7",
 "month": "2026-09",
 "generated": "2026-10-15",
 "count": 167,
 "month_basis": "source date (date added when the source is undated)",
 "usecases": [
  {
   "slug": "claude-plans-codex-executes",
   "url": "https://agentsetups.dev/use-case/claude-plans-codex-executes/",
   "title": "Plan with Claude Code, execute with Codex via MCP",
   "summary": "Claude Code plans and reviews, Codex executes through the Codex MCP, and notes and skills live in Obsidian.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex",
    "Cursor",
    "OpenCode",
    "Antigravity",
    "Command Code"
   ],
   "models": [],
   "tools": [
    "Codex MCP",
    "Obsidian"
   ],
   "prompt": "Goal: Split the work: one agent plans and reviews, another implements.\nSetup: agents used in source: Claude, Codex, Cursor, OpenCode, Antigravity, Command Code; tools/MCPs stated: Codex MCP, Obsidian.\nSteps:\n1. Use Claude Code as the planner. It sends execution to Codex only through the Codex MCP, which Claude manages.\n2. Run the agents in dedicated environments so they keep working when your laptop is closed.\n3. Keep notes and skills in Obsidian so you can switch tools and devices.\n4. Variant: the pilot (Opus 5.5 in Claude Code) plans and assigns tasks to other CLIs, then reviews all the code they write.\n5. Variant: two different models review each change against the same frozen brief; nothing lands until two review rounds come back clean.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Louis-François Bouchard — https://x.com/Whats_AI/status/2100600923689021665",
   "steps": [
    "Use Claude Code as the planner. It sends execution to Codex only through the Codex MCP, which Claude manages.",
    "Run the agents in dedicated environments so they keep working when your laptop is closed.",
    "Keep notes and skills in Obsidian so you can switch tools and devices.",
    "Variant: the pilot (Opus 5.5 in Claude Code) plans and assigns tasks to other CLIs, then reviews all the code they write.",
    "Variant: two different models review each change against the same frozen brief; nothing lands until two review rounds come back clean."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-17",
   "trend_score": 90.1,
   "sources": [
    {
     "author": "Louis-François Bouchard",
     "handle": "@Whats_AI",
     "url": "https://x.com/Whats_AI/status/2100600923689021665",
     "platform": "x",
     "date": "2026-09-17",
     "primary": true
    },
    {
     "author": "Sanchit monga",
     "handle": "@sanchitmonga22",
     "url": "https://x.com/sanchitmonga22/status/2096372075439235580",
     "platform": "x",
     "date": "2026-09-05",
     "primary": false
    },
    {
     "author": "Swapnil Sarkar",
     "handle": "@swapnilskr",
     "url": "https://x.com/swapnilskr/status/2103844926479822852",
     "platform": "x",
     "date": "2026-09-26",
     "primary": false
    },
    {
     "author": "CompilingThings",
     "handle": "@Compilethings",
     "url": "https://x.com/Compilethings/status/2103383637051744279",
     "platform": "x",
     "date": "2026-09-25",
     "primary": false
    }
   ]
  },
  {
   "slug": "grokbot-family-school-email-digest",
   "url": "https://agentsetups.dev/use-case/grokbot-family-school-email-digest/",
   "title": "Have a family bot summarise the kids’ school emails",
   "summary": "@MatthewBerman’s Family Bot reads every school and sports email his kids get and summarises them.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "email"
   ],
   "prompt": "Goal: Stop missing things in the flood of school and sports emails.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: email.\nSteps:\n1. Create a Family Bot in Grok Bot with access to the kids’ school/sports emails.\n2. Have it read every one and summarise it.\n3. Have it put the important items where you will see them.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: The post is a credits giveaway; the use case is the one he describes as his favourite.\nBased on: Matthew Berman — https://x.com/MatthewBerman/status/2098441494478889314 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Create a Family Bot in Grok Bot with access to the kids’ school/sports emails.",
    "Have it read every one and summarise it.",
    "Have it put the important items where you will see them."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-11",
   "trend_score": 89.3,
   "sources": [
    {
     "author": "Matthew Berman",
     "handle": "@MatthewBerman",
     "url": "https://x.com/MatthewBerman/status/2098441494478889314",
     "platform": "x",
     "date": "2026-09-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "long-form-ai-ads-codex",
   "url": "https://agentsetups.dev/use-case/long-form-ai-ads-codex/",
   "title": "Produce 5-minute AI video ads from a Codex pipeline",
   "summary": "Codex starts in the Meta ads library, scripts every scene, drives image and video models plus Suno, all from one CLI.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Codex"
   ],
   "models": [
    "GPT-6 Astra"
   ],
   "tools": [
    "Meta Ads Library",
    "Suno"
   ],
   "prompt": "Goal: Make long-form video ads on autopilot.\nSetup: agents used in source: Codex; tools/MCPs stated: Meta Ads Library, Suno.\nSteps:\n1. Start with research: pull the winning ads in the niche from the Meta ads library.\n2. From that research, write the full script with every scene mapped before anything generates.\n3. Use image models for character and environment sheets, and video models for the sequences.\n4. Generate a soundtrack with Suno.\n5. Control what generates, in what order and with which model from one CLI; output any ratio from 9:16 to 21:9.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Machina — https://x.com/EXM7777/status/2097713112250253528",
   "steps": [
    "Start with research: pull the winning ads in the niche from the Meta ads library.",
    "From that research, write the full script with every scene mapped before anything generates.",
    "Use image models for character and environment sheets, and video models for the sequences.",
    "Generate a soundtrack with Suno.",
    "Control what generates, in what order and with which model from one CLI; output any ratio from 9:16 to 21:9."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-09",
   "trend_score": 85.6,
   "sources": [
    {
     "author": "Machina",
     "handle": "@EXM7777",
     "url": "https://x.com/EXM7777/status/2097713112250253528",
     "platform": "x",
     "date": "2026-09-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "i-have-adhd-skill",
   "url": "https://agentsetups.dev/use-case/i-have-adhd-skill/",
   "title": "Install a skill that stops agents burying the answer",
   "summary": "The i-have-adhd skill makes coding assistants put the action first, number the steps and drop filler.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Make my coding assistant answer action-first.\nSetup: agents used in source: Claude.\nSteps:\n1. Paste into your CLI: “Install the i-have-adhd skill/plugin from https://github.com/ayghri/i-have-adhd, refer to the repo’s AGENTS.md for instructions.”\n2. Expect: action first, numbered steps, no “Hope this helps!”.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: domhudson — https://news.ycombinator.com/item?id=49610631",
   "steps": [
    "Paste into your CLI: “Install the i-have-adhd skill/plugin from https://github.com/ayghri/i-have-adhd, refer to the repo’s AGENTS.md for instructions.”",
    "Expect: action first, numbered steps, no “Hope this helps!”."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-08",
   "trend_score": 85.1,
   "sources": [
    {
     "author": "domhudson",
     "handle": "domhudson",
     "url": "https://news.ycombinator.com/item?id=49610631",
     "platform": "hn",
     "date": "2026-09-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "vibe-coded-photoshop",
   "url": "https://agentsetups.dev/use-case/vibe-coded-photoshop/",
   "title": "Replace a pro app subscription with your own build",
   "summary": "A Codex-built Photoshop alternative reached 20k users after $2,000+ of tokens, driven by user feedback.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Build my own replacement for an expensive desktop app.\nSetup: agents used in source: Codex.\nSteps:\n1. Start with the core features you use.\n2. Feed user feedback from every channel back into the agent.\n3. Keep iterating feature parity.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/AsejereDaDeje — https://www.reddit.com/r/vibecoding/comments/1wpaies/my_vibecoded_photoshop_just_crossed_20k_users/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Start with the core features you use.",
    "Feed user feedback from every channel back into the agent.",
    "Keep iterating feature parity."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 79.3,
   "sources": [
    {
     "author": "/u/AsejereDaDeje",
     "handle": "/u/AsejereDaDeje",
     "url": "https://www.reddit.com/r/vibecoding/comments/1wpaies/my_vibecoded_photoshop_just_crossed_20k_users/",
     "platform": "reddit",
     "date": "2026-09-24",
     "primary": true
    },
    {
     "author": "/u/ai_art_is_art",
     "handle": "/u/ai_art_is_art",
     "url": "https://www.reddit.com/r/vibecoding/comments/1wvz4ua/100_open_source_clean_room_implementations_of_7/",
     "platform": "reddit",
     "date": "2026-10-02",
     "primary": false
    }
   ]
  },
  {
   "slug": "codex-drop-in-renderer",
   "url": "https://agentsetups.dev/use-case/codex-drop-in-renderer/",
   "title": "Have Codex build a drop-in renderer to fix perf",
   "summary": "A Three.js family Halloween project had load and frame-spike issues; Codex built a new renderer as a drop-in.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "three.js"
   ],
   "prompt": "Goal: Fix load times and frame spikes in a three.js project by replacing the renderer.\nSetup: agents used in source: Codex; tools/MCPs stated: three.js.\nSteps:\n1. Design the new renderer yourself.\n2. Ask Codex to build it as a drop-in replacement for the existing one.\n3. Let it work while you do something else.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Simon — https://x.com/iced_coffee_dev/status/2102880675645071652",
   "steps": [
    "Design the new renderer yourself.",
    "Ask Codex to build it as a drop-in replacement for the existing one.",
    "Let it work while you do something else."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 79.2,
   "sources": [
    {
     "author": "Simon",
     "handle": "@iced_coffee_dev",
     "url": "https://x.com/iced_coffee_dev/status/2102880675645071652",
     "platform": "x",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "figma-mcp-to-supabase-crm",
   "url": "https://agentsetups.dev/use-case/figma-mcp-to-supabase-crm/",
   "title": "Turn a Figma CRM design into a working app with MCPs",
   "summary": "The Figma MCP and two skills implement the UI, a human fixes the details, and the Supabase MCP handles the backend.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude"
   ],
   "models": [
    "Fable 5.1"
   ],
   "tools": [
    "Figma MCP",
    "Supabase MCP",
    "Paper MCP"
   ],
   "prompt": "Goal: Build a working app from my Figma design.\nSetup: agents used in source: Claude; tools/MCPs stated: Figma MCP, Supabase MCP, Paper MCP.\nSteps:\n1. Design the UI in Figma.\n2. Implement it with the Figma MCP and Claude (Fable 5.1 Max), using your front-end skills.\n3. Compare the output with Figma and fix spacing, borders and details.\n4. Add more features with Claude, then use the Supabase MCP for the backend.\n5. Variant: with Paper connected through MCP, leave comments on the design and ask Claude Code to implement them.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Marcel — https://x.com/marcelkargul/status/2099869668387291469",
   "steps": [
    "Design the UI in Figma.",
    "Implement it with the Figma MCP and Claude (Fable 5.1 Max), using your front-end skills.",
    "Compare the output with Figma and fix spacing, borders and details.",
    "Add more features with Claude, then use the Supabase MCP for the backend.",
    "Variant: with Paper connected through MCP, leave comments on the design and ask Claude Code to implement them."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-15",
   "trend_score": 77.2,
   "sources": [
    {
     "author": "Marcel",
     "handle": "@marcelkargul",
     "url": "https://x.com/marcelkargul/status/2099869668387291469",
     "platform": "x",
     "date": "2026-09-15",
     "primary": true
    },
    {
     "author": "Sepy Bazzazi",
     "handle": "@SepBaz",
     "url": "https://x.com/SepBaz/status/2110144831532216722",
     "platform": "x",
     "date": "2026-10-13",
     "primary": false
    }
   ]
  },
  {
   "slug": "codex-wall-projection-game",
   "url": "https://agentsetups.dev/use-case/codex-wall-projection-game/",
   "title": "Build a hand-controlled game projected on your wall",
   "summary": "Vibe-coded with Codex: a game projected on a living-room wall, controlled by hand via computer vision + projection mapping.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "computer vision",
    "projection mapping"
   ],
   "prompt": "Goal: Make an interactive game on my living-room wall.\nSetup: agents used in source: Codex; tools/MCPs stated: computer vision, projection mapping.\nSteps:\n1. Use Codex to build the game.\n2. Track your hand with computer vision as the controller.\n3. Project it onto the wall with projection mapping.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Hank — https://x.com/h4nkdog/status/2101758913234288883 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Use Codex to build the game.",
    "Track your hand with computer vision as the controller.",
    "Project it onto the wall with projection mapping."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 76.6,
   "sources": [
    {
     "author": "Hank",
     "handle": "@h4nkdog",
     "url": "https://x.com/h4nkdog/status/2101758913234288883",
     "platform": "x",
     "date": "2026-09-20",
     "primary": true
    }
   ]
  },
  {
   "slug": "generative-riso-animation",
   "url": "https://agentsetups.dev/use-case/generative-riso-animation/",
   "title": "Generate a riso-style animated scene in JavaScript",
   "summary": "Opus 5.5 single-shot a train-journey riso animation in ~45 min; add real instrument samples to its scores.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Salamander Grand Piano samples"
   ],
   "prompt": "Goal: Create an animated art piece entirely in code.\nSetup: agents used in source: Claude; tools/MCPs stated: Salamander Grand Piano samples.\nSteps:\n1. Prompt for the scene and style (e.g. a riso-print train journey drawn entirely in JavaScript).\n2. Have it write the score and use open-source instrument recordings on top for better sound.\n3. Variant: plot wallpapers from real scientific data and code, with no image generation.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/mshort3 — https://www.reddit.com/r/ClaudeAI/comments/1wnkvys/opus_55_creates_a_train_journey_drawn_entirely_in/",
   "steps": [
    "Prompt for the scene and style (e.g. a riso-print train journey drawn entirely in JavaScript).",
    "Have it write the score and use open-source instrument recordings on top for better sound.",
    "Variant: plot wallpapers from real scientific data and code, with no image generation."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-22",
   "trend_score": 76.4,
   "sources": [
    {
     "author": "/u/mshort3",
     "handle": "/u/mshort3",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wnkvys/opus_55_creates_a_train_journey_drawn_entirely_in/",
     "platform": "reddit",
     "date": "2026-09-22",
     "primary": true
    },
    {
     "author": "/u/Singularity-42",
     "handle": "/u/Singularity-42",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wogab3/made_entirely_with_opus_55_321_of_openrouter_api/",
     "platform": "reddit",
     "date": "2026-09-23",
     "primary": false
    },
    {
     "author": "/u/stoleyourshoes",
     "handle": "/u/stoleyourshoes",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wwxsle/i_used_claude_to_make_106_almost_all_black_oled/",
     "platform": "reddit",
     "date": "2026-10-03",
     "primary": false
    }
   ]
  },
  {
   "slug": "mod-pc-games-with-claude",
   "url": "https://agentsetups.dev/use-case/mod-pc-games-with-claude/",
   "title": "Mod PC games you own with Claude Code",
   "summary": "Skills, tools and the fal MCP let Claude Code do recon, reverse engineering and generated assets for game mods.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "fal MCP"
   ],
   "prompt": "Goal: Mod a PC game I own.\nSetup: agents used in source: Claude; tools/MCPs stated: fal MCP.\nSteps:\n1. Install the universal-modder skills and the fal MCP.\n2. Point Claude Code at the game for recon and reverse engineering.\n3. Generate assets with fal and apply the mod.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: rehan-remade — https://github.com/rehan-remade/universal-modder (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install the universal-modder skills and the fal MCP.",
    "Point Claude Code at the game for recon and reverse engineering.",
    "Generate assets with fal and apply the mod."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 75.4,
   "sources": [
    {
     "author": "rehan-remade",
     "handle": "rehan-remade",
     "url": "https://github.com/rehan-remade/universal-modder",
     "platform": "github",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "port-amiga-game-from-assembly",
   "url": "https://agentsetups.dev/use-case/port-amiga-game-from-assembly/",
   "title": "Port a 1993 Amiga game by having an LLM read 68000 assembly",
   "summary": "Its creator moved a 34k-line C++ engine into Godot 4, then had Fable 5 work from the original 72,758 lines of assembly.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Fable 5"
   ],
   "tools": [
    "Godot 4"
   ],
   "prompt": "Goal: Port an old game to a modern engine from its original sources.\nSetup: agents used in source: Claude; tools/MCPs stated: Godot 4.\nSteps:\n1. Plan conditional steps, each only if the previous works.\n2. Step 1 (safe): move an existing engine port into the new engine (34,000 lines of C++ into Godot 4).\n3. Step 2 (hard): give the agent the original assembly (72,758 lines of 68000) and binary level maps.\n4. Play the result every night, say what feels wrong, and make the decisions only the original author can.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: rabahs (Babylonian Twins) — https://babyloniantwins.com/blog/porting-a-1993-amiga-game-to-godot/",
   "steps": [
    "Plan conditional steps, each only if the previous works.",
    "Step 1 (safe): move an existing engine port into the new engine (34,000 lines of C++ into Godot 4).",
    "Step 2 (hard): give the agent the original assembly (72,758 lines of 68000) and binary level maps.",
    "Play the result every night, say what feels wrong, and make the decisions only the original author can."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-03",
   "trend_score": 75.2,
   "sources": [
    {
     "author": "rabahs (Babylonian Twins)",
     "handle": "babyloniantwins.com",
     "url": "https://babyloniantwins.com/blog/porting-a-1993-amiga-game-to-godot/",
     "platform": "blog",
     "date": "2026-09-03",
     "primary": true
    },
    {
     "author": "rabahs",
     "handle": "rabahs",
     "url": "https://news.ycombinator.com/item?id=49550375",
     "platform": "hn",
     "date": "2026-09-03",
     "primary": false
    }
   ]
  },
  {
   "slug": "agents-talk-over-tailscale",
   "url": "https://agentsetups.dev/use-case/agents-talk-over-tailscale/",
   "title": "Let your different agents talk to each other over Tailscale",
   "summary": "A personal tool let Grok Bot ask Muse to make a phone call; it connects Instinct, Codex, Claude Code and Hermes.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "Claude",
    "Codex",
    "Hermes Agent",
    "Grok Bot",
    "Meta Muse",
    "Instinct"
   ],
   "models": [],
   "tools": [
    "Tailscale"
   ],
   "prompt": "Goal: Connect my agents so one can ask another to act.\nSetup: agents used in source: Claude, Codex, Hermes Agent, Grok Bot, Meta Muse, Instinct; tools/MCPs stated: Tailscale.\nSteps:\n1. Put the machines running each agent on a Tailscale network.\n2. Build a small bridge so agents can send each other requests.\n3. Example: have Grok Bot ask Muse to make a phone call.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Matt Van Horn — https://x.com/mvanhorn/status/2102920506391535865 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Put the machines running each agent on a Tailscale network.",
    "Build a small bridge so agents can send each other requests.",
    "Example: have Grok Bot ask Muse to make a phone call."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 74.3,
   "sources": [
    {
     "author": "Matt Van Horn",
     "handle": "@mvanhorn",
     "url": "https://x.com/mvanhorn/status/2102920506391535865",
     "platform": "x",
     "date": "2026-09-24",
     "primary": true
    },
    {
     "author": "Matt Van Horn",
     "handle": "@mvanhorn",
     "url": "https://x.com/mvanhorn/status/2105071040590401670",
     "platform": "x",
     "date": "2026-09-29",
     "primary": false
    }
   ]
  },
  {
   "slug": "scan-then-auto-refactor-prs",
   "url": "https://agentsetups.dev/use-case/scan-then-auto-refactor-prs/",
   "title": "Scan a 0.5M-line codebase, then auto-open refactor PRs",
   "summary": "A Jev scan found 12,938 issues in 2 min for $0.89; an always-on Opus 5.5 loop opens and merges refactor PRs (50 merged).",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5",
    "Jev"
   ],
   "tools": [],
   "prompt": "Goal: Turn a whole-codebase quality and security scan into a steady stream of refactor PRs.\nSetup: agents used in source: Claude.\nSteps:\n1. Scan the whole codebase for code quality and security issues. The author used the Jev model on about 0.5M lines.\n2. Feed the findings to Claude Code (Opus 5.5) running in a loop on a server so it is always on.\n3. The loop opens refactor PRs, runs the gates, and merges once the gates pass.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Pau Guirao — https://x.com/guirao_pau/status/2102691248293257513",
   "steps": [
    "Scan the whole codebase for code quality and security issues. The author used the Jev model on about 0.5M lines.",
    "Feed the findings to Claude Code (Opus 5.5) running in a loop on a server so it is always on.",
    "The loop opens refactor PRs, runs the gates, and merges once the gates pass."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 73.5,
   "sources": [
    {
     "author": "Pau Guirao",
     "handle": "@guirao_pau",
     "url": "https://x.com/guirao_pau/status/2102691248293257513",
     "platform": "x",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "orchestrator-never-writes",
   "url": "https://agentsetups.dev/use-case/orchestrator-never-writes/",
   "title": "Cut orchestration cost 77%: the planner never writes code",
   "summary": "GPT-6.1 Sol plans and reviews only; local Qwen workers on one RTX 3090 do every write. Slower but cheaper.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "GPT-6.1 Sol",
    "Qwen 3.8 27B",
    "DeepSeek V4.1 Flash"
   ],
   "tools": [],
   "prompt": "Goal: Make my expensive model orchestrate only, with cheap workers doing all edits.\nSetup: agents used in source: Claude, Codex.\nSteps:\n1. Let the orchestrator read, plan, delegate and review; refuse every write or shell call it tries.\n2. Only workers touch files (local Qwen 3.8 27B in the source).\n3. Measure cost and time per task (77% cheaper; 43 min vs under 7).\n4. Variant: DeepSeek V4.1 Flash workers cut Astra usage by 98% in another setup.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/GapNew4766 — https://www.reddit.com/r/AI_Agents/comments/1wtrix3/gpt61_sol_is_cheap_we_made_it_77_cheaper_by_never/",
   "steps": [
    "Let the orchestrator read, plan, delegate and review; refuse every write or shell call it tries.",
    "Only workers touch files (local Qwen 3.8 27B in the source).",
    "Measure cost and time per task (77% cheaper; 43 min vs under 7).",
    "Variant: DeepSeek V4.1 Flash workers cut Astra usage by 98% in another setup."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 73.1,
   "sources": [
    {
     "author": "/u/GapNew4766",
     "handle": "/u/GapNew4766",
     "url": "https://www.reddit.com/r/AI_Agents/comments/1wtrix3/gpt61_sol_is_cheap_we_made_it_77_cheaper_by_never/",
     "platform": "reddit",
     "date": "2026-09-30",
     "primary": true
    },
    {
     "author": "/u/Rare_Guide_9830",
     "handle": "/u/Rare_Guide_9830",
     "url": "https://www.reddit.com/r/vibecoding/comments/1wl3lfi/i_built_an_orchestration_package_that_lowered_my/",
     "platform": "reddit",
     "date": "2026-09-20",
     "primary": false
    }
   ]
  },
  {
   "slug": "video-in-same-style",
   "url": "https://agentsetups.dev/use-case/video-in-same-style/",
   "title": "Show it a video you love, get a new one in that style",
   "summary": "reelmimic: an AI crew (Claude Code or Codex) plans, builds and reviews a new video in the same style with you.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Make a new video in the style of one I like.\nSetup: agents used in source: Claude, Codex.\nSteps:\n1. Give the reference video.\n2. The crew plans, builds and reviews the new video with you.\n3. Variant: topic in, narrated motion-graphics explainer out (anything2explainer).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: edenfunf — https://github.com/edenfunf/reelmimic (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give the reference video.",
    "The crew plans, builds and reviews the new video with you.",
    "Variant: topic in, narrated motion-graphics explainer out (anything2explainer)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-28",
   "trend_score": 73.1,
   "sources": [
    {
     "author": "edenfunf",
     "handle": "edenfunf",
     "url": "https://github.com/edenfunf/reelmimic",
     "platform": "github",
     "date": "2026-09-28",
     "primary": true
    },
    {
     "author": "Vincentwei1021",
     "handle": "Vincentwei1021",
     "url": "https://github.com/Vincentwei1021/anything2explainer",
     "platform": "github",
     "date": "2026-09-08",
     "primary": false
    }
   ]
  },
  {
   "slug": "opus-codex-animated-marketing-videos",
   "url": "https://agentsetups.dev/use-case/opus-codex-animated-marketing-videos/",
   "title": "Make animated marketing videos with Opus and Codex",
   "summary": "Opus plans scenes, records, animates and edits; it calls Codex for generated images. Storyboard before building.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Opus 5.5",
    "GPT-6"
   ],
   "tools": [
    "Paper",
    "Figma"
   ],
   "prompt": "Goal: Produce an animated product marketing video with agents.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Paper, Figma.\nSteps:\n1. Start with the idea and let Opus question you: goal, audience, call to action, where it’s published, length and format.\n2. Give brand context and references; connect Paper or Figma so it can use your logos, fonts and screenshots.\n3. Ask for a storyboard first: what each scene shows, on-screen text, which parts need recordings or generated images, motion and timing, audio. Fix it before building.\n4. Generate missing assets: Opus calls GPT-6 through Codex for images, or make them separately and hand them over with placement notes.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: The post continues past this step.\nBased on: Shann³ — https://x.com/shannholmberg/status/2103173892831674715",
   "steps": [
    "Start with the idea and let Opus question you: goal, audience, call to action, where it’s published, length and format.",
    "Give brand context and references; connect Paper or Figma so it can use your logos, fonts and screenshots.",
    "Ask for a storyboard first: what each scene shows, on-screen text, which parts need recordings or generated images, motion and timing, audio. Fix it before building.",
    "Generate missing assets: Opus calls GPT-6 through Codex for images, or make them separately and hand them over with placement notes."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 72.3,
   "sources": [
    {
     "author": "Shann³",
     "handle": "@shannholmberg",
     "url": "https://x.com/shannholmberg/status/2103173892831674715",
     "platform": "x",
     "date": "2026-09-24",
     "primary": true
    }
   ]
  },
  {
   "slug": "make-rust-code-faster-iteratively",
   "url": "https://agentsetups.dev/use-case/make-rust-code-faster-iteratively/",
   "title": "Get 2–20x faster Rust by iterating “make it faster”",
   "summary": "Max Woolf’s guarded loop: ask agents to make Rust (PyO3) code faster, forbid unsafe, benchmark each step.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [
    "Rust",
    "PyO3"
   ],
   "prompt": "Goal: Iteratively make a Rust implementation faster with benchmarks as the judge.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Rust, PyO3.\nSteps:\n1. Pick a target (e.g. reimplementing ML algorithms in Rust with PyO3 bindings).\n2. Set guardrails: forbid unsafe code whenever possible; keep correctness tests.\n3. Ask the agent repeatedly to make the code faster, benchmarking every iteration.\n4. Publish prompts and benchmark results so the gains are checkable.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Max Woolf — https://minimaxir.com/2026/09/agentic-iteration/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Pick a target (e.g. reimplementing ML algorithms in Rust with PyO3 bindings).",
    "Set guardrails: forbid unsafe code whenever possible; keep correctness tests.",
    "Ask the agent repeatedly to make the code faster, benchmarking every iteration.",
    "Publish prompts and benchmark results so the gains are checkable."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-22",
   "trend_score": 69.5,
   "sources": [
    {
     "author": "Max Woolf",
     "handle": "minimaxir",
     "url": "https://minimaxir.com/2026/09/agentic-iteration/",
     "platform": "blog",
     "date": "2026-09-22",
     "primary": true
    },
    {
     "author": "mooreds",
     "handle": "mooreds",
     "url": "https://news.ycombinator.com/item?id=49803085",
     "platform": "hn",
     "date": "2026-09-22",
     "primary": false
    }
   ]
  },
  {
   "slug": "kindle-photo-frame-agent",
   "url": "https://agentsetups.dev/use-case/kindle-photo-frame-agent/",
   "title": "Turn an unused Kindle into a photo frame",
   "summary": "Codex with GPT-6 Astra adapted an open jailbreak over Wi-Fi, built KindleCTL tools and a slideshow app.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "GPT-6 Astra"
   ],
   "tools": [
    "T3 Code",
    "KindleCTL",
    "Python",
    "C"
   ],
   "prompt": "Goal: Give an old Kindle a new job as a photo slideshow.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: T3 Code, KindleCTL, Python, C.\nSteps:\n1. Start in an empty folder; give the agent the Kindle’s network address and model (all over Wi-Fi).\n2. Ask it to build custom software for personal use, adapting existing open-source jailbreak work (here SpiderCat / KindleModding).\n3. Have it build tools to send commands, transfer files and investigate errors; verify access survives a reboot.\n4. Ask for a feedback loop: a persistent diagnostic connection and remote screen captures so it can test without you sending photos.\n5. Test small first (set one image as screensaver), then build the slideshow; fix e-ink ghosting the tests missed.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Niraj Rajgor — https://nirajrajgor.com/blog/kindle-photo-frame-with-ai",
   "steps": [
    "Start in an empty folder; give the agent the Kindle’s network address and model (all over Wi-Fi).",
    "Ask it to build custom software for personal use, adapting existing open-source jailbreak work (here SpiderCat / KindleModding).",
    "Have it build tools to send commands, transfer files and investigate errors; verify access survives a reboot.",
    "Ask for a feedback loop: a persistent diagnostic connection and remote screen captures so it can test without you sending photos.",
    "Test small first (set one image as screensaver), then build the slideshow; fix e-ink ghosting the tests missed."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-27",
   "trend_score": 68.8,
   "sources": [
    {
     "author": "Niraj Rajgor",
     "handle": "nirajrajgor.com",
     "url": "https://nirajrajgor.com/blog/kindle-photo-frame-with-ai",
     "platform": "blog",
     "date": "2026-09-27",
     "primary": true
    },
    {
     "author": "nirajrajgor",
     "handle": "nirajrajgor",
     "url": "https://news.ycombinator.com/item?id=50064318",
     "platform": "hn",
     "date": "2026-10-12",
     "primary": false
    }
   ]
  },
  {
   "slug": "resume-session-in-hermes",
   "url": "https://agentsetups.dev/use-case/resume-session-in-hermes/",
   "title": "Resume a Claude Code or Codex session in Hermes",
   "summary": "The single command hermes --resume @claude / @codex continues the exact session in Hermes Agent.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex",
    "Hermes Agent"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Continue my current Claude Code or Codex session inside Hermes Agent.\nSetup: agents used in source: Claude, Codex, Hermes Agent.\nSteps:\n1. Run hermes --resume @claude or hermes --resume @codex.\n2. Continue the same session in Hermes.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: tonbi — https://x.com/tonbistudio/status/2096238168978645260",
   "steps": [
    "Run hermes --resume @claude or hermes --resume @codex.",
    "Continue the same session in Hermes."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-05",
   "trend_score": 67.3,
   "sources": [
    {
     "author": "tonbi",
     "handle": "@tonbistudio",
     "url": "https://x.com/tonbistudio/status/2096238168978645260",
     "platform": "x",
     "date": "2026-09-05",
     "primary": true
    }
   ]
  },
  {
   "slug": "ai-sdr-team",
   "url": "https://agentsetups.dev/use-case/ai-sdr-team/",
   "title": "Run an AI SDR team: 3 researchers plus an Opus reviewer",
   "summary": "Daily, 3 Sonnet agents take 15 leads each, research them and write cold emails; Opus reviews and you approve.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "Claude"
   ],
   "models": [
    "Sonnet",
    "Opus"
   ],
   "tools": [
    "Meta Ads Library"
   ],
   "prompt": "Goal: Research leads and write personalised cold emails every day.\nSetup: agents used in source: Claude; tools/MCPs stated: Meta Ads Library.\nSteps:\n1. Give each of 3 Sonnet agents 15 leads.\n2. They research each lead’s website and Meta Ads Library entries.\n3. Find specific weaknesses or opportunities, then write a personalised cold email.\n4. Opus reviews every email.\n5. I approve before anything goes out.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: hritik — https://x.com/AI_Bhaiiii/status/2102058314280710503",
   "steps": [
    "Give each of 3 Sonnet agents 15 leads.",
    "They research each lead’s website and Meta Ads Library entries.",
    "Find specific weaknesses or opportunities, then write a personalised cold email.",
    "Opus reviews every email.",
    "I approve before anything goes out."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-21",
   "trend_score": 66.0,
   "sources": [
    {
     "author": "hritik",
     "handle": "@AI_Bhaiiii",
     "url": "https://x.com/AI_Bhaiiii/status/2102058314280710503",
     "platform": "x",
     "date": "2026-09-21",
     "primary": true
    },
    {
     "author": "Richard Illingworth",
     "handle": "@RCIllingworth",
     "url": "https://x.com/RCIllingworth/status/2108558265105702922",
     "platform": "x",
     "date": "2026-10-09",
     "primary": false
    },
    {
     "author": "Christian",
     "handle": "@cbwritescopy",
     "url": "https://x.com/cbwritescopy/status/2097307590527013365",
     "platform": "x",
     "date": "2026-09-08",
     "primary": false
    }
   ]
  },
  {
   "slug": "chess-game-postmortem-skill",
   "url": "https://agentsetups.dev/use-case/chess-game-postmortem-skill/",
   "title": "Get a narrated post-mortem of your chess game",
   "summary": "Give Claude a lichess link and your voice memo; it checks your questions with Stockfish and narrates a video.",
   "category": "education",
   "category_label": "Education",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Stockfish",
    "whisper.cpp",
    "lichess"
   ],
   "prompt": "Goal: Analyse one of my chess games in plain language.\nSetup: agents used in source: Claude; tools/MCPs stated: Stockfish, whisper.cpp, lichess.\nSteps:\n1. Install the chess-postmortem skills.\n2. Give Claude the lichess game link and an mp3 of your thoughts during/after the game.\n3. It transcribes, sweeps the game with Stockfish, annotates the PGN and builds a narrated video.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: brumar — https://news.ycombinator.com/item?id=49857528",
   "steps": [
    "Install the chess-postmortem skills.",
    "Give Claude the lichess game link and an mp3 of your thoughts during/after the game.",
    "It transcribes, sweeps the game with Stockfish, annotates the PGN and builds a narrated video."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 65.3,
   "sources": [
    {
     "author": "brumar",
     "handle": "brumar",
     "url": "https://news.ycombinator.com/item?id=49857528",
     "platform": "hn",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "geolocate-a-photo",
   "url": "https://agentsetups.dev/use-case/geolocate-a-photo/",
   "title": "Find where a photo was taken, showing the work",
   "summary": "geo-sleuth uses OpenStreetMap geometry, elevation skylines, satellite imagery and street view.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [
    "OpenStreetMap"
   ],
   "prompt": "Goal: Work out where a photo was taken.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: OpenStreetMap.\nSteps:\n1. Install the geo-sleuth skill.\n2. Give it the photo.\n3. It compares OSM geometry, elevation skylines, satellite imagery and street view, and shows its reasoning.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Oldcircle — https://github.com/Oldcircle/geo-sleuth (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install the geo-sleuth skill.",
    "Give it the photo.",
    "It compares OSM geometry, elevation skylines, satellite imagery and street view, and shows its reasoning."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-18",
   "trend_score": 64.8,
   "sources": [
    {
     "author": "Oldcircle",
     "handle": "Oldcircle",
     "url": "https://github.com/Oldcircle/geo-sleuth",
     "platform": "github",
     "date": "2026-09-18",
     "primary": true
    }
   ]
  },
  {
   "slug": "trace-texts-across-translations",
   "url": "https://agentsetups.dev/use-case/trace-texts-across-translations/",
   "title": "Trace historical texts across languages",
   "summary": "Historian Benjamin Breen used GPT-6 Astra and Opus 5.5 on “tractable” history problems, e.g. identifying a Newton source.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "GPT-6 Astra",
    "Opus 5.5"
   ],
   "tools": [],
   "prompt": "Goal: Pick historical problems frontier models can actually help solve.\nSetup: agents used in source: Claude, Codex.\nSteps:\n1. Check the problem: is it already identified by experts, fully digitised, suited to multilingual reasoning, code or large-dataset search, and provable or disprovable?\n2. Good fits: cryptography and codebreaking; tracing texts across translations (he identified a French source Newton freely translated into Latin); linking findings scattered across niche subfields.\n3. Work in collaborative groups with domain experts checking the results.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Benjamin Breen — https://resobscura.substack.com/p/ai-labs-need-to-start-funding-historical (summarised from source; the source has no explicit step list)",
   "steps": [
    "Check the problem: is it already identified by experts, fully digitised, suited to multilingual reasoning, code or large-dataset search, and provable or disprovable?",
    "Good fits: cryptography and codebreaking; tracing texts across translations (he identified a French source Newton freely translated into Latin); linking findings scattered across niche subfields.",
    "Work in collaborative groups with domain experts checking the results."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 63.8,
   "sources": [
    {
     "author": "Benjamin Breen",
     "handle": "Res Obscura",
     "url": "https://resobscura.substack.com/p/ai-labs-need-to-start-funding-historical",
     "platform": "blog",
     "date": "2026-09-24",
     "primary": true
    },
    {
     "author": "benbreen",
     "handle": "benbreen",
     "url": "https://news.ycombinator.com/item?id=49835531",
     "platform": "hn",
     "date": "2026-09-24",
     "primary": false
    }
   ]
  },
  {
   "slug": "meta-lead-gen-campaign-claude-code",
   "url": "https://agentsetups.dev/use-case/meta-lead-gen-campaign-claude-code/",
   "title": "Build and launch a Meta lead-gen campaign with Claude Code",
   "summary": "Claude Code set up the pixel and system-user token via the Chrome extension, wired CAPI tracking and launched by API.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Meta Business Manager"
   ],
   "prompt": "Goal: Build an end-to-end Meta lead-gen campaign without clicking around Business Manager.\nSetup: agents used in source: Claude; tools/MCPs stated: Meta Business Manager.\nSteps:\n1. Browser: let Claude Code use the Chrome extension in Business Manager to create a pixel and a system-user token, and link the assets.\n2. Creative: feed it inspiration from DTC brands (via scrapecreators); the author made 12 “job photo + text bubble” creatives in 15–20 min.\n3. Landing page: a calendar-booking quiz funnel to self-qualify leads.\n4. Tracking: have it pull the pixel and CAPI details, implement and test the events.\n5. Build: store the system-user token in the environment and have it create and launch the campaigns programmatically.\n6. Targeting: go broad and optimise for the deep-funnel event, not clicks.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: The Boring Marketer — https://x.com/boringmarketer/status/2094776379090878718",
   "steps": [
    "Browser: let Claude Code use the Chrome extension in Business Manager to create a pixel and a system-user token, and link the assets.",
    "Creative: feed it inspiration from DTC brands (via scrapecreators); the author made 12 “job photo + text bubble” creatives in 15–20 min.",
    "Landing page: a calendar-booking quiz funnel to self-qualify leads.",
    "Tracking: have it pull the pixel and CAPI details, implement and test the events.",
    "Build: store the system-user token in the environment and have it create and launch the campaigns programmatically.",
    "Targeting: go broad and optimise for the deep-funnel event, not clicks."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-01",
   "trend_score": 62.3,
   "sources": [
    {
     "author": "The Boring Marketer",
     "handle": "@boringmarketer",
     "url": "https://x.com/boringmarketer/status/2094776379090878718",
     "platform": "x",
     "date": "2026-09-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "muse-instinct-agents-partner",
   "url": "https://agentsetups.dev/use-case/muse-instinct-agents-partner/",
   "title": "Introduce Muse to Instinct so they split the work",
   "summary": "@ZevLapin’s Muse and Instinct agents partnered: 4,700 leads harvested and validated in two hours, no duplicate work.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "Meta Muse",
    "Instinct"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Have two personal agents from different vendors collaborate on one project.\nSetup: agents used in source: Meta Muse, Instinct.\nSteps:\n1. Introduce your Muse agent to your Instinct agent.\n2. Give them a shared task (here lead harvesting and validation).\n3. Let them divide the work and agree on how they work together (they wrote their own “work contract”).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Zev — https://x.com/ZevLapin/status/2100774170783309977 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Introduce your Muse agent to your Instinct agent.",
    "Give them a shared task (here lead harvesting and validation).",
    "Let them divide the work and agree on how they work together (they wrote their own “work contract”)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-18",
   "trend_score": 62.0,
   "sources": [
    {
     "author": "Zev",
     "handle": "@ZevLapin",
     "url": "https://x.com/ZevLapin/status/2100774170783309977",
     "platform": "x",
     "date": "2026-09-18",
     "primary": true
    }
   ]
  },
  {
   "slug": "personal-finance-dashboard-simplefin",
   "url": "https://agentsetups.dev/use-case/personal-finance-dashboard-simplefin/",
   "title": "Build a Monarch-style finance dashboard for under $20",
   "summary": "SimpleFin bank sync into open-source Actual Budget, with a React front end built on Opus 5.5 medium.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "SimpleFin",
    "Actual Budget",
    "React"
   ],
   "prompt": "Goal: Build my own personal finance dashboard that keeps data local.\nSetup: agents used in source: Claude; tools/MCPs stated: SimpleFin, Actual Budget, React.\nSteps:\n1. Connect bank accounts through SimpleFin and link them to Actual Budget as the backend (local, open-source data).\n2. Have the agent research existing dashboards and pull screenshots to work from.\n3. Get one page working well first (cash flow), then add others.\n4. Add custom pages (e.g. per-property cash flow) feeding only net cash flow into the main budget.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/RallyMantis — https://www.reddit.com/r/ClaudeAI/comments/1wr140j/i_built_my_own_monarchstyle_finance_dashboard/",
   "steps": [
    "Connect bank accounts through SimpleFin and link them to Actual Budget as the backend (local, open-source data).",
    "Have the agent research existing dashboards and pull screenshots to work from.",
    "Get one page working well first (cash flow), then add others.",
    "Add custom pages (e.g. per-property cash flow) feeding only net cash flow into the main budget."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 61.2,
   "sources": [
    {
     "author": "/u/RallyMantis",
     "handle": "/u/RallyMantis",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wr140j/i_built_my_own_monarchstyle_finance_dashboard/",
     "platform": "reddit",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-in-chrome-nyt-connections",
   "url": "https://agentsetups.dev/use-case/claude-in-chrome-nyt-connections/",
   "title": "Have Claude in Chrome solve a web puzzle",
   "summary": "Claude in Chrome solved a NYT Connections puzzle one-shot in 40 seconds.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Test browser-agent control on a real website task.\nSetup: agents used in source: Claude.\nSteps:\n1. Open the page in Chrome with Claude in Chrome.\n2. Ask it to solve the puzzle and watch it work.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Josh You — https://x.com/justjoshinyou13/status/2102962460005122407 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Open the page in Chrome with Claude in Chrome.",
    "Ask it to solve the puzzle and watch it work."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 60.2,
   "sources": [
    {
     "author": "Josh You",
     "handle": "@justjoshinyou13",
     "url": "https://x.com/justjoshinyou13/status/2102962460005122407",
     "platform": "x",
     "date": "2026-09-24",
     "primary": true
    }
   ]
  },
  {
   "slug": "local-qwen-openclaw-5090",
   "url": "https://agentsetups.dev/use-case/local-qwen-openclaw-5090/",
   "title": "Run OpenClaw on a local Qwen model at 150–250 tok/s",
   "summary": "An RTX 5090 with SGLang serving Qwen3.8 made a local model a real alternative to paid frontier APIs.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Codex",
    "OpenClaw"
   ],
   "models": [
    "Qwen3.8"
   ],
   "tools": [
    "SGLang"
   ],
   "prompt": "Goal: Use a fast local model as my OpenClaw daily driver.\nSetup: agents used in source: Codex, OpenClaw; tools/MCPs stated: SGLang.\nSteps:\n1. Serve the model with SGLang on a strong GPU (RTX 5090).\n2. Point OpenClaw at it.\n3. Compare speed and capability against your paid models.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Extension_Brick9151 — https://www.reddit.com/r/openclaw/comments/1wh8pe8/qwen3827b_openclaw_is_amazing/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Serve the model with SGLang on a strong GPU (RTX 5090).",
    "Point OpenClaw at it.",
    "Compare speed and capability against your paid models."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-15",
   "trend_score": 60.0,
   "sources": [
    {
     "author": "/u/Extension_Brick9151",
     "handle": "/u/Extension_Brick9151",
     "url": "https://www.reddit.com/r/openclaw/comments/1wh8pe8/qwen3827b_openclaw_is_amazing/",
     "platform": "reddit",
     "date": "2026-09-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-job-hunt",
   "url": "https://agentsetups.dev/use-case/hermes-job-hunt/",
   "title": "Apply to 50 jobs in 2 weeks with tailored materials",
   "summary": "Hermes finds fresh postings and writes a custom resume, cover letter and recruiter email; 2 interviews, 1–2 min each.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Claude",
    "Hermes Agent"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Run my job search with tailored applications.\nSetup: agents used in source: Claude, Hermes Agent.\nSteps:\n1. Find recently posted jobs that match my profile.\n2. For each, write a custom resume, cover letter and a cold email to the recruiter or decision maker.\n3. Variant (Job Search OS skills): /job-fit-scorer, /resume-tailor (only real experience), /referral-request, /interview-prep, /interview-debrief.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Noah — https://x.com/noahreeveshq/status/2102125839529697644",
   "steps": [
    "Find recently posted jobs that match my profile.",
    "For each, write a custom resume, cover letter and a cold email to the recruiter or decision maker.",
    "Variant (Job Search OS skills): /job-fit-scorer, /resume-tailor (only real experience), /referral-request, /interview-prep, /interview-debrief."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-21",
   "trend_score": 59.6,
   "sources": [
    {
     "author": "Noah",
     "handle": "@noahreeveshq",
     "url": "https://x.com/noahreeveshq/status/2102125839529697644",
     "platform": "x",
     "date": "2026-09-21",
     "primary": true
    },
    {
     "author": "Aakash Gupta",
     "handle": "@aakashgupta",
     "url": "https://x.com/aakashgupta/status/2108234472009449620",
     "platform": "x",
     "date": "2026-10-08",
     "primary": false
    }
   ]
  },
  {
   "slug": "codex-3d-scan-to-ios-game",
   "url": "https://agentsetups.dev/use-case/codex-3d-scan-to-ios-game/",
   "title": "Turn a 3D-scanned object into an iOS game with Codex",
   "summary": "A 3D-scanned firewood splitter went from a three.js web toy to a native iOS app with leaderboards and friend challenges.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "iOS"
   ],
   "prompt": "Goal: Ship my three.js experiment as a real iOS game.\nSetup: agents used in source: Codex; tools/MCPs stated: iOS.\nSteps:\n1. Start from the three.js web experience built around your 3D scan.\n2. Have Codex port it to a native iOS app.\n3. Add features: leaderboards and competing with friends for the cleanest cut.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Gavin Shapiro 🐧 — https://x.com/shapiro500/status/2102757069136814323",
   "steps": [
    "Start from the three.js web experience built around your 3D scan.",
    "Have Codex port it to a native iOS app.",
    "Add features: leaderboards and competing with friends for the cleanest cut."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 59.5,
   "sources": [
    {
     "author": "Gavin Shapiro 🐧",
     "handle": "@shapiro500",
     "url": "https://x.com/shapiro500/status/2102757069136814323",
     "platform": "x",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-whatsapp-memory-assistant",
   "url": "https://agentsetups.dev/use-case/n8n-whatsapp-memory-assistant/",
   "title": "Give a WhatsApp AI assistant selective long-term memory",
   "summary": "An n8n workflow saves only important user facts (name, job, preferences) and retrieves them later.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "n8n",
    "WhatsApp"
   ],
   "prompt": "Goal: Make my WhatsApp assistant remember important facts about users.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n, WhatsApp.\nSteps:\n1. Detect important information in each message instead of storing everything.\n2. Save only those details.\n3. Retrieve them when the user returns.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/cuebicai — https://www.reddit.com/r/n8n/comments/1ws34sk/built_an_n8n_workflow_for_a_whatsapp_ai_assistant/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Detect important information in each message instead of storing everything.",
    "Save only those details.",
    "Retrieve them when the user returns."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-28",
   "trend_score": 59.5,
   "sources": [
    {
     "author": "/u/cuebicai",
     "handle": "/u/cuebicai",
     "url": "https://www.reddit.com/r/n8n/comments/1ws34sk/built_an_n8n_workflow_for_a_whatsapp_ai_assistant/",
     "platform": "reddit",
     "date": "2026-09-28",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-instagram-comment-dm",
   "url": "https://agentsetups.dev/use-case/n8n-instagram-comment-dm/",
   "title": "Auto-DM people who comment a keyword on Instagram",
   "summary": "n8n: new comment → look up the post’s config in Google Sheets → build and send the DM with the link.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "n8n",
    "Google Sheets",
    "Instagram"
   ],
   "prompt": "Goal: Send a DM with a link to everyone who comments a keyword.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n, Google Sheets, Instagram.\nSteps:\n1. Trigger on new comments; get the post/reel ID and the comment keyword.\n2. Search Google Sheets for the matching configuration (message + link).\n3. Build the DM and send it.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/cuebicai — https://www.reddit.com/r/n8n/comments/1wnwmlo/built_an_n8n_workflow_to_automatically_dm_people/",
   "steps": [
    "Trigger on new comments; get the post/reel ID and the comment keyword.",
    "Search Google Sheets for the matching configuration (message + link).",
    "Build the DM and send it."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 59.1,
   "sources": [
    {
     "author": "/u/cuebicai",
     "handle": "/u/cuebicai",
     "url": "https://www.reddit.com/r/n8n/comments/1wnwmlo/built_an_n8n_workflow_to_automatically_dm_people/",
     "platform": "reddit",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "markdown-wiki-memory-benchmark",
   "url": "https://agentsetups.dev/use-case/markdown-wiki-memory-benchmark/",
   "title": "Pick an agent memory system with your own benchmark",
   "summary": "1,800 tasks across 12 memory systems with Claude Code: a plain Markdown wiki tied for first (97.1/100).",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5"
   ],
   "tools": [
    "Cognee"
   ],
   "prompt": "Goal: Compare memory systems for my agents on the same work.\nSetup: agents used in source: Claude; tools/MCPs stated: Cognee.\nSteps:\n1. Give agents the same multi-session work and a fixed question set with each memory system.\n2. Let each agent decide what to store, guided by that tool’s docs.\n3. Compare accuracy, token cost and latency (a Markdown wiki tied with Cognee; Cognee was ~half the cost but 5x slower).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Major-Shirt-8227 — https://www.reddit.com/r/AI_Agents/comments/1wjq4vh/i_tested_12_ai_memory_systems_across_1800_tasks_a/",
   "steps": [
    "Give agents the same multi-session work and a fixed question set with each memory system.",
    "Let each agent decide what to store, guided by that tool’s docs.",
    "Compare accuracy, token cost and latency (a Markdown wiki tied with Cognee; Cognee was ~half the cost but 5x slower)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-18",
   "trend_score": 58.9,
   "sources": [
    {
     "author": "/u/Major-Shirt-8227",
     "handle": "/u/Major-Shirt-8227",
     "url": "https://www.reddit.com/r/AI_Agents/comments/1wjq4vh/i_tested_12_ai_memory_systems_across_1800_tasks_a/",
     "platform": "reddit",
     "date": "2026-09-18",
     "primary": true
    }
   ]
  },
  {
   "slug": "agent-edits-raw-footage-video-use",
   "url": "https://agentsetups.dev/use-case/agent-edits-raw-footage-video-use/",
   "title": "Let Claude Code or Codex edit raw footage",
   "summary": "With the video-use repo, the agent cuts filler words and dead air, adds subtitles, renders and checks its own cuts.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [
    "FFmpeg"
   ],
   "prompt": "Goal: Automate the edits I make on every video.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: FFmpeg.\nSteps:\n1. Give the setup prompt to Claude Code with shell access; let it read install.md, install the repo, connect FFmpeg and register the skill.\n2. Put raw footage in a folder and ask the agent to edit: remove filler words, cut dead space, add subtitles, render.\n3. Have it check its own cut points.\n4. Start with one format (e.g. a founder Loom into a 60s launch video, or 3 clips from one podcast) before scaling.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: The Startup Ideas Podcast (SIP) 🧃 — https://x.com/startupideaspod/status/2095550256905847147",
   "steps": [
    "Give the setup prompt to Claude Code with shell access; let it read install.md, install the repo, connect FFmpeg and register the skill.",
    "Put raw footage in a folder and ask the agent to edit: remove filler words, cut dead space, add subtitles, render.",
    "Have it check its own cut points.",
    "Start with one format (e.g. a founder Loom into a 60s launch video, or 3 clips from one podcast) before scaling."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-03",
   "trend_score": 58.5,
   "sources": [
    {
     "author": "The Startup Ideas Podcast (SIP) 🧃",
     "handle": "@startupideaspod",
     "url": "https://x.com/startupideaspod/status/2095550256905847147",
     "platform": "x",
     "date": "2026-09-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-lead-intelligence",
   "url": "https://agentsetups.dev/use-case/n8n-lead-intelligence/",
   "title": "Research and score leads with Tavily and ScrapeGraphAI",
   "summary": "Form → Tavily search → fetch/clean sites (ScrapeGraphAI fallback) → LLM structured scoring → Sheets CRM.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "n8n",
    "Tavily",
    "ScrapeGraphAI",
    "OpenRouter",
    "Google Sheets"
   ],
   "prompt": "Goal: Research and qualify companies automatically.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n, Tavily, ScrapeGraphAI, OpenRouter, Google Sheets.\nSteps:\n1. Form trigger with a research request; validate input.\n2. Tavily search; validate, normalise URLs, filter directories, de-duplicate.\n3. Fetch websites, extract and clean text (ScrapeGraphAI fallback).\n4. LLM chain with structured output; deterministic lead scoring.\n5. Store in a Google Sheets CRM and generate a Markdown report.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/FlakyBeyond5850 — https://www.reddit.com/r/n8n/comments/1wrbyx4/built_a_leadgeneration_and_companyintelligence/",
   "steps": [
    "Form trigger with a research request; validate input.",
    "Tavily search; validate, normalise URLs, filter directories, de-duplicate.",
    "Fetch websites, extract and clean text (ScrapeGraphAI fallback).",
    "LLM chain with structured output; deterministic lead scoring.",
    "Store in a Google Sheets CRM and generate a Markdown report."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-27",
   "trend_score": 57.8,
   "sources": [
    {
     "author": "/u/FlakyBeyond5850",
     "handle": "/u/FlakyBeyond5850",
     "url": "https://www.reddit.com/r/n8n/comments/1wrbyx4/built_a_leadgeneration_and_companyintelligence/",
     "platform": "reddit",
     "date": "2026-09-27",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-d2c-support-os",
   "url": "https://agentsetups.dev/use-case/n8n-d2c-support-os/",
   "title": "Automate D2C support: order tracking, returns, retention",
   "summary": "WhatsApp messages → AI agent → live order status from Shopify → full reply, no human in the loop.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "n8n",
    "WhatsApp",
    "Shopify"
   ],
   "prompt": "Goal: Answer repetitive D2C customer questions automatically.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n, WhatsApp, Shopify.\nSteps:\n1. Customer messages on WhatsApp; the agent reads the query.\n2. It checks the database / pulls live order status from Shopify.\n3. Reply with full order details; handle returns and retention flows.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/_no__regrets_ — https://www.reddit.com/r/n8n/comments/1wknhfx/built_a_d2c_brand_ai_operating_system_that/",
   "steps": [
    "Customer messages on WhatsApp; the agent reads the query.",
    "It checks the database / pulls live order status from Shopify.",
    "Reply with full order details; handle returns and retention flows."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-19",
   "trend_score": 56.8,
   "sources": [
    {
     "author": "/u/_no__regrets_",
     "handle": "/u/_no__regrets_",
     "url": "https://www.reddit.com/r/n8n/comments/1wknhfx/built_a_d2c_brand_ai_operating_system_that/",
     "platform": "reddit",
     "date": "2026-09-19",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-md-for-bioinformatics",
   "url": "https://agentsetups.dev/use-case/claude-md-for-bioinformatics/",
   "title": "Write a CLAUDE.md for your RNA-seq analysis setup",
   "summary": "A researcher stopped re-explaining the pipeline, reference genome and DESeq2 parameters each session.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "DESeq2"
   ],
   "prompt": "Goal: Capture my analysis setup so I never re-explain it.\nSetup: agents used in source: Claude; tools/MCPs stated: DESeq2.\nSteps:\n1. Write a CLAUDE.md with your pipeline, reference genome and analysis parameters (e.g. DESeq2).\n2. Keep it updated as the analysis changes.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Ming \"Tommy\" Tang — https://x.com/tangming2005/status/2102393729910997445 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Write a CLAUDE.md with your pipeline, reference genome and analysis parameters (e.g. DESeq2).",
    "Keep it updated as the analysis changes."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-22",
   "trend_score": 56.7,
   "sources": [
    {
     "author": "Ming \"Tommy\" Tang",
     "handle": "@tangming2005",
     "url": "https://x.com/tangming2005/status/2102393729910997445",
     "platform": "x",
     "date": "2026-09-22",
     "primary": true
    }
   ]
  },
  {
   "slug": "expensive-think-cheap-work",
   "url": "https://agentsetups.dev/use-case/expensive-think-cheap-work/",
   "title": "Expensive models think, cheap models implement",
   "summary": "GPT models plan via CloudHarness MCP; Pi/OMP implement with DeepSeek V4.1 Flash/GLM-5.3 via OpenCode Go for ~$10/mo.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Pi",
    "OMP (oh-my-pi)",
    "OpenCode"
   ],
   "models": [
    "DeepSeek V4.1 Flash",
    "GLM-5.3",
    "GPT-5.6 Sol"
   ],
   "tools": [
    "OpenCode Go",
    "CloudHarness MCP"
   ],
   "prompt": "Goal: Route thinking to strong models and implementation to cheap ones.\nSetup: agents used in source: Pi, OMP (oh-my-pi), OpenCode; tools/MCPs stated: OpenCode Go, CloudHarness MCP.\nSteps:\n1. Use expensive models for brainstorming, analysis, architecture, design and planning.\n2. If they need to inspect a repo, connect them via CloudHarness MCP.\n3. Throw the plan to Pi/OMP and let cheap models implement.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Duy /zuey/ — https://x.com/goon_nguyen/status/2102387489847869717",
   "steps": [
    "Use expensive models for brainstorming, analysis, architecture, design and planning.",
    "If they need to inspect a repo, connect them via CloudHarness MCP.",
    "Throw the plan to Pi/OMP and let cheap models implement."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-22",
   "trend_score": 56.5,
   "sources": [
    {
     "author": "Duy /zuey/",
     "handle": "@goon_nguyen",
     "url": "https://x.com/goon_nguyen/status/2102387489847869717",
     "platform": "x",
     "date": "2026-09-22",
     "primary": true
    }
   ]
  },
  {
   "slug": "wechat-daily-briefing",
   "url": "https://agentsetups.dev/use-case/wechat-daily-briefing/",
   "title": "Get daily briefings and follow-ups from WeChat",
   "summary": "A local-first WeChat intelligence hub: read-only CLI, Codex skills, searchable history, daily briefings.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "WeChat"
   ],
   "prompt": "Goal: Turn my WeChat chats into daily briefings and follow-ups.\nSetup: agents used in source: Codex; tools/MCPs stated: WeChat.\nSteps:\n1. Install the hub (read-only CLI).\n2. Use the Codex skills to search history.\n3. Get daily briefings, follow-ups and opportunity tracking.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Rion-Wu-tech — https://github.com/Rion-Wu-tech/wechat-intelligence-hub (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install the hub (read-only CLI).",
    "Use the Codex skills to search history.",
    "Get daily briefings, follow-ups and opportunity tracking."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-04",
   "trend_score": 56.4,
   "sources": [
    {
     "author": "Rion-Wu-tech",
     "handle": "Rion-Wu-tech",
     "url": "https://github.com/Rion-Wu-tech/wechat-intelligence-hub",
     "platform": "github",
     "date": "2026-09-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "opencode-ollama-sandbox",
   "url": "https://agentsetups.dev/use-case/opencode-ollama-sandbox/",
   "title": "Run OpenCode with local Ollama models in a sandbox",
   "summary": "On a 48GB MacBook: Docker sbx sandbox + OpenCode + Ollama with Qwen 3.8 27B for multi-hour runs.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "OpenCode"
   ],
   "models": [
    "Qwen 3.8 27B",
    "Gemma 4"
   ],
   "tools": [
    "Ollama",
    "Docker sbx"
   ],
   "prompt": "Goal: Set up local-model coding in a sandbox on my Mac.\nSetup: agents used in source: OpenCode; tools/MCPs stated: Ollama, Docker sbx.\nSteps:\n1. Install Docker Sandbox: brew trust docker/tap && brew install docker/tap/sbx.\n2. Install OpenCode: brew install anomalyco/tap/opencode. Install the Ollama app.\n3. Pull a workhorse model (e.g. ollama pull qwen3.8:27b-mxfp8, ~32GB) for long runs.\n4. Run OpenCode inside the sandbox so hallucinated commands can’t touch your machine.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: tensorsandtokens — https://tensorsandtokens.com/posts/opencode-ollama/",
   "steps": [
    "Install Docker Sandbox: brew trust docker/tap && brew install docker/tap/sbx.",
    "Install OpenCode: brew install anomalyco/tap/opencode. Install the Ollama app.",
    "Pull a workhorse model (e.g. ollama pull qwen3.8:27b-mxfp8, ~32GB) for long runs.",
    "Run OpenCode inside the sandbox so hallucinated commands can’t touch your machine."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-11",
   "trend_score": 54.1,
   "sources": [
    {
     "author": "tensorsandtokens",
     "handle": "tensorsandtokens.com",
     "url": "https://tensorsandtokens.com/posts/opencode-ollama/",
     "platform": "blog",
     "date": "2026-09-11",
     "primary": true
    },
    {
     "author": "etoxin",
     "handle": "etoxin",
     "url": "https://news.ycombinator.com/item?id=49652122",
     "platform": "hn",
     "date": "2026-09-11",
     "primary": false
    }
   ]
  },
  {
   "slug": "find-leads-weekly",
   "url": "https://agentsetups.dev/use-case/find-leads-weekly/",
   "title": "Find qualified leads from buying signals every Monday",
   "summary": "The agent asks about your niche, defines the signals that qualify prospects, writes leads to Notion, then schedules itself weekly.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "Claude",
    "Codex",
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "Notion"
   ],
   "prompt": "Goal: Find qualified leads for my business and repeat it weekly.\nSetup: agents used in source: Claude, Codex, Hermes Agent; tools/MCPs stated: Notion.\nSteps:\n1. Ask me a few questions to find my niche.\n2. Identify my target audience, where they hang out, and the signals that separate a good prospect from an okay one. Example for a content writer: raised money in the last 6 months, a blog with no posts in 3 months, a founder posting erratically.\n3. Write the leads to Notion.\n4. Turn the routine into a scheduled task that runs every Monday.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Favour is locked in. — https://x.com/FavourYusuf1/status/2101380484131422476",
   "steps": [
    "Ask me a few questions to find my niche.",
    "Identify my target audience, where they hang out, and the signals that separate a good prospect from an okay one. Example for a content writer: raised money in the last 6 months, a blog with no posts in 3 months, a founder posting erratically.",
    "Write the leads to Notion.",
    "Turn the routine into a scheduled task that runs every Monday."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-19",
   "trend_score": 54.0,
   "sources": [
    {
     "author": "Favour is locked in.",
     "handle": "@FavourYusuf1",
     "url": "https://x.com/FavourYusuf1/status/2101380484131422476",
     "platform": "x",
     "date": "2026-09-19",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-advanced-workflow",
   "url": "https://agentsetups.dev/use-case/claude-code-advanced-workflow/",
   "title": "Set up subagents, hooks, worktrees and headless mode",
   "summary": "A walkthrough of custom subagents, skills, hooks, worktrees, headless scripts, checkpoints and session branching.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Granola"
   ],
   "prompt": "Goal: Set up an advanced Claude Code workflow.\nSetup: agents used in source: Claude; tools/MCPs stated: Granola.\nSteps:\n1. Create custom subagents and advanced skills.\n2. Add pre/post tool hooks.\n3. Use git worktrees for parallel changes.\n4. Run headless scripts.\n5. Use checkpoints & rewind, continue sessions, and branch sessions.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Tech With Tim — https://x.com/TechWithTimm/status/2097308980628648349",
   "steps": [
    "Create custom subagents and advanced skills.",
    "Add pre/post tool hooks.",
    "Use git worktrees for parallel changes.",
    "Run headless scripts.",
    "Use checkpoints & rewind, continue sessions, and branch sessions."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-08",
   "trend_score": 53.6,
   "sources": [
    {
     "author": "Tech With Tim",
     "handle": "@TechWithTimm",
     "url": "https://x.com/TechWithTimm/status/2097308980628648349",
     "platform": "x",
     "date": "2026-09-08",
     "primary": true
    },
    {
     "author": "Tech With Tim",
     "handle": "@TechWithTimm",
     "url": "https://x.com/TechWithTimm/status/2104934232036434078",
     "platform": "x",
     "date": "2026-09-29",
     "primary": false
    }
   ]
  },
  {
   "slug": "n8n-score-form-submissions",
   "url": "https://agentsetups.dev/use-case/n8n-score-form-submissions/",
   "title": "Score form submissions with AI and alert on Telegram",
   "summary": "DeepSeek assigns category, intent, budget, urgency and priority; Telegram + Gmail + Sheets in parallel.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "n8n"
   ],
   "models": [
    "DeepSeek"
   ],
   "tools": [
    "n8n",
    "Telegram",
    "Gmail",
    "Google Sheets"
   ],
   "prompt": "Goal: Score every new form submission and alert me.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n, Telegram, Gmail, Google Sheets.\nSteps:\n1. Trigger on a new Google Sheets row from the form.\n2. Have the model return category, intent, budget, urgency and priority (use a Structured Output Parser).\n3. In parallel: Telegram alert, Gmail acknowledgement, and save the scored row.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Ravi_chandran_ — https://www.reddit.com/r/n8n/comments/1wt203w/built_an_n8n_workflow_that_scores_new_form/",
   "steps": [
    "Trigger on a new Google Sheets row from the form.",
    "Have the model return category, intent, budget, urgency and priority (use a Structured Output Parser).",
    "In parallel: Telegram alert, Gmail acknowledgement, and save the scored row."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-29",
   "trend_score": 53.6,
   "sources": [
    {
     "author": "/u/Ravi_chandran_",
     "handle": "/u/Ravi_chandran_",
     "url": "https://www.reddit.com/r/n8n/comments/1wt203w/built_an_n8n_workflow_that_scores_new_form/",
     "platform": "reddit",
     "date": "2026-09-29",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-directing-assistant-films",
   "url": "https://agentsetups.dev/use-case/grokbot-directing-assistant-films/",
   "title": "Use Grok Bot as directing assistant for short films",
   "summary": "@dvorahfr made three short films (steampunk, mafia, mythology) with Grok Bot as directing assistant and Grok Imagine Agent mode.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Grok Imagine"
   ],
   "prompt": "Goal: Make short AI films with an assistant handling direction.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Grok Imagine.\nSteps:\n1. Use Grok Bot as a directing assistant.\n2. Generate the footage with Grok Imagine in “Agent” mode.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Déborah — https://x.com/dvorahfr/status/2101379726359122193 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Use Grok Bot as a directing assistant.",
    "Generate the footage with Grok Imagine in “Agent” mode."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-19",
   "trend_score": 53.3,
   "sources": [
    {
     "author": "Déborah",
     "handle": "@dvorahfr",
     "url": "https://x.com/dvorahfr/status/2101379726359122193",
     "platform": "x",
     "date": "2026-09-19",
     "primary": true
    }
   ]
  },
  {
   "slug": "rewrite-go-to-rust-via-representation",
   "url": "https://agentsetups.dev/use-case/rewrite-go-to-rust-via-representation/",
   "title": "Rewrite 65k lines of Go in Rust for $400",
   "summary": "Extract the code as a data representation, operate on it, put it back as Rust; Fable orchestrates subagents, never writes code.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [
    "Fable 5"
   ],
   "tools": [],
   "prompt": "Goal: Do a large language-to-language rewrite cheaply.\nSetup: agents used in source: Claude.\nSteps:\n1. Ask the model to represent your code as graphs, ontologies, state machines, process charts, constraints or formulae.\n2. Operate on that representation: simplify state machines, remove hidden communication channels.\n3. Ask for the code back, in the new language.\n4. Forbid the main agent from reading or writing code itself; have it orchestrate subagents (Claude Code’s Glob, Grep, WebSearch) to save context on long runs.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Iurii Krasnoshchok — https://iurii.net/en/blog/posts/software-engineering/i-used-fable-to-rewrite-65kloc-to-rust/",
   "steps": [
    "Ask the model to represent your code as graphs, ontologies, state machines, process charts, constraints or formulae.",
    "Operate on that representation: simplify state machines, remove hidden communication channels.",
    "Ask for the code back, in the new language.",
    "Forbid the main agent from reading or writing code itself; have it orchestrate subagents (Claude Code’s Glob, Grep, WebSearch) to save context on long runs."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-01",
   "trend_score": 52.9,
   "sources": [
    {
     "author": "Iurii Krasnoshchok",
     "handle": "iurii.net",
     "url": "https://iurii.net/en/blog/posts/software-engineering/i-used-fable-to-rewrite-65kloc-to-rust/",
     "platform": "blog",
     "date": "2026-09-01",
     "primary": true
    },
    {
     "author": "aka-rider",
     "handle": "aka-rider",
     "url": "https://news.ycombinator.com/item?id=49526131",
     "platform": "hn",
     "date": "2026-09-01",
     "primary": false
    }
   ]
  },
  {
   "slug": "muse-call-many-stores-at-once",
   "url": "https://agentsetups.dev/use-case/muse-call-many-stores-at-once/",
   "title": "Have Muse call five stores at once to find stock",
   "summary": "@MattPRD’s Muse phoned five Tesla locations in parallel to find a Model YL his wife could see in person, and found one.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Meta Muse"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Find which nearby store actually has the item I want to see.\nSetup: agents used in source: Meta Muse.\nSteps:\n1. Tell Muse what you need (e.g. a specific car on display) and your area.\n2. Ask it to call all nearby locations at the same time.\n3. Get back which one has it. Use it for “type 2” tasks you would never have had the patience to do yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Matt Schlicht — https://x.com/MattPRD/status/2100015979212447907",
   "steps": [
    "Tell Muse what you need (e.g. a specific car on display) and your area.",
    "Ask it to call all nearby locations at the same time.",
    "Get back which one has it. Use it for “type 2” tasks you would never have had the patience to do yourself."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-16",
   "trend_score": 52.8,
   "sources": [
    {
     "author": "Matt Schlicht",
     "handle": "@MattPRD",
     "url": "https://x.com/MattPRD/status/2100015979212447907",
     "platform": "x",
     "date": "2026-09-16",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-chief-of-staff-prompt",
   "url": "https://agentsetups.dev/use-case/grokbot-chief-of-staff-prompt/",
   "title": "Hire a Grok Bot chief of staff with a 2-sentence prompt",
   "summary": "@coreyganim’s prompt makes the bot write its own system prompt, then suggest and brief the first bots to hire.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Set up a chief-of-staff bot that designs the rest of my bot team.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Prompt: “You’re my Chief of Staff bot. Give me a list of all the things a typical chief of staff would be responsible for, then suggest a system prompt you can install for yourself.”\n2. Add three lines: who you are and what your business does; what you want to accomplish in Grok Bot; “suggest the first bots you’d hire and what each one owns”.\n3. Let it hire and brief the sub-bots; don’t hand-write stuffed prompts. You may need fewer bots than you think.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Corey Ganim — https://x.com/coreyganim/status/2099808193178485185",
   "steps": [
    "Prompt: “You’re my Chief of Staff bot. Give me a list of all the things a typical chief of staff would be responsible for, then suggest a system prompt you can install for yourself.”",
    "Add three lines: who you are and what your business does; what you want to accomplish in Grok Bot; “suggest the first bots you’d hire and what each one owns”.",
    "Let it hire and brief the sub-bots; don’t hand-write stuffed prompts. You may need fewer bots than you think."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-15",
   "trend_score": 52.5,
   "sources": [
    {
     "author": "Corey Ganim",
     "handle": "@coreyganim",
     "url": "https://x.com/coreyganim/status/2099808193178485185",
     "platform": "x",
     "date": "2026-09-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "paint-mona-lisa-js-paint",
   "url": "https://agentsetups.dev/use-case/paint-mona-lisa-js-paint/",
   "title": "Have Claude paint the Mona Lisa in JS Paint",
   "summary": "One prompt: find the Mona Lisa, then replicate it with mouse movements and brushes in JS Paint in Chrome. 20 minutes.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "JS Paint",
    "Chrome"
   ],
   "prompt": "Goal: Test browser computer use on a creative task.\nSetup: agents used in source: Claude; tools/MCPs stated: JS Paint, Chrome.\nSteps:\n1. Prompt: “search for the picture of Mona Lisa, then replicate it using mouse movement and brushes in JS Paint using Chrome.”\n2. Let it draw (~20 minutes).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Kiana Ehsani — https://x.com/ehsanik/status/2102885216692162993",
   "steps": [
    "Prompt: “search for the picture of Mona Lisa, then replicate it using mouse movement and brushes in JS Paint using Chrome.”",
    "Let it draw (~20 minutes)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 51.9,
   "sources": [
    {
     "author": "Kiana Ehsani",
     "handle": "@ehsanik",
     "url": "https://x.com/ehsanik/status/2102885216692162993",
     "platform": "x",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "posting-history-skill",
   "url": "https://agentsetups.dev/use-case/posting-history-skill/",
   "title": "Write posts from your own posting history",
   "summary": "A skill reads your last 20 posts first, finds open threads and promises, then asks for the one missing fact.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Publora"
   ],
   "prompt": "Goal: Help me write my next post based on what I’ve already posted.\nSetup: agents used in source: Claude; tools/MCPs stated: Publora.\nSteps:\n1. Don’t give a draft first.\n2. Read my last twenty posts (list_posts).\n3. Find questions I asked and never came back to, and promises I made.\n4. Ask me for the one fact you can’t know, then draft.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Eugeniya Ivanova — https://dev.to/eugeniya_ivanova_4a58eadc/i-gave-an-agent-my-posting-history-it-found-a-promise-i-never-made-4n62",
   "steps": [
    "Don’t give a draft first.",
    "Read my last twenty posts (list_posts).",
    "Find questions I asked and never came back to, and promises I made.",
    "Ask me for the one fact you can’t know, then draft."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-08",
   "trend_score": 51.8,
   "sources": [
    {
     "author": "Eugeniya Ivanova",
     "handle": "@eugeniya_ivanova_4a58eadc",
     "url": "https://dev.to/eugeniya_ivanova_4a58eadc/i-gave-an-agent-my-posting-history-it-found-a-promise-i-never-made-4n62",
     "platform": "devto",
     "date": "2026-09-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "interactive-anatomy-from-dataset",
   "url": "https://agentsetups.dev/use-case/interactive-anatomy-from-dataset/",
   "title": "Build an interactive 3D anatomy explorer in 2 hours",
   "summary": "Point the model at an open anatomy dataset; Codex wrote the interface for all 206 bones — spin, explode, slice, click any bone.",
   "category": "education",
   "category_label": "Education",
   "agents": [
    "Codex"
   ],
   "models": [
    "GPT-6 Astra"
   ],
   "tools": [
    "Claude Code Artifact"
   ],
   "prompt": "Goal: Explore a subject I know nothing about with an interactive model.\nSetup: agents used in source: Codex; tools/MCPs stated: Claude Code Artifact.\nSteps:\n1. Point the model (here GPT-6 Astra) at an open anatomy dataset.\n2. Have Codex write the whole interface for all 206 bones: spin, explode, cut in half, click a bone to read about it.\n3. Ship it as an Artifact.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Emm | scenario.com — https://x.com/emmanuel_2m/status/2098058975195308130",
   "steps": [
    "Point the model (here GPT-6 Astra) at an open anatomy dataset.",
    "Have Codex write the whole interface for all 206 bones: spin, explode, cut in half, click a bone to read about it.",
    "Ship it as an Artifact."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-10",
   "trend_score": 51.5,
   "sources": [
    {
     "author": "Emm | scenario.com",
     "handle": "@emmanuel_2m",
     "url": "https://x.com/emmanuel_2m/status/2098058975195308130",
     "platform": "x",
     "date": "2026-09-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "tiktok-research-to-brief",
   "url": "https://agentsetups.dev/use-case/tiktok-research-to-brief/",
   "title": "Build a TikTok research-to-brief pipeline in 37 minutes",
   "summary": "Scrape TikTok, analyse the videos with AI and generate creative briefs for clients, built in Claude Code + Replit.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Replit"
   ],
   "prompt": "Goal: Build a research-to-brief pipeline for TikTok content.\nSetup: agents used in source: Claude; tools/MCPs stated: Replit.\nSteps:\n1. Scrape TikTok for the niche.\n2. Analyse the videos with AI.\n3. Generate creative briefs for clients.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Maliha Tasnim — https://x.com/this_is_tasnim/status/2100424146627055635 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Scrape TikTok for the niche.",
    "Analyse the videos with AI.",
    "Generate creative briefs for clients."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-17",
   "trend_score": 50.4,
   "sources": [
    {
     "author": "Maliha Tasnim",
     "handle": "@this_is_tasnim",
     "url": "https://x.com/this_is_tasnim/status/2100424146627055635",
     "platform": "x",
     "date": "2026-09-17",
     "primary": true
    }
   ]
  },
  {
   "slug": "dictate-gameboy-game",
   "url": "https://agentsetups.dev/use-case/dictate-gameboy-game/",
   "title": "Dictate a Game Boy game to Codex on your commute",
   "summary": "Using the modretro plugin in Codex, a dad built a Game Boy game mostly by dictation on a 30-min drive.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Codex"
   ],
   "models": [
    "Astra"
   ],
   "tools": [
    "modretro plugin"
   ],
   "prompt": "Goal: Build a Game Boy game by voice.\nSetup: agents used in source: Codex; tools/MCPs stated: modretro plugin.\nSteps:\n1. Install the modretro plugin in Codex.\n2. Dictate the game design and changes.\n3. Test in the simulator, then on real hardware.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Erik Natzke — https://x.com/Natzke/status/2105355307409145976 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install the modretro plugin in Codex.",
    "Dictate the game design and changes.",
    "Test in the simulator, then on real hardware."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 50.1,
   "sources": [
    {
     "author": "Erik Natzke",
     "handle": "@Natzke",
     "url": "https://x.com/Natzke/status/2105355307409145976",
     "platform": "x",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "cross-agent-session-memory",
   "url": "https://agentsetups.dev/use-case/cross-agent-session-memory/",
   "title": "Share work memory across Claude Code, Codex and Pi",
   "summary": "Nimrod reads each agent’s local session files into one SQLite log, injects a project brief at session start and answers queries over MCP.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex",
    "OpenCode"
   ],
   "models": [],
   "tools": [
    "Nimrod",
    "SQLite",
    "MCP",
    "fastembed"
   ],
   "prompt": "Goal: Stop re-explaining the same project to every new agent session.\nSetup: agents used in source: Claude, Codex, OpenCode; tools/MCPs stated: Nimrod, SQLite, MCP, fastembed.\nSteps:\n1. Read each agent’s own session store (JSONL or SQLite on disk) without writing to it.\n2. Extract what was asked, files touched, commands run and how it ended into one local SQLite database; no model writes to the log.\n3. Inject a short project brief at the start of each session.\n4. Expose search, recent sessions, timeline and session detail through MCP (FTS5 plus local embeddings).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/danilofs — https://www.reddit.com/r/PiAgent/comments/1wlixcy/crossagent_work_memory_for_claude_code_codex/",
   "steps": [
    "Read each agent’s own session store (JSONL or SQLite on disk) without writing to it.",
    "Extract what was asked, files touched, commands run and how it ended into one local SQLite database; no model writes to the log.",
    "Inject a short project brief at the start of each session.",
    "Expose search, recent sessions, timeline and session detail through MCP (FTS5 plus local embeddings)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 50.0,
   "sources": [
    {
     "author": "/u/danilofs",
     "handle": "/u/danilofs",
     "url": "https://www.reddit.com/r/PiAgent/comments/1wlixcy/crossagent_work_memory_for_claude_code_codex/",
     "platform": "reddit",
     "date": "2026-09-20",
     "primary": true
    }
   ]
  },
  {
   "slug": "stop-hook-runs-tests",
   "url": "https://agentsetups.dev/use-case/stop-hook-runs-tests/",
   "title": "Make Claude Code run tests before it can say “done”",
   "summary": "A 20-line Stop hook runs the test suite whenever Claude tries to finish and sends it back on failure.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Stop hook"
   ],
   "prompt": "Goal: Enforce passing tests before the agent finishes.\nSetup: agents used in source: Claude; tools/MCPs stated: Stop hook.\nSteps:\n1. Add a Stop hook that runs your tests when Claude tries to finish.\n2. If tests fail, return the failure so Claude goes back to work.\n3. Related: one rulebook that overrides everything, “lanes” for job size, and permissions.ask for git push.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: elijahmanlockedin112 — https://dev.to/elijahmanlockedin112/claude-code-said-done-my-tests-said-otherwise-heres-the-20-line-fix-jc",
   "steps": [
    "Add a Stop hook that runs your tests when Claude tries to finish.",
    "If tests fail, return the failure so Claude goes back to work.",
    "Related: one rulebook that overrides everything, “lanes” for job size, and permissions.ask for git push."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 49.7,
   "sources": [
    {
     "author": "elijahmanlockedin112",
     "handle": "@elijahmanlockedin112",
     "url": "https://dev.to/elijahmanlockedin112/claude-code-said-done-my-tests-said-otherwise-heres-the-20-line-fix-jc",
     "platform": "devto",
     "date": "2026-09-26",
     "primary": true
    },
    {
     "author": "Dhrupo Nil",
     "handle": "@dhrupo",
     "url": "https://dev.to/dhrupo/how-i-set-up-claude-code-one-rulebook-a-12-step-relay-to-use-it-daily-40gi",
     "platform": "devto",
     "date": "2026-10-07",
     "primary": false
    }
   ]
  },
  {
   "slug": "n8n-gmail-label-to-tasks",
   "url": "https://agentsetups.dev/use-case/n8n-gmail-label-to-tasks/",
   "title": "Turn labelled emails into tasks for $0",
   "summary": "Gmail label trigger → JavaScript parser → Google Sheets row: no more copy-pasting action items.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "n8n",
    "Gmail",
    "Google Sheets"
   ],
   "prompt": "Goal: Convert emails I label “Action Required” into tasks.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n, Gmail, Google Sheets.\nSteps:\n1. Gmail trigger on a label.\n2. Parse the email into task fields with a Code node.\n3. Add a row to a Google Sheets task database.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/VasuBuilds — https://www.reddit.com/r/n8n/comments/1wrf7pi/i_built_a_free_n8n_workflow_that_automatically/",
   "steps": [
    "Gmail trigger on a label.",
    "Parse the email into task fields with a Code node.",
    "Add a row to a Google Sheets task database."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-27",
   "trend_score": 48.6,
   "sources": [
    {
     "author": "/u/VasuBuilds",
     "handle": "/u/VasuBuilds",
     "url": "https://www.reddit.com/r/n8n/comments/1wrf7pi/i_built_a_free_n8n_workflow_that_automatically/",
     "platform": "reddit",
     "date": "2026-09-27",
     "primary": true
    }
   ]
  },
  {
   "slug": "ai-pop-star-news-song",
   "url": "https://agentsetups.dev/use-case/ai-pop-star-news-song/",
   "title": "Turn daily AI news into a song and music video",
   "summary": "Claude Code + Opus built the pipeline; the song was written by GPT and produced in Suno; video from 2 reference images.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Suno"
   ],
   "prompt": "Goal: Make a song and music video from yesterday’s news.\nSetup: agents used in source: Claude; tools/MCPs stated: Suno.\nSteps:\n1. Collect the day’s news.\n2. Write the song with a model and produce it in Suno.\n3. Generate the video from reference images and drop in the song.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Artforartsake99 — https://www.reddit.com/r/vibecoding/comments/1wuj7fm/i_vibe_coded_an_ai_pop_star_that_sings_the_daily/",
   "steps": [
    "Collect the day’s news.",
    "Write the song with a model and produce it in Suno.",
    "Generate the video from reference images and drop in the song."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 48.2,
   "sources": [
    {
     "author": "/u/Artforartsake99",
     "handle": "/u/Artforartsake99",
     "url": "https://www.reddit.com/r/vibecoding/comments/1wuj7fm/i_vibe_coded_an_ai_pop_star_that_sings_the_daily/",
     "platform": "reddit",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "build-own-computer-use-mcp",
   "url": "https://agentsetups.dev/use-case/build-own-computer-use-mcp/",
   "title": "Have your agent build its own computer-use MCP",
   "summary": "With no computer use built in, the agent wrote an MCP server for UI-TARS and gave itself the capability.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Command Code"
   ],
   "models": [
    "DeepSeek 4.1 Flash"
   ],
   "tools": [
    "UI-TARS"
   ],
   "prompt": "Goal: Give my agent computer use with an open-source tool.\nSetup: agents used in source: Command Code; tools/MCPs stated: UI-TARS.\nSteps:\n1. Ask the agent to use an open-source computer-use model (UI-TARS).\n2. Have it create an MCP server for it.\n3. Test it on a simple task.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: fatih kadir akın — https://x.com/fkadev/status/2100535225470038448",
   "steps": [
    "Ask the agent to use an open-source computer-use model (UI-TARS).",
    "Have it create an MCP server for it.",
    "Test it on a simple task."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-17",
   "trend_score": 47.9,
   "sources": [
    {
     "author": "fatih kadir akın",
     "handle": "@fkadev",
     "url": "https://x.com/fkadev/status/2100535225470038448",
     "platform": "x",
     "date": "2026-09-17",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-runs-dev-agency-chores",
   "url": "https://agentsetups.dev/use-case/hermes-runs-dev-agency-chores/",
   "title": "Let Hermes run PR reviews and client status updates",
   "summary": "A 20-dev agency gave Hermes repo, IRC and Cloudflare access on a VPS; it now handles PR reviews, daily status and builds after approval.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Hermes Agent"
   ],
   "models": [
    "DeepSeek V4.1 Flash"
   ],
   "tools": [
    "IRC",
    "MCP"
   ],
   "prompt": "Goal: Take the manual work out of PR reviews, daily status and client builds.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: IRC, MCP.\nSteps:\n1. Run Hermes on one VPS with access to the team’s chat, repos and infrastructure.\n2. Have it act only after you say yes to its proposals.\n3. For each new task, first create a skill with test cases, then do the task.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: The author found it token-hungry and saw issues moving CLI sessions to Slack.\nBased on: /u/xbxz — https://www.reddit.com/r/hermesagent/comments/1wijyx0/hermes_is_too_good_to_be_true_working_use_cases/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Run Hermes on one VPS with access to the team’s chat, repos and infrastructure.",
    "Have it act only after you say yes to its proposals.",
    "For each new task, first create a skill with test cases, then do the task."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-17",
   "trend_score": 47.8,
   "sources": [
    {
     "author": "/u/xbxz",
     "handle": "/u/xbxz",
     "url": "https://www.reddit.com/r/hermesagent/comments/1wijyx0/hermes_is_too_good_to_be_true_working_use_cases/",
     "platform": "reddit",
     "date": "2026-09-17",
     "primary": true
    }
   ]
  },
  {
   "slug": "two-local-agents-relay",
   "url": "https://agentsetups.dev/use-case/two-local-agents-relay/",
   "title": "Let two local models build an app in relay",
   "summary": "On an RTX 3070 Ti with Ollama, two small Qwen models passed work back and forth for 6 rounds.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [],
   "models": [
    "Qwen2.5-Coder",
    "Qwen3"
   ],
   "tools": [
    "Ollama"
   ],
   "prompt": "Goal: Test whether two local models can build an app without me.\nSetup: tools/MCPs stated: Ollama.\nSteps:\n1. Run two models in Ollama (a coder model and a general model).\n2. Have them pass work back and forth for a fixed number of rounds.\n3. Inspect the result honestly.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Mika Flowers — https://dev.to/mikachu/can-two-local-ai-agents-build-an-app-without-me-i-gave-them-6-rounds-to-find-out-ko1 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Run two models in Ollama (a coder model and a general model).",
    "Have them pass work back and forth for a fixed number of rounds.",
    "Inspect the result honestly."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-25",
   "trend_score": 47.8,
   "sources": [
    {
     "author": "Mika Flowers",
     "handle": "@mikachu",
     "url": "https://dev.to/mikachu/can-two-local-ai-agents-build-an-app-without-me-i-gave-them-6-rounds-to-find-out-ko1",
     "platform": "devto",
     "date": "2026-09-25",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-sdr-outbound-team",
   "url": "https://agentsetups.dev/use-case/grokbot-sdr-outbound-team/",
   "title": "Run outbound sales through one chief-of-staff bot",
   "summary": "SpaceXAI SDR workshop: 50 prepped prospects by 8am, a Gmail-trained writer bot, and a Salesforce trigger to pause sequences.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Gmail",
    "Salesforce"
   ],
   "prompt": "Goal: Have a Grok Bot team run my outbound prospecting.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Gmail, Salesforce.\nSteps:\n1. Talk only to a chief-of-staff bot that delegates everything.\n2. Have it deliver 50 prepped prospects at 8am, top 5 urgent, and block calendar time to act on them.\n3. Train a writer bot on your Gmail, weighted to recent positive replies.\n4. Split accounts (e.g. 200) across sub-bots that run in parallel.\n5. Add a Salesforce trigger: when a deal moves forward, remove its contacts from the outbound sequence.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: Second-hand summary of a vendor workshop.\nBased on: Shoopy — https://x.com/0xShoopy/status/2102398258035274210 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Talk only to a chief-of-staff bot that delegates everything.",
    "Have it deliver 50 prepped prospects at 8am, top 5 urgent, and block calendar time to act on them.",
    "Train a writer bot on your Gmail, weighted to recent positive replies.",
    "Split accounts (e.g. 200) across sub-bots that run in parallel.",
    "Add a Salesforce trigger: when a deal moves forward, remove its contacts from the outbound sequence."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-22",
   "trend_score": 47.4,
   "sources": [
    {
     "author": "Shoopy",
     "handle": "@0xShoopy",
     "url": "https://x.com/0xShoopy/status/2102398258035274210",
     "platform": "x",
     "date": "2026-09-22",
     "primary": true
    }
   ]
  },
  {
   "slug": "tiny-ai-civilisation-sim",
   "url": "https://agentsetups.dev/use-case/tiny-ai-civilisation-sim/",
   "title": "Simulate a tiny AI civilisation for $0.02",
   "summary": "48 citizens, Jev picking actions, GPT as world director, Devin building the Three.js world; code enforces the rules.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Devin"
   ],
   "models": [
    "Jev",
    "GPT"
   ],
   "tools": [
    "Three.js",
    "OpenRouter"
   ],
   "prompt": "Goal: Build a small agent-based simulation where models choose and code enforces.\nSetup: agents used in source: Devin; tools/MCPs stated: Three.js, OpenRouter.\nSteps:\n1. Give each citizen a role, skills, needs and memories.\n2. A decision model (Jev) gets each citizen’s state, observations and allowed actions, and picks the next action.\n3. A larger model acts as world director, proposing events (construction, weather, arrivals).\n4. Use a coding agent (Devin) to build the simulation and its Three.js world.\n5. Enforce rules in code: reject invalid actions; let local rules keep citizens moving while decisions are pending.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Lovepreet Singh — https://x.com/SinghDevHub/status/2102086884998664521",
   "steps": [
    "Give each citizen a role, skills, needs and memories.",
    "A decision model (Jev) gets each citizen’s state, observations and allowed actions, and picks the next action.",
    "A larger model acts as world director, proposing events (construction, weather, arrivals).",
    "Use a coding agent (Devin) to build the simulation and its Three.js world.",
    "Enforce rules in code: reject invalid actions; let local rules keep citizens moving while decisions are pending."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-21",
   "trend_score": 47.3,
   "sources": [
    {
     "author": "Lovepreet Singh",
     "handle": "@SinghDevHub",
     "url": "https://x.com/SinghDevHub/status/2102086884998664521",
     "platform": "x",
     "date": "2026-09-21",
     "primary": true
    }
   ]
  },
  {
   "slug": "roguelike-via-mcp-servers",
   "url": "https://agentsetups.dev/use-case/roguelike-via-mcp-servers/",
   "title": "Build a roguelike with Claude Code driving MCP tools",
   "summary": "Opus 5.5 in Claude Code used MCP servers for Meshy, Blender, ElevenLabs and Unity, from concept art to a Windows build.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Meshy",
    "Blender MCP",
    "Unity MCP",
    "ElevenLabs"
   ],
   "prompt": "Goal: Make a playable game without writing code.\nSetup: agents used in source: Claude; tools/MCPs stated: Meshy, Blender MCP, Unity MCP, ElevenLabs.\nSteps:\n1. Start from your concept art.\n2. Connect MCP servers: Meshy (3D models), Blender, ElevenLabs (audio) and Unity.\n3. Have Claude Code drive them to a playable build, then playtest it yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: VORTEX: AI Bros & AI Arena, Peak AI Buzz — https://x.com/VORTEX_Promos/status/2103622389573505119 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Start from your concept art.",
    "Connect MCP servers: Meshy (3D models), Blender, ElevenLabs (audio) and Unity.",
    "Have Claude Code drive them to a playable build, then playtest it yourself."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-25",
   "trend_score": 47.1,
   "sources": [
    {
     "author": "VORTEX: AI Bros & AI Arena, Peak AI Buzz",
     "handle": "@VORTEX_Promos",
     "url": "https://x.com/VORTEX_Promos/status/2103622389573505119",
     "platform": "x",
     "date": "2026-09-25",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-morning-workout-coach",
   "url": "https://agentsetups.dev/use-case/grokbot-morning-workout-coach/",
   "title": "Get a personalised morning workout from a Grok Bot coach",
   "summary": "Forge Coach asks about age, fitness, medical issues and equipment, then sends a daily workout with videos and adapts to done/skipped.",
   "category": "health",
   "category_label": "Health",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Know exactly what workout to do each day.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Add the coach bot to your Grok Bot.\n2. Answer its questions: age, fitness level, medical issues (and whether a doctor cleared you), weight, equipment, space to walk or run.\n3. Pick the time for your morning workout.\n4. Reply “done” or “skipped” daily so it adjusts.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Coffee and Grit — https://x.com/CoffeeNGrit/status/2104048659847324098",
   "steps": [
    "Add the coach bot to your Grok Bot.",
    "Answer its questions: age, fitness level, medical issues (and whether a doctor cleared you), weight, equipment, space to walk or run.",
    "Pick the time for your morning workout.",
    "Reply “done” or “skipped” daily so it adjusts."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-27",
   "trend_score": 46.6,
   "sources": [
    {
     "author": "Coffee and Grit",
     "handle": "@CoffeeNGrit",
     "url": "https://x.com/CoffeeNGrit/status/2104048659847324098",
     "platform": "x",
     "date": "2026-09-27",
     "primary": true
    },
    {
     "author": "Coffee and Grit",
     "handle": "@CoffeeNGrit",
     "url": "https://x.com/CoffeeNGrit/status/2110154913284002205",
     "platform": "x",
     "date": "2026-10-13",
     "primary": false
    }
   ]
  },
  {
   "slug": "hermes-daily-brief-sourced-lines",
   "url": "https://agentsetups.dev/use-case/hermes-daily-brief-sourced-lines/",
   "title": "Set up a sourced daily brief in Hermes Agent",
   "summary": "A paste-in prompt: Hermes asks for 3–5 topics and a time, shows a sample brief with a link per line, then schedules a cron job.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "cron"
   ],
   "prompt": "Goal: Get a daily brief on my topics, every line with a source.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: cron.\nSteps:\n1. Paste the prompt into a fresh Hermes chat. Rules: a source on every line, follow my topics exactly, create nothing until I say yes.\n2. It asks for three to five topics, then when and where the brief should arrive.\n3. It searches each topic once and shows a sample brief: one line per finding, link at the end, max ten lines.\n4. It shows the exact scheduled job (name, schedule, prompt, delivery) and waits for yes.\n5. After yes it creates the job with its cron tool and tells you how to list and remove it.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: witcheer — https://x.com/witcheer/status/2100954266038829170",
   "steps": [
    "Paste the prompt into a fresh Hermes chat. Rules: a source on every line, follow my topics exactly, create nothing until I say yes.",
    "It asks for three to five topics, then when and where the brief should arrive.",
    "It searches each topic once and shows a sample brief: one line per finding, link at the end, max ten lines.",
    "It shows the exact scheduled job (name, schedule, prompt, delivery) and waits for yes.",
    "After yes it creates the job with its cron tool and tells you how to list and remove it."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-18",
   "trend_score": 46.2,
   "sources": [
    {
     "author": "witcheer",
     "handle": "@witcheer",
     "url": "https://x.com/witcheer/status/2100954266038829170",
     "platform": "x",
     "date": "2026-09-18",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-widgets-iphone-home-screen",
   "url": "https://agentsetups.dev/use-case/claude-widgets-iphone-home-screen/",
   "title": "Let Claude build widgets on your iPhone Home Screen",
   "summary": "Through an MCP for the Glance app, Claude creates, lays out and later updates Home Screen widgets, e.g. the two latest Anthropic stories.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Glance",
    "MCP",
    "WidgetKit"
   ],
   "prompt": "Goal: Get live, personal widgets on my phone without building them myself.\nSetup: agents used in source: Claude; tools/MCPs stated: Glance, MCP, WidgetKit.\nSteps:\n1. Connect Claude to the Glance app through its MCP.\n2. Ask for a widget in plain language, e.g. “a Home Screen widget that shows me the two latest Claude/Anthropic stories”.\n3. Let Claude choose the layout and populate it, then update the content later through the MCP.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Dense-Map-406 — https://www.reddit.com/r/ClaudeCowork/comments/1wu6mgx/i_built_a_way_to_connect_claude_to_your_iphone/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Connect Claude to the Glance app through its MCP.",
    "Ask for a widget in plain language, e.g. “a Home Screen widget that shows me the two latest Claude/Anthropic stories”.",
    "Let Claude choose the layout and populate it, then update the content later through the MCP."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 45.5,
   "sources": [
    {
     "author": "/u/Dense-Map-406",
     "handle": "/u/Dense-Map-406",
     "url": "https://www.reddit.com/r/ClaudeCowork/comments/1wu6mgx/i_built_a_way_to_connect_claude_to_your_iphone/",
     "platform": "reddit",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "verify-agent-done-claims",
   "url": "https://agentsetups.dev/use-case/verify-agent-done-claims/",
   "title": "Gate “done” claims behind a real test run",
   "summary": "One dev found 69% of “done” claims false, another 35% of “tests pass” claims; both re-run checks before the agent may stop.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex",
    "Cursor",
    "Gemini CLI"
   ],
   "models": [],
   "tools": [
    "Stop hook"
   ],
   "prompt": "Goal: Stop trusting an agent’s word that the work is finished.\nSetup: agents used in source: Claude, Codex, Cursor, Gemini CLI; tools/MCPs stated: Stop hook.\nSteps:\n1. Measure first: scan your local transcripts for “done” / “tests pass” claims and check them.\n2. Add a Stop hook (Claude Code, Codex CLI and others have one) that runs checks when the agent claims completion: fast checks always, the full suite only when the claim warrants it.\n3. Watch for green-without-fix: skipped or deleted tests, weakened assertions.\n4. In CLAUDE.md / AGENTS.md: “Before claiming checks pass, re-run them after your last edit” — ask for proof, not a verdict.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Raimondas Lencevicius — https://dev.to/raimondasl/69-of-my-coding-agents-done-claims-werent-here-is-the-gate-i-put-in-front-of-them-lho",
   "steps": [
    "Measure first: scan your local transcripts for “done” / “tests pass” claims and check them.",
    "Add a Stop hook (Claude Code, Codex CLI and others have one) that runs checks when the agent claims completion: fast checks always, the full suite only when the claim warrants it.",
    "Watch for green-without-fix: skipped or deleted tests, weakened assertions.",
    "In CLAUDE.md / AGENTS.md: “Before claiming checks pass, re-run them after your last edit” — ask for proof, not a verdict."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-21",
   "trend_score": 45.3,
   "sources": [
    {
     "author": "Raimondas Lencevicius",
     "handle": "@raimondasl",
     "url": "https://dev.to/raimondasl/69-of-my-coding-agents-done-claims-werent-here-is-the-gate-i-put-in-front-of-them-lho",
     "platform": "devto",
     "date": "2026-09-21",
     "primary": true
    },
    {
     "author": "Vinzenz Eiberger",
     "handle": "@vinzenz_eiberger",
     "url": "https://dev.to/vinzenz_eiberger/i-checked-101-tests-pass-claims-from-my-ai-coding-agents-35-werent-true-h6n",
     "platform": "devto",
     "date": "2026-09-24",
     "primary": false
    }
   ]
  },
  {
   "slug": "audit-fb-ads-agency",
   "url": "https://agentsetups.dev/use-case/audit-fb-ads-agency/",
   "title": "Audit your Facebook ads agency with a data warehouse",
   "summary": "Put ads, PostHog and CRM data in a warehouse, have a vision model analyse creatives, then let Claude Code find what works.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "PostHog",
    "S3",
    "Facebook Ads API"
   ],
   "prompt": "Goal: Audit my ads agency’s work using my own data.\nSetup: agents used in source: Claude; tools/MCPs stated: PostHog, S3, Facebook Ads API.\nSteps:\n1. Get your ads, PostHog and CRM data into a data warehouse.\n2. Give Claude Code access to the warehouse and an S3 bucket for storage.\n3. Pull all ad creative and its conversion data.\n4. Have a vision model analyse the creative, ad text and landing pages, and build a database from it.\n5. Have Claude Code analyse that database to find what is and isn’t working.\n6. Optionally give it a Facebook Ads API key to modify campaigns based on the analysis.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Cody Schneider — https://x.com/codyschneider/status/2097369443344994336",
   "steps": [
    "Get your ads, PostHog and CRM data into a data warehouse.",
    "Give Claude Code access to the warehouse and an S3 bucket for storage.",
    "Pull all ad creative and its conversion data.",
    "Have a vision model analyse the creative, ad text and landing pages, and build a database from it.",
    "Have Claude Code analyse that database to find what is and isn’t working.",
    "Optionally give it a Facebook Ads API key to modify campaigns based on the analysis."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-08",
   "trend_score": 45.0,
   "sources": [
    {
     "author": "Cody Schneider",
     "handle": "@codyschneider",
     "url": "https://x.com/codyschneider/status/2097369443344994336",
     "platform": "x",
     "date": "2026-09-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-weekly-meal-planner",
   "url": "https://agentsetups.dev/use-case/grokbot-weekly-meal-planner/",
   "title": "Make a meal-planning bot for your household",
   "summary": "@TimDOES made “Bot My Meals”, a Grok Bot that creates new meals for him and his wife every week.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Automate weekly meal planning.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Create a meal-planning bot that generates new meals every week.\n2. Share it as a template if others want it.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: TimDOES — https://x.com/TimDOES/status/2104785657394839990 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Create a meal-planning bot that generates new meals every week.",
    "Share it as a template if others want it."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-29",
   "trend_score": 45.0,
   "sources": [
    {
     "author": "TimDOES",
     "handle": "@TimDOES",
     "url": "https://x.com/TimDOES/status/2104785657394839990",
     "platform": "x",
     "date": "2026-09-29",
     "primary": true
    }
   ]
  },
  {
   "slug": "remake-classic-game",
   "url": "https://agentsetups.dev/use-case/remake-classic-game/",
   "title": "Remake a classic game with AI code, art and music",
   "summary": "Claude Code + Codex + GPT Image 2 + Suno rebuilt a MindMaze-style game; another compared models on a Theme Park clone.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Opus 5.5",
    "GPT-6.1 Sol"
   ],
   "tools": [
    "GPT Image 2",
    "Suno"
   ],
   "prompt": "Goal: Build a spiritual successor to a classic game.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: GPT Image 2, Suno.\nSteps:\n1. Share the idea and a little input; decide what is feasible for v1 and write a spec.\n2. Build code with the agents; generate artwork and music with image/music models.\n3. Iterate (Opus took 3 iterations in the Theme Park clone).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: John Bura — https://x.com/johnbura/status/2102463302475637087 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Share the idea and a little input; decide what is feasible for v1 and write a spec.",
    "Build code with the agents; generate artwork and music with image/music models.",
    "Iterate (Opus took 3 iterations in the Theme Park clone)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-22",
   "trend_score": 43.9,
   "sources": [
    {
     "author": "John Bura",
     "handle": "@johnbura",
     "url": "https://x.com/johnbura/status/2102463302475637087",
     "platform": "x",
     "date": "2026-09-22",
     "primary": true
    },
    {
     "author": "René Schulte",
     "handle": "@rschu",
     "url": "https://x.com/rschu/status/2105708801135382874",
     "platform": "x",
     "date": "2026-10-01",
     "primary": false
    }
   ]
  },
  {
   "slug": "coding-agent-results-to-telegram",
   "url": "https://agentsetups.dev/use-case/coding-agent-results-to-telegram/",
   "title": "Get coding-agent results on Telegram via Hermes",
   "summary": "hermes mcp serve lets Claude Code or Codex send “what changed / passed / needs review” to your phone.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "Claude",
    "Codex",
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "Telegram",
    "hermes mcp serve"
   ],
   "prompt": "Goal: When a coding task finishes, send me the result on Telegram.\nSetup: agents used in source: Claude, Codex, Hermes Agent; tools/MCPs stated: Telegram, hermes mcp serve.\nSteps:\n1. Run hermes mcp serve to connect an MCP-capable coding agent to Hermes messaging tools.\n2. Keep the Hermes gateway running.\n3. Have the coding agent send: what changed, what passed, what needs review.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Hermes Agent Super-Intel — https://x.com/BkashJosi/status/2103108439090315314",
   "steps": [
    "Run hermes mcp serve to connect an MCP-capable coding agent to Hermes messaging tools.",
    "Keep the Hermes gateway running.",
    "Have the coding agent send: what changed, what passed, what needs review."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 43.3,
   "sources": [
    {
     "author": "Hermes Agent Super-Intel",
     "handle": "@BkashJosi",
     "url": "https://x.com/BkashJosi/status/2103108439090315314",
     "platform": "x",
     "date": "2026-09-24",
     "primary": true
    }
   ]
  },
  {
   "slug": "programmatic-seo-158-pages",
   "url": "https://agentsetups.dev/use-case/programmatic-seo-158-pages/",
   "title": "Launch a programmatic SEO site: 158 pages indexed in 7 days",
   "summary": "Find a niche with a structured-data angle, verify the data is extractable, then generate hundreds of pages.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Claude"
   ],
   "models": [
    "Fable"
   ],
   "tools": [],
   "prompt": "Goal: Build a programmatic SEO site in a niche with a structured-data angle.\nSetup: agents used in source: Claude.\nSteps:\n1. Find a niche with high search volume and a programmatic angle, where structured data beats the current results.\n2. Have Claude Code check whether all the needed data can be extracted.\n3. Set up systematic rechecks to confirm every fetched data point is valid.\n4. Programmatically produce pages across the full product range.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Chris Panteli (Co-Founder) — https://x.com/Linkifi_/status/2104846207335985296",
   "steps": [
    "Find a niche with high search volume and a programmatic angle, where structured data beats the current results.",
    "Have Claude Code check whether all the needed data can be extracted.",
    "Set up systematic rechecks to confirm every fetched data point is valid.",
    "Programmatically produce pages across the full product range."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-29",
   "trend_score": 43.0,
   "sources": [
    {
     "author": "Chris Panteli (Co-Founder)",
     "handle": "@Linkifi_",
     "url": "https://x.com/Linkifi_/status/2104846207335985296",
     "platform": "x",
     "date": "2026-09-29",
     "primary": true
    }
   ]
  },
  {
   "slug": "podcast-analytics-dashboard",
   "url": "https://agentsetups.dev/use-case/podcast-analytics-dashboard/",
   "title": "Build a podcast analytics pipeline and dashboard",
   "summary": "A first-time Claude Code user combined YouTube’s 3 APIs, Spotify for Creators and Open Podcast in one dashboard.",
   "category": "data-analysis",
   "category_label": "Data analysis",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "YouTube APIs",
    "Spotify for Creators",
    "Open Podcast"
   ],
   "prompt": "Goal: Build a data pipeline and content analytics dashboard for my shows.\nSetup: agents used in source: Claude; tools/MCPs stated: YouTube APIs, Spotify for Creators, Open Podcast.\nSteps:\n1. Pull YouTube’s 3 APIs for each show’s channel.\n2. Pull Spotify for Creators data for all shows.\n3. Use Open Podcast’s free connector.\n4. Combine everything into one dashboard.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Aaron Orendorff — https://x.com/AaronOrendorff/status/2105005028834718067",
   "steps": [
    "Pull YouTube’s 3 APIs for each show’s channel.",
    "Pull Spotify for Creators data for all shows.",
    "Use Open Podcast’s free connector.",
    "Combine everything into one dashboard."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-29",
   "trend_score": 42.6,
   "sources": [
    {
     "author": "Aaron Orendorff",
     "handle": "@AaronOrendorff",
     "url": "https://x.com/AaronOrendorff/status/2105005028834718067",
     "platform": "x",
     "date": "2026-09-29",
     "primary": true
    }
   ]
  },
  {
   "slug": "clear-admin-backlog",
   "url": "https://agentsetups.dev/use-case/clear-admin-backlog/",
   "title": "Clear your admin backlog: Ramp, equipment, insurance",
   "summary": "Grok Bot closed out everything in Ramp, found and negotiated equipment and caught an insurance liability.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude",
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Ramp"
   ],
   "prompt": "Goal: Close out my outstanding admin tasks.\nSetup: agents used in source: Claude, Grok Bot; tools/MCPs stated: Ramp.\nSteps:\n1. Give the agent your outstanding admin items (e.g. Ramp).\n2. Have it find and negotiate for equipment you need.\n3. Ask it to review policies for liabilities.\n4. Variant: with a Vapi key, it called 5 repair shops in parallel and booked a flat-tyre repair.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: John Aguillard — https://x.com/JohnAguillard/status/2095985651296469356 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give the agent your outstanding admin items (e.g. Ramp).",
    "Have it find and negotiate for equipment you need.",
    "Ask it to review policies for liabilities.",
    "Variant: with a Vapi key, it called 5 repair shops in parallel and booked a flat-tyre repair."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-04",
   "trend_score": 42.4,
   "sources": [
    {
     "author": "John Aguillard",
     "handle": "@JohnAguillard",
     "url": "https://x.com/JohnAguillard/status/2095985651296469356",
     "platform": "x",
     "date": "2026-09-04",
     "primary": true
    },
    {
     "author": "Mike Fishbein",
     "handle": "@mfishbein",
     "url": "https://x.com/mfishbein/status/2097319292614099229",
     "platform": "x",
     "date": "2026-09-08",
     "primary": false
    }
   ]
  },
  {
   "slug": "kiro-builds-claude-reviews-rigor",
   "url": "https://agentsetups.dev/use-case/kiro-builds-claude-reviews-rigor/",
   "title": "Set rigor levels when Kiro builds and Claude reviews",
   "summary": "A non-typing builder: Kiro writes, Claude reviews, she decides. Both agents over-hardened a throwaway; a rigor budget fixed it.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Kiro"
   ],
   "models": [],
   "tools": [
    "AWS Bedrock AgentCore",
    "Strands"
   ],
   "prompt": "Goal: Direct two agents without over-engineering throwaway code.\nSetup: agents used in source: Claude, Kiro; tools/MCPs stated: AWS Bedrock AgentCore, Strands.\nSteps:\n1. Split roles: Kiro builds, Claude reviews against your rules, you validate and decide.\n2. Tag throwaway code explicitly, and tell both agents what the tag means; they won’t watch it for you.\n3. Compliance gate: ~10 minutes before implementing, check you’re allowed to build it the way you intend.\n4. Hand-check: ~20 minutes after the automated suite, test by hand.\n5. Rigor budget: full rigor for code that survives, working rigor for features, spike rigor for throwaways.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Earl Grey — https://dev.to/earlgreyhot1701d/block-zero-oh-no-claude-kiro-and-i-over-engineered-the-throwaway-5d42",
   "steps": [
    "Split roles: Kiro builds, Claude reviews against your rules, you validate and decide.",
    "Tag throwaway code explicitly, and tell both agents what the tag means; they won’t watch it for you.",
    "Compliance gate: ~10 minutes before implementing, check you’re allowed to build it the way you intend.",
    "Hand-check: ~20 minutes after the automated suite, test by hand.",
    "Rigor budget: full rigor for code that survives, working rigor for features, spike rigor for throwaways."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-01",
   "trend_score": 41.3,
   "sources": [
    {
     "author": "Earl Grey",
     "handle": "@earlgreyhot1701d",
     "url": "https://dev.to/earlgreyhot1701d/block-zero-oh-no-claude-kiro-and-i-over-engineered-the-throwaway-5d42",
     "platform": "devto",
     "date": "2026-09-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-cycling-route-with-stops",
   "url": "https://agentsetups.dev/use-case/grokbot-cycling-route-with-stops/",
   "title": "Have your coach bot plan a ride with food stops",
   "summary": "@mikepat711’s cycling-coach Grok Bot mapped a course to hit the target miles and climbing, with food and water stops in the file.",
   "category": "health",
   "category_label": "Health",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Plan a training ride that hits my coach’s distance and elevation.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Give the coach bot the assignment (miles and elevation).\n2. Ask it to map a course and program food and water stops into the route file.\n3. Have it upload the file to your ride app.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Mike P — https://x.com/mikepat711/status/2099226611476283790 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give the coach bot the assignment (miles and elevation).",
    "Ask it to map a course and program food and water stops into the route file.",
    "Have it upload the file to your ride app."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-13",
   "trend_score": 40.7,
   "sources": [
    {
     "author": "Mike P",
     "handle": "@mikepat711",
     "url": "https://x.com/mikepat711/status/2099226611476283790",
     "platform": "x",
     "date": "2026-09-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "instagram-bookmarks-searchable-diary",
   "url": "https://agentsetups.dev/use-case/instagram-bookmarks-searchable-diary/",
   "title": "Turn Instagram bookmarks into a searchable diary",
   "summary": "Built with Codex + Muse Spark: an agent goes through all your saved Instagram posts and turns them into a searchable diary.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Codex",
    "Meta Muse"
   ],
   "models": [
    "Muse Spark"
   ],
   "tools": [
    "Instagram"
   ],
   "prompt": "Goal: Make years of Instagram saves findable.\nSetup: agents used in source: Codex, Meta Muse; tools/MCPs stated: Instagram.\nSteps:\n1. Build an agent (here with Codex, using Muse Spark) that reads all your Instagram bookmarks.\n2. Have it turn them into a searchable diary.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Priyaa — https://x.com/pritopian/status/2097471188838813842 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Build an agent (here with Codex, using Muse Spark) that reads all your Instagram bookmarks.",
    "Have it turn them into a searchable diary."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-08",
   "trend_score": 40.1,
   "sources": [
    {
     "author": "Priyaa",
     "handle": "@pritopian",
     "url": "https://x.com/pritopian/status/2097471188838813842",
     "platform": "x",
     "date": "2026-09-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "obsidian-vault-trading-brain",
   "url": "https://agentsetups.dev/use-case/obsidian-vault-trading-brain/",
   "title": "Give your trading bot an Obsidian second brain",
   "summary": "Grok Bot and Claude Code built a 28,728-file vault from scattered charts, screenshots and notes; it then refused a trade.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Claude",
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Obsidian"
   ],
   "prompt": "Goal: Consolidate my scattered trading research into a vault my bot consults.\nSetup: agents used in source: Claude, Grok Bot; tools/MCPs stated: Obsidian.\nSteps:\n1. Gather charts, screenshots and notes from their separate places.\n2. Have the agents build an Obsidian vault from them.\n3. Have the trading bot check the vault before acting.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Spike 1% — https://x.com/SpikeCalls/status/2095985761439137915 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Gather charts, screenshots and notes from their separate places.",
    "Have the agents build an Obsidian vault from them.",
    "Have the trading bot check the vault before acting."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-04",
   "trend_score": 38.5,
   "sources": [
    {
     "author": "Spike 1%",
     "handle": "@SpikeCalls",
     "url": "https://x.com/SpikeCalls/status/2095985761439137915",
     "platform": "x",
     "date": "2026-09-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-routines-non-coder",
   "url": "https://agentsetups.dev/use-case/claude-routines-non-coder/",
   "title": "Run daily routines in Claude without writing code",
   "summary": "A 10 a.m. analytics check, a Mon/Wed/Fri drafts file and an HN digest, set up in plain English.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Claude Code routines",
    "scheduled tasks"
   ],
   "prompt": "Goal: Set up small recurring routines in plain English.\nSetup: agents used in source: Claude; tools/MCPs stated: Claude Code routines, scheduled tasks.\nSteps:\n1. Create a 10 a.m. routine that checks your numbers so you don’t spend hours analysing.\n2. Add a Mon/Wed/Fri routine that maintains a file of future post ideas.\n3. Add a scheduled task that digests Hacker News for you.\n4. Note: local routines need your computer awake and online.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Eugeniya Ivanova — https://dev.to/eugeniya_ivanova_4a58eadc/i-didnt-come-to-claude-through-code-i-came-through-a-10-am-routine-3e14",
   "steps": [
    "Create a 10 a.m. routine that checks your numbers so you don’t spend hours analysing.",
    "Add a Mon/Wed/Fri routine that maintains a file of future post ideas.",
    "Add a scheduled task that digests Hacker News for you.",
    "Note: local routines need your computer awake and online."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-18",
   "trend_score": 38.0,
   "sources": [
    {
     "author": "Eugeniya Ivanova",
     "handle": "@eugeniya_ivanova_4a58eadc",
     "url": "https://dev.to/eugeniya_ivanova_4a58eadc/i-didnt-come-to-claude-through-code-i-came-through-a-10-am-routine-3e14",
     "platform": "devto",
     "date": "2026-09-18",
     "primary": true
    }
   ]
  },
  {
   "slug": "beat-synced-promo-reels",
   "url": "https://agentsetups.dev/use-case/beat-synced-promo-reels/",
   "title": "Make beat-synced promo reels with a Claude Code skill",
   "summary": "An MIT-licensed Claude Code skill makes beat-synced promo reels; another skill turns a repo into launch films.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Make a beat-synced promo reel for my product.\nSetup: agents used in source: Claude.\nSteps:\n1. Install the beat-synced reel skill from the author’s repo.\n2. Give it your product footage and a track.\n3. Have it cut on the beat and render.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Ivan Morgillo — https://x.com/hamen/status/2105191686028546289 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install the beat-synced reel skill from the author’s repo.",
    "Give it your product footage and a track.",
    "Have it cut on the beat and render."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 37.8,
   "sources": [
    {
     "author": "Ivan Morgillo",
     "handle": "@hamen",
     "url": "https://x.com/hamen/status/2105191686028546289",
     "platform": "x",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-nightly-fact-check-posts",
   "url": "https://agentsetups.dev/use-case/grokbot-nightly-fact-check-posts/",
   "title": "Have Grok Bot fact-check your X posts every night",
   "summary": "@DrPhiltill’s nightly Grok Bot fact-check of all his X discussions caught one highly valuable correction so far.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "X"
   ],
   "prompt": "Goal: Catch mistakes in what I post publicly.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: X.\nSteps:\n1. Ask Grok Bot to fact-check all your discussions on X every night (the author shares his prompt in the post image).\n2. Review the corrections it flags.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Phil Metzger — https://x.com/DrPhiltill/status/2101309065368351195 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask Grok Bot to fact-check all your discussions on X every night (the author shares his prompt in the post image).",
    "Review the corrections it flags."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-19",
   "trend_score": 37.4,
   "sources": [
    {
     "author": "Phil Metzger",
     "handle": "@DrPhiltill",
     "url": "https://x.com/DrPhiltill/status/2101309065368351195",
     "platform": "x",
     "date": "2026-09-19",
     "primary": true
    }
   ]
  },
  {
   "slug": "mp3-renamer-mac-app",
   "url": "https://agentsetups.dev/use-case/mp3-renamer-mac-app/",
   "title": "Build a Mac utility with Figma MCP and Codex",
   "summary": "An afternoon mp3 renamer: add covers, sanitise and format metadata, rename files. Built with the Figma MCP and Codex.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "Figma MCP"
   ],
   "prompt": "Goal: Replace a manual file-tidying habit with a small native app.\nSetup: agents used in source: Codex; tools/MCPs stated: Figma MCP.\nSteps:\n1. Design the UI in Figma and expose it via the Figma MCP.\n2. Have Codex build the Mac app: add covers, sanitise and format metadata, rename files to your format.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Tom Lowry — https://x.com/negativespaceca/status/2101842286560563407 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Design the UI in Figma and expose it via the Figma MCP.",
    "Have Codex build the Mac app: add covers, sanitise and format metadata, rename files to your format."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-21",
   "trend_score": 37.4,
   "sources": [
    {
     "author": "Tom Lowry",
     "handle": "@negativespaceca",
     "url": "https://x.com/negativespaceca/status/2101842286560563407",
     "platform": "x",
     "date": "2026-09-21",
     "primary": true
    }
   ]
  },
  {
   "slug": "amp-orbs-ship-three-features",
   "url": "https://agentsetups.dev/use-case/amp-orbs-ship-three-features/",
   "title": "Ship several features in a day with Amp Orbs",
   "summary": "A solo maker shipped 3 features to Keep (website change monitor, read-only shared notes, transcribed voice notes) using Amp Orbs.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Amp"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Ship several product features in parallel in one day.\nSetup: agents used in source: Amp.\nSteps:\n1. Spin up an Amp Orb per feature (here: website change monitor, read-only note sharing, transcribed voice notes).\n2. Review and merge each, plus bug fixes along the way.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Ian Nuttall — https://x.com/iannuttall/status/2098049708040016193 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Spin up an Amp Orb per feature (here: website change monitor, read-only note sharing, transcribed voice notes).",
    "Review and merge each, plus bug fixes along the way."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-10",
   "trend_score": 37.1,
   "sources": [
    {
     "author": "Ian Nuttall",
     "handle": "@iannuttall",
     "url": "https://x.com/iannuttall/status/2098049708040016193",
     "platform": "x",
     "date": "2026-09-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "antigravity-gemini-fix-phone-adb",
   "url": "https://agentsetups.dev/use-case/antigravity-gemini-fix-phone-adb/",
   "title": "Have Gemini debug a phone glitch over ADB",
   "summary": "In Antigravity, Gemini queried settings over ADB, then pulled and disassembled OEM code to find a debug overlay nobody documented.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Antigravity"
   ],
   "models": [],
   "tools": [
    "ADB",
    "Android"
   ],
   "prompt": "Goal: Fix a strange Android behaviour Google search can’t explain.\nSetup: agents used in source: Antigravity; tools/MCPs stated: ADB, Android.\nSteps:\n1. Connect the phone over USB and ask the agent in Antigravity for help.\n2. Let it query runtime settings via adb shell settings get … before guessing.\n3. If the cause is in proprietary OEM code, have it pull the APK and parse the DEX string table to find the responsible code.\n4. Apply the setting change it identifies.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Omar Afifi — https://dev.to/omarafifi/my-phone-broke-and-gemini-fixed-it-329l (summarised from source; the source has no explicit step list)",
   "steps": [
    "Connect the phone over USB and ask the agent in Antigravity for help.",
    "Let it query runtime settings via adb shell settings get … before guessing.",
    "If the cause is in proprietary OEM code, have it pull the APK and parse the DEX string table to find the responsible code.",
    "Apply the setting change it identifies."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-09",
   "trend_score": 36.0,
   "sources": [
    {
     "author": "Omar Afifi",
     "handle": "@omarafifi",
     "url": "https://dev.to/omarafifi/my-phone-broke-and-gemini-fixed-it-329l",
     "platform": "devto",
     "date": "2026-09-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "vps-dokploy-mcp-lovable-alternative",
   "url": "https://agentsetups.dev/use-case/vps-dokploy-mcp-lovable-alternative/",
   "title": "Deploy apps by chat with a $5 VPS and Dokploy MCP",
   "summary": "An MCP gateway next to Dokploy lets claude.ai or ChatGPT write a page, push to GitHub and deploy it on a subdomain.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Dokploy",
    "Junctio",
    "GitHub",
    "Docker Compose"
   ],
   "prompt": "Goal: Get “build and deploy” by chat without a paid app builder.\nSetup: agents used in source: Claude; tools/MCPs stated: Dokploy, Junctio, GitHub, Docker Compose.\nSteps:\n1. Rent any $5 VPS (Dokploy wants ~2 GB RAM) and install Dokploy.\n2. Run an MCP gateway container next to it (the author wrote Junctio) holding the Dokploy API key; claude.ai and ChatGPT can’t spawn local stdio servers.\n3. Connect the gateway to your AI client.\n4. Prompt: “Build a landing page for X, push it to my GitHub, deploy it on Dokploy under x.example.com.”\n5. There is no live preview or visual editor; the same trick works for any API with an OpenAPI spec.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Web Artisan — https://dev.to/k2sodev/i-almost-replaced-lovable-with-a-5-vps-dokploy-and-one-mcp-gateway-3mn9",
   "steps": [
    "Rent any $5 VPS (Dokploy wants ~2 GB RAM) and install Dokploy.",
    "Run an MCP gateway container next to it (the author wrote Junctio) holding the Dokploy API key; claude.ai and ChatGPT can’t spawn local stdio servers.",
    "Connect the gateway to your AI client.",
    "Prompt: “Build a landing page for X, push it to my GitHub, deploy it on Dokploy under x.example.com.”",
    "There is no live preview or visual editor; the same trick works for any API with an OpenAPI spec."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-18",
   "trend_score": 36.0,
   "sources": [
    {
     "author": "Web Artisan",
     "handle": "@k2sodev",
     "url": "https://dev.to/k2sodev/i-almost-replaced-lovable-with-a-5-vps-dokploy-and-one-mcp-gateway-3mn9",
     "platform": "devto",
     "date": "2026-09-18",
     "primary": true
    }
   ]
  },
  {
   "slug": "close-bug-reports-while-hardening",
   "url": "https://agentsetups.dev/use-case/close-bug-reports-while-hardening/",
   "title": "Close bugs with one agent while another hardens code",
   "summary": "Muse Spark + Oh My Pi close existing bugs while GLM-5.3 + droid lock down the codebase against future bugs.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "OMP (oh-my-pi)",
    "Meta Muse",
    "Droid"
   ],
   "models": [
    "Muse Spark 1.3",
    "GLM-5.3"
   ],
   "tools": [
    "droid"
   ],
   "prompt": "Goal: Work two tracks in parallel: fix open bugs and harden the codebase.\nSetup: agents used in source: OMP (oh-my-pi), Meta Muse, Droid; tools/MCPs stated: droid.\nSteps:\n1. Point one agent at your existing bug reports to close them.\n2. Point a second agent at researching and locking down the codebase so future agents create fewer bugs.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Pratham — https://x.com/prathamdby/status/2104196873502547981 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Point one agent at your existing bug reports to close them.",
    "Point a second agent at researching and locking down the codebase so future agents create fewer bugs."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-27",
   "trend_score": 35.7,
   "sources": [
    {
     "author": "Pratham",
     "handle": "@prathamdby",
     "url": "https://x.com/prathamdby/status/2104196873502547981",
     "platform": "x",
     "date": "2026-09-27",
     "primary": true
    }
   ]
  },
  {
   "slug": "debug-ssh-then-session-cartoon",
   "url": "https://agentsetups.dev/use-case/debug-ssh-then-session-cartoon/",
   "title": "Fix slow SSH, then turn the session into a cartoon",
   "summary": "Claude Code fixed slow Codex SSH connections; the /session-story skill turned the session into an animated cartoon.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "HyperFrames /session-story"
   ],
   "prompt": "Goal: Fix a dev-environment issue and share the story.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: HyperFrames /session-story.\nSteps:\n1. Ask Claude Code to debug and fix the slow SSH connections.\n2. Run the community /session-story skill to turn the session into an animated cartoon.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: James Russo — https://x.com/Rames_Jusso/status/2103253095958663364",
   "steps": [
    "Ask Claude Code to debug and fix the slow SSH connections.",
    "Run the community /session-story skill to turn the session into an animated cartoon."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 35.7,
   "sources": [
    {
     "author": "James Russo",
     "handle": "@Rames_Jusso",
     "url": "https://x.com/Rames_Jusso/status/2103253095958663364",
     "platform": "x",
     "date": "2026-09-24",
     "primary": true
    }
   ]
  },
  {
   "slug": "instinct-book-salon-abroad",
   "url": "https://agentsetups.dev/use-case/instinct-book-salon-abroad/",
   "title": "Have Instinct book a salon abroad",
   "summary": "Instinct found Copenhagen salons, read reviews, sent photos, then emailed the salon when booking needed a Danish phone number.",
   "category": "travel",
   "category_label": "Travel",
   "agents": [
    "Instinct"
   ],
   "models": [],
   "tools": [
    "email"
   ],
   "prompt": "Goal: Book a specific service in a city where I don’t speak the language or have a local number.\nSetup: agents used in source: Instinct; tools/MCPs stated: email.\nSteps:\n1. Describe the service (e.g. a wavy perm) and city.\n2. Let the agent find salons, read reviews and send you photos; choose one.\n3. If online booking needs a local phone number, let it email the salon instead.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: The Startup Ideas Podcast (SIP) 🧃 — https://x.com/startupideaspod/status/2100245612910571873",
   "steps": [
    "Describe the service (e.g. a wavy perm) and city.",
    "Let the agent find salons, read reviews and send you photos; choose one.",
    "If online booking needs a local phone number, let it email the salon instead."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-16",
   "trend_score": 35.4,
   "sources": [
    {
     "author": "The Startup Ideas Podcast (SIP) 🧃",
     "handle": "@startupideaspod",
     "url": "https://x.com/startupideaspod/status/2100245612910571873",
     "platform": "x",
     "date": "2026-09-16",
     "primary": true
    }
   ]
  },
  {
   "slug": "rewrite-service-node-to-go",
   "url": "https://agentsetups.dev/use-case/rewrite-service-node-to-go/",
   "title": "Rewrite a critical Node.js service in Go overnight",
   "summary": "Checkly built ~600 black-box tests from production scenarios first; Claude Code wrote 13k lines of Go and servers went 20→5.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Port a service to a new language with black-box tests as the safety net.\nSetup: agents used in source: Claude.\nSteps:\n1. Build black-box tests from real production scenarios (Checkly had about 600).\n2. Have Claude Code rewrite the service in the target language.\n3. Run the same tests against the new service before switching traffic.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Checkly — https://x.com/checklyHQ/status/2104919645790544282 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Build black-box tests from real production scenarios (Checkly had about 600).",
    "Have Claude Code rewrite the service in the target language.",
    "Run the same tests against the new service before switching traffic."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-29",
   "trend_score": 34.9,
   "sources": [
    {
     "author": "Checkly",
     "handle": "@checklyHQ",
     "url": "https://x.com/checklyHQ/status/2104919645790544282",
     "platform": "x",
     "date": "2026-09-29",
     "primary": true
    }
   ]
  },
  {
   "slug": "threejs-world-skill-loop",
   "url": "https://agentsetups.dev/use-case/threejs-world-skill-loop/",
   "title": "Build a playable 3D world with a three.js skill",
   "summary": "Install a three.js skill, describe one scene, add water, fog, weather and day/night one prompt each, and let Opus loop.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "three.js"
   ],
   "prompt": "Goal: Make a browser 3D world without a game engine.\nSetup: agents used in source: Claude; tools/MCPs stated: three.js.\nSteps:\n1. Install a three.js skill into Claude Code (the post points to MengTo’s open-source skills).\n2. Describe one scene: a boat, a river, a valley.\n3. Add water, fog, weather, day and night, one prompt each.\n4. Feed it screenshots of the look, not paragraphs.\n5. Let Opus loop for hours on details, then publish and share one link.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Amodex — https://x.com/amodexbt/status/2102806581565923344",
   "steps": [
    "Install a three.js skill into Claude Code (the post points to MengTo’s open-source skills).",
    "Describe one scene: a boat, a river, a valley.",
    "Add water, fog, weather, day and night, one prompt each.",
    "Feed it screenshots of the look, not paragraphs.",
    "Let Opus loop for hours on details, then publish and share one link."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 34.9,
   "sources": [
    {
     "author": "Amodex",
     "handle": "@amodexbt",
     "url": "https://x.com/amodexbt/status/2102806581565923344",
     "platform": "x",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "cron-start-codex-window",
   "url": "https://agentsetups.dev/use-case/cron-start-codex-window/",
   "title": "Use a cron job to start your Codex usage window",
   "summary": "A Hermes cron triggers the Codex 5-hour window at 6:30, 11:30, 16:30 and 21:30 every day.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Codex",
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "cron"
   ],
   "prompt": "Goal: Schedule a daily job that starts my Codex 5-hour window at fixed times.\nSetup: agents used in source: Codex, Hermes Agent; tools/MCPs stated: cron.\nSteps:\n1. Create a Hermes cron job.\n2. Trigger Codex at 6:30, 11:30, 16:30 and 21:30.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Azad Balabanian — https://x.com/Azadux/status/2098552242085462171",
   "steps": [
    "Create a Hermes cron job.",
    "Trigger Codex at 6:30, 11:30, 16:30 and 21:30."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-11",
   "trend_score": 34.4,
   "sources": [
    {
     "author": "Azad Balabanian",
     "handle": "@Azadux",
     "url": "https://x.com/Azadux/status/2098552242085462171",
     "platform": "x",
     "date": "2026-09-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "youtube-research-audit",
   "url": "https://agentsetups.dev/use-case/youtube-research-audit/",
   "title": "Audit what YouTube creators actually build",
   "summary": "GrokBot pulled the top 100 “building AI agents” videos and categorised what was really built.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "YouTube"
   ],
   "prompt": "Goal: Analyse the top videos on a topic and categorise them.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: YouTube.\nSteps:\n1. Pull the top 100 YouTube videos for the query.\n2. Categorise what each actually builds.\n3. Report the breakdown (e.g. 31% were just skills).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Topher Stephenson | CRE AI, Ops, Marketing — https://x.com/TopherNOW/status/2099510737664180733",
   "steps": [
    "Pull the top 100 YouTube videos for the query.",
    "Categorise what each actually builds.",
    "Report the breakdown (e.g. 31% were just skills)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-14",
   "trend_score": 32.9,
   "sources": [
    {
     "author": "Topher Stephenson | CRE AI, Ops, Marketing",
     "handle": "@TopherNOW",
     "url": "https://x.com/TopherNOW/status/2099510737664180733",
     "platform": "x",
     "date": "2026-09-14",
     "primary": true
    }
   ]
  },
  {
   "slug": "learn-japanese-with-mvs",
   "url": "https://agentsetups.dev/use-case/learn-japanese-with-mvs/",
   "title": "Build a Learn-Japanese-with-MVs app with TTS",
   "summary": "A Gemini 3.8 Flash TTS web app (and LINE Bot) for learning Japanese from music videos.",
   "category": "education",
   "category_label": "Education",
   "agents": [
    "Claude"
   ],
   "models": [
    "Gemini 3.8 Flash TTS"
   ],
   "tools": [
    "LINE Bot"
   ],
   "prompt": "Goal: Build a language-learning app using a new TTS model.\nSetup: agents used in source: Claude; tools/MCPs stated: LINE Bot.\nSteps:\n1. Pick lyrics/lines from music videos.\n2. Generate pronunciations with the TTS model.\n3. Wire it to a web app or LINE Bot.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Evan Lin — https://dev.to/gde/ai-in-practice-gemini-38-flash-tts-launch-i-built-a-learn-japanese-with-mvs-web-app-and-4o79 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Pick lyrics/lines from music videos.",
    "Generate pronunciations with the TTS model.",
    "Wire it to a web app or LINE Bot."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 32.7,
   "sources": [
    {
     "author": "Evan Lin",
     "handle": "@evanlin",
     "url": "https://dev.to/gde/ai-in-practice-gemini-38-flash-tts-launch-i-built-a-learn-japanese-with-mvs-web-app-and-4o79",
     "platform": "devto",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "lidar-scan-home-redesign",
   "url": "https://agentsetups.dev/use-case/lidar-scan-home-redesign/",
   "title": "Redesign your home from a phone LiDAR scan",
   "summary": "Scan with PolyCam, export GLTF, load into Codex with Astra, then chat through redesigns and walk inside them.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Codex"
   ],
   "models": [
    "Astra"
   ],
   "tools": [
    "PolyCam",
    "GLTF"
   ],
   "prompt": "Goal: Get an explorable 3D model of my home to try redesigns.\nSetup: agents used in source: Codex; tools/MCPs stated: PolyCam, GLTF.\nSteps:\n1. Use a phone with LiDAR (iPhone 12 Pro or later).\n2. Scan the space with a scanning app like PolyCam and use its free GLTF export.\n3. Load it into Codex (the author used Astra).\n4. Chat to try redesign scenarios and walk around inside.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Matt Ferrante — https://x.com/ferrants/status/2098126056691831240",
   "steps": [
    "Use a phone with LiDAR (iPhone 12 Pro or later).",
    "Scan the space with a scanning app like PolyCam and use its free GLTF export.",
    "Load it into Codex (the author used Astra).",
    "Chat to try redesign scenarios and walk around inside."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-10",
   "trend_score": 32.7,
   "sources": [
    {
     "author": "Matt Ferrante",
     "handle": "@ferrants",
     "url": "https://x.com/ferrants/status/2098126056691831240",
     "platform": "x",
     "date": "2026-09-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "copilot-agent-issue-to-pr",
   "url": "https://agentsetups.dev/use-case/copilot-agent-issue-to-pr/",
   "title": "Assign a GitHub issue to the Copilot coding agent",
   "summary": "Treat it like an intern: put the log line in the issue, state the fix constraint, then request changes on the PR.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "GitHub Copilot"
   ],
   "models": [],
   "tools": [
    "GitHub"
   ],
   "prompt": "Goal: Hand a scoped bug to a GitHub-hosted coding agent.\nSetup: agents used in source: GitHub Copilot; tools/MCPs stated: GitHub.\nSteps:\n1. Write the issue with the log line and the exact constraint (e.g. key on (delivery_id, attempt) or the business id; do not redesign the worker).\n2. Assign it to the coding agent and wait for the PR.\n3. Review it like an intern’s PR and request changes on noise.\n4. Variant (Jules): a precise 3-sentence ticket worked; a vague “clean up” ticket did not.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Equinox — https://x.com/Equinox_enx/status/2095089632287543718",
   "steps": [
    "Write the issue with the log line and the exact constraint (e.g. key on (delivery_id, attempt) or the business id; do not redesign the worker).",
    "Assign it to the coding agent and wait for the PR.",
    "Review it like an intern’s PR and request changes on noise.",
    "Variant (Jules): a precise 3-sentence ticket worked; a vague “clean up” ticket did not."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-02",
   "trend_score": 32.3,
   "sources": [
    {
     "author": "Equinox",
     "handle": "@Equinox_enx",
     "url": "https://x.com/Equinox_enx/status/2095089632287543718",
     "platform": "x",
     "date": "2026-09-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "planner-implementer-task-spec",
   "url": "https://agentsetups.dev/use-case/planner-implementer-task-spec/",
   "title": "Use a task spec contract between planner and subagents",
   "summary": "A YAML spec the planner must emit and implementers echo back cut wrong-problem retries from 31% to 7% in a Claude Code loop.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "YAML"
   ],
   "prompt": "Goal: Stop zero-context implementer agents from solving the wrong problem.\nSetup: agents used in source: Claude; tools/MCPs stated: YAML.\nSteps:\n1. Treat the handoff as an interface, not a message: the planner must emit one fenced block that validates against a schema (task_id, goal, target files, acceptance criteria…).\n2. Have the implementer echo the spec back in its own words before touching code; reject mismatches.\n3. Reuse the same spec as the input for the verifier agent.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: yureki_lab — https://dev.to/yureki_lab/how-i-built-a-task-spec-contract-between-my-planner-and-implementer-agents-e94",
   "steps": [
    "Treat the handoff as an interface, not a message: the planner must emit one fenced block that validates against a schema (task_id, goal, target files, acceptance criteria…).",
    "Have the implementer echo the spec back in its own words before touching code; reject mismatches.",
    "Reuse the same spec as the input for the verifier agent."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 32.0,
   "sources": [
    {
     "author": "yureki_lab",
     "handle": "@yureki_lab",
     "url": "https://dev.to/yureki_lab/how-i-built-a-task-spec-contract-between-my-planner-and-implementer-agents-e94",
     "platform": "devto",
     "date": "2026-09-20",
     "primary": true
    }
   ]
  },
  {
   "slug": "indian-stocks-mcp-server",
   "url": "https://agentsetups.dev/use-case/indian-stocks-mcp-server/",
   "title": "Build an MCP server for live stock data",
   "summary": "Tired of pasting numbers, a builder made an MCP server for ~8,200 NSE and BSE stocks so Claude stops inventing P/Es.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "MCP"
   ],
   "prompt": "Goal: Give my agent real market data instead of copy-paste.\nSetup: agents used in source: Claude; tools/MCPs stated: MCP.\nSteps:\n1. Build an MCP server over the exchange data you need (here all NSE + BSE stocks).\n2. Connect it to Claude so it pulls numbers instead of recalling them.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: hit — https://x.com/justbuildingai/status/2101558228241006839 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Build an MCP server over the exchange data you need (here all NSE + BSE stocks).",
    "Connect it to Claude so it pulls numbers instead of recalling them."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 31.6,
   "sources": [
    {
     "author": "hit",
     "handle": "@justbuildingai",
     "url": "https://x.com/justbuildingai/status/2101558228241006839",
     "platform": "x",
     "date": "2026-09-20",
     "primary": true
    }
   ]
  },
  {
   "slug": "codex-sign-pdf-from-email",
   "url": "https://agentsetups.dev/use-case/codex-sign-pdf-from-email/",
   "title": "Have Codex sign and return a PDF from your email",
   "summary": "While driving, Codex pulled a PDF from email, verified the details, added his handwritten name and sent it back in 3 minutes.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "email",
    "PDF"
   ],
   "prompt": "Goal: Return a signed document while I’m away from my computer.\nSetup: agents used in source: Codex; tools/MCPs stated: email, PDF.\nSteps:\n1. Ask Codex to find the PDF in your email.\n2. Have it verify the details.\n3. Have it add your handwritten signature/name and send the completed PDF back.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Diego | AI 🚀 - e/acc — https://x.com/diegocabezas01/status/2095145831942791263",
   "steps": [
    "Ask Codex to find the PDF in your email.",
    "Have it verify the details.",
    "Have it add your handwritten signature/name and send the completed PDF back."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-02",
   "trend_score": 31.4,
   "sources": [
    {
     "author": "Diego | AI 🚀 - e/acc",
     "handle": "@diegocabezas01",
     "url": "https://x.com/diegocabezas01/status/2095145831942791263",
     "platform": "x",
     "date": "2026-09-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "company-run-by-scheduled-claude-agents",
   "url": "https://agentsetups.dev/use-case/company-run-by-scheduled-claude-agents/",
   "title": "Run a tiny business with scheduled Claude Code agents",
   "summary": "Five roles (CEO, builder, growth, verifier, board) wake on GitHub Actions; files are the memory; a script guards the money.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "GitHub Actions",
    "claude-code-action",
    "Gumroad API"
   ],
   "prompt": "Goal: Have agents run a small online business on a schedule.\nSetup: agents used in source: Claude; tools/MCPs stated: GitHub Actions, claude-code-action, Gumroad API.\nSteps:\n1. Make the repo the brain: CLAUDE.md as constitution, STATE.md generated by script, STRATEGY.md, BACKLOG.md as the handoff table, JOURNAL.md per run, role files in .claude/agents.\n2. Wake each role with a scheduled workflow running claude-code-action (e.g. CEO daily, builder twice daily).\n3. Agents don’t touch git: after they edit, shell steps revert protected files, then commit.\n4. Money rules live in a non-AI treasury script (sales sync, reserve).\n5. Before marking done, hand acceptance criteria to a fresh-context verifier subagent.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Nick T — https://dev.to/nick_t_eac6be7ee8e88de2f3/i-handed-a-tiny-business-to-claude-code-agents-on-a-cron-schedule-heres-the-architecture-2615",
   "steps": [
    "Make the repo the brain: CLAUDE.md as constitution, STATE.md generated by script, STRATEGY.md, BACKLOG.md as the handoff table, JOURNAL.md per run, role files in .claude/agents.",
    "Wake each role with a scheduled workflow running claude-code-action (e.g. CEO daily, builder twice daily).",
    "Agents don’t touch git: after they edit, shell steps revert protected files, then commit.",
    "Money rules live in a non-AI treasury script (sales sync, reserve).",
    "Before marking done, hand acceptance criteria to a fresh-context verifier subagent."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 31.3,
   "sources": [
    {
     "author": "Nick T",
     "handle": "@nick_t_eac6be7ee8e88de2f3",
     "url": "https://dev.to/nick_t_eac6be7ee8e88de2f3/i-handed-a-tiny-business-to-claude-code-agents-on-a-cron-schedule-heres-the-architecture-2615",
     "platform": "devto",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "esp32-voice-agent-hermes",
   "url": "https://agentsetups.dev/use-case/esp32-voice-agent-hermes/",
   "title": "Build a $30 ESP32 voice gadget with Hermes",
   "summary": "An open-source alternative to the Muse Charm: ESP32-C6 hardware, Hermes Agent as the brain, Venice for inference.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "ESP32-C6",
    "Venice"
   ],
   "prompt": "Goal: Make my own press-to-talk agent device without vendor lock-in.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: ESP32-C6, Venice.\nSteps:\n1. Use an ESP32-C6 board (~$30).\n2. Use Hermes Agent as the brain and Venice for inference.\n3. Press, talk, get a reply, and have it get things done.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Kakusan — https://x.com/kakujain/status/2105300887254270026 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Use an ESP32-C6 board (~$30).",
    "Use Hermes Agent as the brain and Venice for inference.",
    "Press, talk, get a reply, and have it get things done."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 31.1,
   "sources": [
    {
     "author": "Kakusan",
     "handle": "@kakujain",
     "url": "https://x.com/kakujain/status/2105300887254270026",
     "platform": "x",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "207-agents-in-30-waves",
   "url": "https://agentsetups.dev/use-case/207-agents-in-30-waves/",
   "title": "Run 207 agents in 30 waves with gates",
   "summary": "~3h of planning, then 207 Claude Code agents in 30 waves with gates, acceptance, fixes and a write-up; ~100 ran overnight.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Run a big job as waves of parallel agents.\nSetup: agents used in source: Claude.\nSteps:\n1. Spend real time planning (the author spent ~3 hours).\n2. Run agents in waves, with a gate and acceptance check between waves.\n3. Add a fixes pass and a final write-up.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Slobodan Stojanović — https://x.com/slobodan_/status/2103175515943108950 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Spend real time planning (the author spent ~3 hours).",
    "Run agents in waves, with a gate and acceptance check between waves.",
    "Add a fixes pass and a final write-up."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 30.8,
   "sources": [
    {
     "author": "Slobodan Stojanović",
     "handle": "@slobodan_",
     "url": "https://x.com/slobodan_/status/2103175515943108950",
     "platform": "x",
     "date": "2026-09-24",
     "primary": true
    }
   ]
  },
  {
   "slug": "apple-shortcuts-as-code",
   "url": "https://agentsetups.dev/use-case/apple-shortcuts-as-code/",
   "title": "Build Apple Shortcuts as code with Claude Code",
   "summary": "Claude Code wrote 3 Shortcuts as code, signed them and imported them to the iPhone, with no block dragging.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Apple Shortcuts"
   ],
   "prompt": "Goal: Create working Apple Shortcuts without the editor.\nSetup: agents used in source: Claude; tools/MCPs stated: Apple Shortcuts.\nSteps:\n1. Describe each shortcut.\n2. Have Claude Code write them as code and sign them.\n3. Import them into the iPhone.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Shrikar Archak — https://x.com/shrikar84/status/2103611389860536495 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Describe each shortcut.",
    "Have Claude Code write them as code and sign them.",
    "Import them into the iPhone."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-25",
   "trend_score": 30.6,
   "sources": [
    {
     "author": "Shrikar Archak",
     "handle": "@shrikar84",
     "url": "https://x.com/shrikar84/status/2103611389860536495",
     "platform": "x",
     "date": "2026-09-25",
     "primary": true
    }
   ]
  },
  {
   "slug": "meal-prep-app-for-creator",
   "url": "https://agentsetups.dev/use-case/meal-prep-app-for-creator/",
   "title": "Build a meal-prep app for a creator’s followers",
   "summary": "A husband built his wife’s meal-prep planner, 100 recipes and a synced shopping list with Claude Code; 850 on the waitlist.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Build an app a creator can launch to her audience.\nSetup: agents used in source: Claude.\nSteps:\n1. Build the meal-prep planner, recipe library (100 recipes) and synced shopping list with Claude Code.\n2. Open a waitlist before launch.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Timothy 🟢 | Panic Drop — https://x.com/timoassi/status/2103492326395937187 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Build the meal-prep planner, recipe library (100 recipes) and synced shopping list with Claude Code.",
    "Open a waitlist before launch."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-25",
   "trend_score": 29.9,
   "sources": [
    {
     "author": "Timothy 🟢 | Panic Drop",
     "handle": "@timoassi",
     "url": "https://x.com/timoassi/status/2103492326395937187",
     "platform": "x",
     "date": "2026-09-25",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-real-estate-deal-scorecard",
   "url": "https://agentsetups.dev/use-case/grokbot-real-estate-deal-scorecard/",
   "title": "Score a house six ways before you get attached",
   "summary": "@TanyaZorov’s Grok Bot template scores any US address for room rental, long/mid/short-term rental, flip and BRRRR.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Zillow",
    "Redfin"
   ],
   "prompt": "Goal: Underwrite a property quickly before investing time in it.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Zillow, Redfin.\nSteps:\n1. Paste a US address or a Zillow/Redfin/Realtor link.\n2. Have the bot score it six ways: rent-by-the-room, long-term, mid-term, short-term rental, flip and BRRRR.\n3. Get a short scorecard and a clear answer on which strategies fit and which don’t.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: TanyaZ — https://x.com/TanyaZorov/status/2101798329726197907",
   "steps": [
    "Paste a US address or a Zillow/Redfin/Realtor link.",
    "Have the bot score it six ways: rent-by-the-room, long-term, mid-term, short-term rental, flip and BRRRR.",
    "Get a short scorecard and a clear answer on which strategies fit and which don’t."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 29.7,
   "sources": [
    {
     "author": "TanyaZ",
     "handle": "@TanyaZorov",
     "url": "https://x.com/TanyaZorov/status/2101798329726197907",
     "platform": "x",
     "date": "2026-09-20",
     "primary": true
    },
    {
     "author": "TanyaZ",
     "handle": "@TanyaZorov",
     "url": "https://x.com/TanyaZorov/status/2102026792122937587",
     "platform": "x",
     "date": "2026-09-21",
     "primary": false
    }
   ]
  },
  {
   "slug": "assistant-flight-bake-off",
   "url": "https://agentsetups.dev/use-case/assistant-flight-bake-off/",
   "title": "Run one flight request through four assistants",
   "summary": "@twid gave Instinct, Grok Bot, Muse and Hermes the same tricky LGA/JFK→SJC/SFO request; Grok Bot came first.",
   "category": "travel",
   "category_label": "Travel",
   "agents": [
    "Hermes Agent",
    "Grok Bot",
    "Meta Muse",
    "Instinct"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Compare personal assistants on a real booking task before choosing one.\nSetup: agents used in source: Hermes Agent, Grok Bot, Meta Muse, Instinct.\nSteps:\n1. Write one realistic request with options and preferences (airports, two dates, cabin preferences like Delta One or JetBlue Mint “if not outrageous”).\n2. Send the identical prompt to each assistant.\n3. Compare the results and pick the best.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Todd Dailey — https://x.com/twid/status/2101789185598247390",
   "steps": [
    "Write one realistic request with options and preferences (airports, two dates, cabin preferences like Delta One or JetBlue Mint “if not outrageous”).",
    "Send the identical prompt to each assistant.",
    "Compare the results and pick the best."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 29.5,
   "sources": [
    {
     "author": "Todd Dailey",
     "handle": "@twid",
     "url": "https://x.com/twid/status/2101789185598247390",
     "platform": "x",
     "date": "2026-09-20",
     "primary": true
    }
   ]
  },
  {
   "slug": "mobile-optimise-finance-app",
   "url": "https://agentsetups.dev/use-case/mobile-optimise-finance-app/",
   "title": "Make your personal finance app work on your phone",
   "summary": "A personal finance app only lived on the laptop; Codex mobile-optimised it so payments get logged on the go.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Make my personal web app usable on my phone.\nSetup: agents used in source: Codex.\nSteps:\n1. Ask Codex to mobile-optimise the site.\n2. Use it on the go so you log entries where they happen.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Cecilia Kim — https://x.com/ceciliakdesign/status/2095959197456257337 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask Codex to mobile-optimise the site.",
    "Use it on the go so you log entries where they happen."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-04",
   "trend_score": 29.2,
   "sources": [
    {
     "author": "Cecilia Kim",
     "handle": "@ceciliakdesign",
     "url": "https://x.com/ceciliakdesign/status/2095959197456257337",
     "platform": "x",
     "date": "2026-09-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "civic-budget-decoder-rag",
   "url": "https://agentsetups.dev/use-case/civic-budget-decoder-rag/",
   "title": "Turn a city budget into a civic Q&A app",
   "summary": "Claude Code (Opus 5.5) built a RAG app on Neon over Milwaukee’s proposed budget, with per-address “tax receipts”.",
   "category": "data-analysis",
   "category_label": "Data analysis",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Neon",
    "Mastra",
    "CopilotKit",
    "Vercel"
   ],
   "prompt": "Goal: Help residents understand a proposed city budget.\nSetup: agents used in source: Claude; tools/MCPs stated: Neon, Mastra, CopilotKit, Vercel.\nSteps:\n1. Load the budget documents into a RAG system on a vector database (Neon).\n2. Add a per-address “tax receipt” feature from city property data.\n3. Build a chat agent (Mastra) with a generative-UI interface (CopilotKit / OpenUI).\n4. Host the front end (Vercel); make it work on phones.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Tarik Moody — https://x.com/tarikjmoody/status/2102900178143367442",
   "steps": [
    "Load the budget documents into a RAG system on a vector database (Neon).",
    "Add a per-address “tax receipt” feature from city property data.",
    "Build a chat agent (Mastra) with a generative-UI interface (CopilotKit / OpenUI).",
    "Host the front end (Vercel); make it work on phones."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 28.3,
   "sources": [
    {
     "author": "Tarik Moody",
     "handle": "@tarikjmoody",
     "url": "https://x.com/tarikjmoody/status/2102900178143367442",
     "platform": "x",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "block-test-tampering-hooks",
   "url": "https://agentsetups.dev/use-case/block-test-tampering-hooks/",
   "title": "Stop agents editing tests to make them pass",
   "summary": "Hooks snapshot test-file hashes at session start and block risky outbound commands, across Claude Code, Codex and Gemini CLI.",
   "category": "security",
   "category_label": "Security",
   "agents": [
    "Claude",
    "Codex",
    "Gemini CLI"
   ],
   "models": [],
   "tools": [
    "agent-guard-hooks"
   ],
   "prompt": "Goal: Make sure “tests pass” means the code was fixed, not the tests.\nSetup: agents used in source: Claude, Codex, Gemini CLI; tools/MCPs stated: agent-guard-hooks.\nSteps:\n1. pip install agent-guard-hooks; agent-guard install (add --tool codex or --tool gemini for those CLIs).\n2. On SessionStart it hashes every test file; edits to tests are caught.\n3. A PreToolUse hook on Bash blocks risky patterns (pushes to protected branches etc.) before they run.\n4. Run agent-guard verify --tool codex --days 7 to check gates are mounted and firing.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: hao li — https://dev.to/haoli/my-agent-changed-tobe10-to-tobe9-and-called-it-done-i-built-hooks-to-stop-that-8c4",
   "steps": [
    "pip install agent-guard-hooks; agent-guard install (add --tool codex or --tool gemini for those CLIs).",
    "On SessionStart it hashes every test file; edits to tests are caught.",
    "A PreToolUse hook on Bash blocks risky patterns (pushes to protected branches etc.) before they run.",
    "Run agent-guard verify --tool codex --days 7 to check gates are mounted and firing."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 28.2,
   "sources": [
    {
     "author": "hao li",
     "handle": "@haoli",
     "url": "https://dev.to/haoli/my-agent-changed-tobe10-to-tobe9-and-called-it-done-i-built-hooks-to-stop-that-8c4",
     "platform": "devto",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "agent-team-chief-pm-codemaster",
   "url": "https://agentsetups.dev/use-case/agent-team-chief-pm-codemaster/",
   "title": "Ship 40 PRs a day with a chief-of-staff agent team",
   "summary": "A ChiefOfStaff, per-project PMs and a CodeMaster that prompts claude -p / codex CLIs on a VM, looping PRs to green.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex",
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Run my projects through an agent team.\nSetup: agents used in source: Claude, Codex, Grok Bot.\nSteps:\n1. Talk only to a ChiefOfStaff agent, which works all the other bots.\n2. Give each project a PM agent that understands it in depth.\n3. PMs send requests to a “CodeMaster” that writes prompts for claude -p and codex CLI, and runs them only on a VM.\n4. Loop PRs until green, then merge.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Gabe Fletcher — https://x.com/gabefletcher/status/2097488984846852345",
   "steps": [
    "Talk only to a ChiefOfStaff agent, which works all the other bots.",
    "Give each project a PM agent that understands it in depth.",
    "PMs send requests to a “CodeMaster” that writes prompts for claude -p and codex CLI, and runs them only on a VM.",
    "Loop PRs until green, then merge."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-09",
   "trend_score": 28.1,
   "sources": [
    {
     "author": "Gabe Fletcher",
     "handle": "@gabefletcher",
     "url": "https://x.com/gabefletcher/status/2097488984846852345",
     "platform": "x",
     "date": "2026-09-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-outreach-pays-for-itself",
   "url": "https://agentsetups.dev/use-case/grokbot-outreach-pays-for-itself/",
   "title": "Make your Grok Bot pay for its own API key",
   "summary": "Every morning it finds X posts complaining about what he fixes and drafts outreach in his voice; 11 days: $27 spent, $6,300 invoiced.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "X"
   ],
   "prompt": "Goal: Find clients who already have the problem I solve.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: X.\nSteps:\n1. Rule: the bot pays for its own API key or it gets shut off.\n2. Every morning it reads X for people complaining about the thing you fix.\n3. It drafts outreach in your voice, quoting their post.\n4. It waits for you and never sends on its own.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Roxx — https://x.com/Roxx_0x/status/2097709794576470039 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Rule: the bot pays for its own API key or it gets shut off.",
    "Every morning it reads X for people complaining about the thing you fix.",
    "It drafts outreach in your voice, quoting their post.",
    "It waits for you and never sends on its own."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-09",
   "trend_score": 27.9,
   "sources": [
    {
     "author": "Roxx",
     "handle": "@Roxx_0x",
     "url": "https://x.com/Roxx_0x/status/2097709794576470039",
     "platform": "x",
     "date": "2026-09-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "networking-boardy-obsidian",
   "url": "https://agentsetups.dev/use-case/networking-boardy-obsidian/",
   "title": "Run networking through Boardy, Claude Code and Obsidian",
   "summary": "Boardy finds a fit and emails you; Claude Code reads it with Obsidian context; notes loop back to Obsidian.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Boardy",
    "Gmail",
    "Obsidian"
   ],
   "prompt": "Goal: Run my networking workflow without LinkedIn.\nSetup: agents used in source: Claude; tools/MCPs stated: Boardy, Gmail, Obsidian.\nSteps:\n1. Boardy finds the fit and emails you.\n2. Claude Code reads it in Gmail with your context from Obsidian.\n3. You decide; Boardy takes the meeting and writes notes.\n4. Everything loops back into Obsidian.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: EZ — https://x.com/EZheng66099/status/2097509351724331447",
   "steps": [
    "Boardy finds the fit and emails you.",
    "Claude Code reads it in Gmail with your context from Obsidian.",
    "You decide; Boardy takes the meeting and writes notes.",
    "Everything loops back into Obsidian."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-09",
   "trend_score": 27.8,
   "sources": [
    {
     "author": "EZ",
     "handle": "@EZheng66099",
     "url": "https://x.com/EZheng66099/status/2097509351724331447",
     "platform": "x",
     "date": "2026-09-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "overnight-inbox-brief-drafts",
   "url": "https://agentsetups.dev/use-case/overnight-inbox-brief-drafts/",
   "title": "Morning brief: read Outlook, Teams and Slack, draft replies",
   "summary": "Overnight Claude Code keeps only what needs you and drafts every reply in your voice; nothing sends without approval.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Outlook",
    "Teams",
    "Slack"
   ],
   "prompt": "Goal: Brief me each morning and draft my replies.\nSetup: agents used in source: Claude; tools/MCPs stated: Outlook, Teams, Slack.\nSteps:\n1. Overnight, read Outlook, Teams and Slack.\n2. Keep only what needs me.\n3. Draft every reply in my voice.\n4. Approved drafts land in my drafts folder. Nothing is sent without me.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Gabriel Rosinol (Bielrv) — https://x.com/gabrielrosinol/status/2104958721935732895",
   "steps": [
    "Overnight, read Outlook, Teams and Slack.",
    "Keep only what needs me.",
    "Draft every reply in my voice.",
    "Approved drafts land in my drafts folder. Nothing is sent without me."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-29",
   "trend_score": 27.7,
   "sources": [
    {
     "author": "Gabriel Rosinol (Bielrv)",
     "handle": "@gabrielrosinol",
     "url": "https://x.com/gabrielrosinol/status/2104958721935732895",
     "platform": "x",
     "date": "2026-09-29",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-free-models-gateway",
   "url": "https://agentsetups.dev/use-case/hermes-free-models-gateway/",
   "title": "Run Hermes on free models through a gateway",
   "summary": "Put OmniRoute between Hermes Agent and providers (OpenRouter, NVIDIA) so free tiers fail over without reconfiguring Hermes.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "OmniRoute",
    "OpenRouter",
    "NVIDIA"
   ],
   "prompt": "Goal: Experiment with Hermes Agent without paying for one provider.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: OmniRoute, OpenRouter, NVIDIA.\nSteps:\n1. Install OmniRoute locally and start it.\n2. Add OpenRouter as a provider (API key), then add NVIDIA as another provider.\n3. Point Hermes Agent at OmniRoute instead of a single provider.\n4. Run a real task and check routing.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Vivek Shetye — https://dev.to/vivek_shetye/how-i-run-hermes-agent-on-free-ai-models-with-omniroute-3103",
   "steps": [
    "Install OmniRoute locally and start it.",
    "Add OpenRouter as a provider (API key), then add NVIDIA as another provider.",
    "Point Hermes Agent at OmniRoute instead of a single provider.",
    "Run a real task and check routing."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-15",
   "trend_score": 27.6,
   "sources": [
    {
     "author": "Vivek Shetye",
     "handle": "@vivek_shetye",
     "url": "https://dev.to/vivek_shetye/how-i-run-hermes-agent-on-free-ai-models-with-omniroute-3103",
     "platform": "devto",
     "date": "2026-09-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "shop-home-insurance",
   "url": "https://agentsetups.dev/use-case/shop-home-insurance/",
   "title": "Shop your homeowners insurance and save $4,600 a year",
   "summary": "With coverages, property info and Chrome access, Claude Code got quotes from ~12 providers; a new policy was approved the same day.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Chrome",
    "Gmail"
   ],
   "prompt": "Goal: Find a cheaper homeowners insurance policy with equal coverage.\nSetup: agents used in source: Claude; tools/MCPs stated: Chrome, Gmail.\nSteps:\n1. Provide your existing coverages, property info and the personal details insurers need.\n2. Give the agent Chrome access, plus Gmail and your current policy/mortgage company.\n3. Have it seek quotes from about a dozen providers and shortlist the strongest.\n4. Apply for the best one yourself (author: saved $4,600/yr; approved with AAA at $3,100/yr).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Seth Pratt — https://x.com/sethprattsf/status/2100023090860429659",
   "steps": [
    "Provide your existing coverages, property info and the personal details insurers need.",
    "Give the agent Chrome access, plus Gmail and your current policy/mortgage company.",
    "Have it seek quotes from about a dozen providers and shortlist the strongest.",
    "Apply for the best one yourself (author: saved $4,600/yr; approved with AAA at $3,100/yr)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-16",
   "trend_score": 27.4,
   "sources": [
    {
     "author": "Seth Pratt",
     "handle": "@sethprattsf",
     "url": "https://x.com/sethprattsf/status/2100023090860429659",
     "platform": "x",
     "date": "2026-09-16",
     "primary": true
    }
   ]
  },
  {
   "slug": "gtm-conversion-tracking-script",
   "url": "https://agentsetups.dev/use-case/gtm-conversion-tracking-script/",
   "title": "Script your Google Tag Manager conversion setup",
   "summary": "Claude Code adds dataLayer events, creates Ads conversions by API and builds triggers, GA4, Ads and Meta tags via the GTM API.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Google Tag Manager API",
    "Google Ads API",
    "GA4",
    "Meta Pixel"
   ],
   "prompt": "Goal: Instrument conversion tracking in an afternoon, repeatably.\nSetup: agents used in source: Claude; tools/MCPs stated: Google Tag Manager API, Google Ads API, GA4, Meta Pixel.\nSteps:\n1. In your app repo, have Claude Code add a dataLayer.push for every key event (signup, demo booked, trial started, checkout).\n2. Create a Google Cloud project, enable the Tag Manager API and set up OAuth with tagmanager.edit.containers and tagmanager.publish scopes.\n3. Have it create each conversion action via the Google Ads API to get IDs and labels.\n4. Have it write a script that builds, in a new GTM workspace: a custom-event trigger per event, GA4 event tags, Ads conversion tags, Meta pixel tags, and data-layer variables for value, currency and hashed email.\n5. The script creates a version and publishes; verify every tag fires in GTM preview mode.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Cody Schneider — https://x.com/codyschneider/status/2100645989828669785",
   "steps": [
    "In your app repo, have Claude Code add a dataLayer.push for every key event (signup, demo booked, trial started, checkout).",
    "Create a Google Cloud project, enable the Tag Manager API and set up OAuth with tagmanager.edit.containers and tagmanager.publish scopes.",
    "Have it create each conversion action via the Google Ads API to get IDs and labels.",
    "Have it write a script that builds, in a new GTM workspace: a custom-event trigger per event, GA4 event tags, Ads conversion tags, Meta pixel tags, and data-layer variables for value, currency and hashed email.",
    "The script creates a version and publishes; verify every tag fires in GTM preview mode."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-17",
   "trend_score": 26.0,
   "sources": [
    {
     "author": "Cody Schneider",
     "handle": "@codyschneider",
     "url": "https://x.com/codyschneider/status/2100645989828669785",
     "platform": "x",
     "date": "2026-09-17",
     "primary": true
    }
   ]
  },
  {
   "slug": "codex-computer-use-errands",
   "url": "https://agentsetups.dev/use-case/codex-computer-use-errands/",
   "title": "Use Codex computer use for web errands",
   "summary": "Codex pulled NRCS soil data during a meeting, booked plane tickets and mirrored an iPhone to change insurance.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Do a web errand on my computer while I do something else.\nSetup: agents used in source: Codex.\nSteps:\n1. Describe the errand (e.g. pull soil survey data from the NRCS site; book plane tickets).\n2. Let computer use navigate.\n3. If a change only works in a phone app, mirror the iPhone and let it navigate there.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Nick Horob — https://x.com/NickHorob/status/2095280114409882068 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Describe the errand (e.g. pull soil survey data from the NRCS site; book plane tickets).",
    "Let computer use navigate.",
    "If a change only works in a phone app, mirror the iPhone and let it navigate there."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-02",
   "trend_score": 25.4,
   "sources": [
    {
     "author": "Nick Horob",
     "handle": "@NickHorob",
     "url": "https://x.com/NickHorob/status/2095280114409882068",
     "platform": "x",
     "date": "2026-09-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "session-second-brain",
   "url": "https://agentsetups.dev/use-case/session-second-brain/",
   "title": "Distil every coding session into searchable notes",
   "summary": "Drop a raw Claude session in, distil it into a tagged note, then search by meaning: make search q=\"…\".",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Stop re-solving the same bugs.\nSetup: agents used in source: Claude.\nSteps:\n1. After each session, feed the raw Claude transcript to a distiller that writes a tagged note.\n2. Index notes for semantic search.\n3. Query later, e.g. make search q=\"how did I do an aptos coin transfer?\".\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Rajdeep Singha — https://x.com/web3withsingh/status/2098645907617030594",
   "steps": [
    "After each session, feed the raw Claude transcript to a distiller that writes a tagged note.",
    "Index notes for semantic search.",
    "Query later, e.g. make search q=\"how did I do an aptos coin transfer?\"."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-12",
   "trend_score": 25.1,
   "sources": [
    {
     "author": "Rajdeep Singha",
     "handle": "@web3withsingh",
     "url": "https://x.com/web3withsingh/status/2098645907617030594",
     "platform": "x",
     "date": "2026-09-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "webhook-fix-architecture-locked",
   "url": "https://agentsetups.dev/use-case/webhook-fix-architecture-locked/",
   "title": "Fix a webhook bug with the architecture door locked",
   "summary": "Four-line instructions (persist first, then 200, no queue) got a minimal fix for Stripe acks before the payment row existed.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Stripe"
   ],
   "prompt": "Goal: Fix a sequencing bug in a live webhook handler without redesigning anything.\nSetup: agents used in source: Claude; tools/MCPs stated: Stripe.\nSteps:\n1. Open the handler and its test.\n2. Give terse instructions, e.g. “persist first. then 200. do not add a queue. use the store we already have.”\n3. Accept only the minimal fix and delete any unrequested design advice.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Xypher — https://x.com/Xypher_18/status/2095950543780991119",
   "steps": [
    "Open the handler and its test.",
    "Give terse instructions, e.g. “persist first. then 200. do not add a queue. use the store we already have.”",
    "Accept only the minimal fix and delete any unrequested design advice."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-04",
   "trend_score": 25.1,
   "sources": [
    {
     "author": "Xypher",
     "handle": "@Xypher_18",
     "url": "https://x.com/Xypher_18/status/2095950543780991119",
     "platform": "x",
     "date": "2026-09-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "3d-scrollytelling-site-pipeline",
   "url": "https://agentsetups.dev/use-case/3d-scrollytelling-site-pipeline/",
   "title": "Build a 3D scrollytelling site with an AI pipeline",
   "summary": "An F-15 “AeroForce” site in one sitting: Pinterest → Sketchfab → ChatGPT → Gemini → Claude Code → 60 FPS scrollytelling.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Pinterest",
    "Sketchfab",
    "ChatGPT",
    "Gemini"
   ],
   "prompt": "Goal: Make an interactive 3D product-style website without manual 3D math.\nSetup: agents used in source: Claude; tools/MCPs stated: Pinterest, Sketchfab, ChatGPT, Gemini.\nSteps:\n1. Collect visual references on Pinterest.\n2. Get a 3D model from Sketchfab.\n3. Use ChatGPT and Gemini in the pipeline before handing off to Claude Code.\n4. Have Claude Code build the 60 FPS scrollytelling site.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Himanshu Hingorani — https://x.com/himanshubuildss/status/2103246725276475497 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Collect visual references on Pinterest.",
    "Get a 3D model from Sketchfab.",
    "Use ChatGPT and Gemini in the pipeline before handing off to Claude Code.",
    "Have Claude Code build the 60 FPS scrollytelling site."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 24.7,
   "sources": [
    {
     "author": "Himanshu Hingorani",
     "handle": "@himanshubuildss",
     "url": "https://x.com/himanshubuildss/status/2103246725276475497",
     "platform": "x",
     "date": "2026-09-24",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-md-structure-not-size-cap",
   "url": "https://agentsetups.dev/use-case/claude-md-structure-not-size-cap/",
   "title": "Test CLAUDE.md structure, not just its size",
   "summary": "A shop agent’s CLAUDE.md, split from 548KB to under a 45KB cap, regrew in 18 days; per-section limits and moving rules to skills held.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Keep my agent instruction file lean over time.\nSetup: agents used in source: Claude.\nSteps:\n1. Split a bloated CLAUDE.md into a short core plus skills.\n2. A total-size cap alone invites the wrong deletions; add structure tests (body size, line count, longest line, footer budget).\n3. When a section grows, move it into the skill that uses it (approval rules, fetch commands) instead of trimming elsewhere.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Rulestack — https://dev.to/rulestack/we-cut-claudemd-to-33kb-eighteen-days-later-it-was-45kb-again-what-a-size-cap-missed-and-a-3ha8",
   "steps": [
    "Split a bloated CLAUDE.md into a short core plus skills.",
    "A total-size cap alone invites the wrong deletions; add structure tests (body size, line count, longest line, footer budget).",
    "When a section grows, move it into the skill that uses it (approval rules, fetch commands) instead of trimming elsewhere."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-12",
   "trend_score": 24.1,
   "sources": [
    {
     "author": "Rulestack",
     "handle": "@rulestack",
     "url": "https://dev.to/rulestack/we-cut-claudemd-to-33kb-eighteen-days-later-it-was-45kb-again-what-a-size-cap-missed-and-a-3ha8",
     "platform": "devto",
     "date": "2026-09-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "things3-mcp-daily-brief",
   "url": "https://agentsetups.dev/use-case/things3-mcp-daily-brief/",
   "title": "Get a Codex daily brief with Things 3 todos",
   "summary": "A custom Things 3 MCP app loads in Claude or Codex; a scheduled morning brief checks email and suggests todos.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [
    "Things 3",
    "MCP"
   ],
   "prompt": "Goal: Turn my morning email into Things 3 todos automatically.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Things 3, MCP.\nSteps:\n1. Build an MCP (with an MCP app UI) for your todo app, here Things 3.\n2. Schedule a morning daily brief in which Codex checks all your emails.\n3. Review the suggested todos in the conversation and add them.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Martin Merschroth — https://x.com/majroth/status/2101366598766633425 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Build an MCP (with an MCP app UI) for your todo app, here Things 3.",
    "Schedule a morning daily brief in which Codex checks all your emails.",
    "Review the suggested todos in the conversation and add them."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-19",
   "trend_score": 24.0,
   "sources": [
    {
     "author": "Martin Merschroth",
     "handle": "@majroth",
     "url": "https://x.com/majroth/status/2101366598766633425",
     "platform": "x",
     "date": "2026-09-19",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-weekly-farm-order",
   "url": "https://agentsetups.dev/use-case/grokbot-weekly-farm-order/",
   "title": "Let Grok Bot place your weekly farm-store order",
   "summary": "Every Sunday a Grok Bot goes into the farm’s online store and orders the family’s raw milk, and suggests when to buy more.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Stop remembering a weekly grocery order.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Give Grok Bot access to the store’s online ordering.\n2. Schedule it every Sunday to place the standing order.\n3. Let it suggest adjustments.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Mars 🌿 — https://x.com/MarsHomestead/status/2101727559461568941 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give Grok Bot access to the store’s online ordering.",
    "Schedule it every Sunday to place the standing order.",
    "Let it suggest adjustments."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 23.8,
   "sources": [
    {
     "author": "Mars 🌿",
     "handle": "@MarsHomestead",
     "url": "https://x.com/MarsHomestead/status/2101727559461568941",
     "platform": "x",
     "date": "2026-09-20",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-kids-morning-newspaper",
   "url": "https://agentsetups.dev/use-case/grokbot-kids-morning-newspaper/",
   "title": "Print your kids a morning newspaper with Grok Bot",
   "summary": "A Grok Bot auto-prints a 6am paper: school and sports news, weather with what to wear, the schedule, a comic and a riddle.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Give my kids a fun daily briefing.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Build a Grok Bot that compiles school & sports news, weather (with what to wear), the day’s schedule, a comic, a riddle and an animal-battle bit.\n2. Have it print automatically each morning at 6am.\n3. Optional: publish it as a template on the Grok Bot marketplace.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Tommy Keeley — https://x.com/tommydotkeeley/status/2098065976033984798",
   "steps": [
    "Build a Grok Bot that compiles school & sports news, weather (with what to wear), the day’s schedule, a comic, a riddle and an animal-battle bit.",
    "Have it print automatically each morning at 6am.",
    "Optional: publish it as a template on the Grok Bot marketplace."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-10",
   "trend_score": 23.7,
   "sources": [
    {
     "author": "Tommy Keeley",
     "handle": "@tommydotkeeley",
     "url": "https://x.com/tommydotkeeley/status/2098065976033984798",
     "platform": "x",
     "date": "2026-09-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-night-shift-ec2",
   "url": "https://agentsetups.dev/use-case/hermes-night-shift-ec2/",
   "title": "Give Hermes Agent its own EC2 night shift",
   "summary": "Terraform + SSM + systemd: EventBridge starts EC2 at 11 PM, Hermes runs the job and reports to Telegram, stops at 7 AM.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "AWS EC2",
    "Terraform",
    "AWS SSM",
    "Tailscale",
    "systemd",
    "Telegram",
    "EventBridge Scheduler"
   ],
   "prompt": "Goal: Run Hermes overnight without leaving my MacBook open.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: AWS EC2, Terraform, AWS SSM, Tailscale, systemd, Telegram, EventBridge Scheduler.\nSteps:\n1. Provision an Ubuntu 24.04 EC2 box with Terraform: encrypted gp3, IMDSv2, termination protection, 0 inbound rules.\n2. Manage it with AWS SSM; use Tailscale for private shell access.\n3. Run Hermes as its own Linux user with a systemd user service; loginctl enable-linger hermes keeps it alive.\n4. Auth headless: hermes auth add openai-codex --no-browser; smoke test: hermes -z \"Reply with exactly: HERMES OK\".\n5. Telegram is the control plane (BotFather bot restricted to your user ID).\n6. EventBridge starts EC2 at 11 PM and stops it at 7 AM.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Arc — https://x.com/c199benzene/status/2103986129452384726",
   "steps": [
    "Provision an Ubuntu 24.04 EC2 box with Terraform: encrypted gp3, IMDSv2, termination protection, 0 inbound rules.",
    "Manage it with AWS SSM; use Tailscale for private shell access.",
    "Run Hermes as its own Linux user with a systemd user service; loginctl enable-linger hermes keeps it alive.",
    "Auth headless: hermes auth add openai-codex --no-browser; smoke test: hermes -z \"Reply with exactly: HERMES OK\".",
    "Telegram is the control plane (BotFather bot restricted to your user ID).",
    "EventBridge starts EC2 at 11 PM and stops it at 7 AM."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 23.7,
   "sources": [
    {
     "author": "Arc",
     "handle": "@c199benzene",
     "url": "https://x.com/c199benzene/status/2103986129452384726",
     "platform": "x",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "endurance-coach-terminal",
   "url": "https://agentsetups.dev/use-case/endurance-coach-terminal/",
   "title": "Build an endurance coach from a year of training data",
   "summary": "Fed a year of TrainingPeaks data and race goals, Claude Code found 30% of long runs in the grey zone.",
   "category": "health",
   "category_label": "Health",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "TrainingPeaks"
   ],
   "prompt": "Goal: Coach my endurance training from my own data, without hype.\nSetup: agents used in source: Claude; tools/MCPs stated: TrainingPeaks.\nSteps:\n1. Feed it a year of TrainingPeaks data, plus race goals and training times.\n2. Analyse intensity distribution (e.g. long runs in the grey zone).\n3. Recommend changes plainly, with no pep talk.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Bryan Collins — https://x.com/bryancollins/status/2104829282073616572 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Feed it a year of TrainingPeaks data, plus race goals and training times.",
    "Analyse intensity distribution (e.g. long runs in the grey zone).",
    "Recommend changes plainly, with no pep talk."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-29",
   "trend_score": 23.3,
   "sources": [
    {
     "author": "Bryan Collins",
     "handle": "@bryancollins",
     "url": "https://x.com/bryancollins/status/2104829282073616572",
     "platform": "x",
     "date": "2026-09-29",
     "primary": true
    }
   ]
  },
  {
   "slug": "amp-threads-across-two-machines",
   "url": "https://agentsetups.dev/use-case/amp-threads-across-two-machines/",
   "title": "Have Amp threads on two machines repair a server together",
   "summary": "After breaking a Mac sync server, Amp suggested a thread on each machine; they collaborated for hours, swapping files.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Amp"
   ],
   "models": [],
   "tools": [
    "Amp mobile app"
   ],
   "prompt": "Goal: Fix a service that spans two computers.\nSetup: agents used in source: Amp; tools/MCPs stated: Amp mobile app.\nSteps:\n1. Start an Amp thread on each machine involved (here a MacBook and a Mac mini).\n2. Let the threads collaborate, sharing files without SSH, through the repair.\n3. Monitor them from the Amp mobile app.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Guilherme Castro — https://x.com/skastr052/status/2098339677304435108",
   "steps": [
    "Start an Amp thread on each machine involved (here a MacBook and a Mac mini).",
    "Let the threads collaborate, sharing files without SSH, through the repair.",
    "Monitor them from the Amp mobile app."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-11",
   "trend_score": 23.0,
   "sources": [
    {
     "author": "Guilherme Castro",
     "handle": "@skastr052",
     "url": "https://x.com/skastr052/status/2098339677304435108",
     "platform": "x",
     "date": "2026-09-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "scratch-md-across-sessions",
   "url": "https://agentsetups.dev/use-case/scratch-md-across-sessions/",
   "title": "Keep a SCRATCH.md to survive 40+ long sessions",
   "summary": "Building an app over 40+ hour-long Claude Code sessions, a SCRATCH.md next to the terminal mattered more than prompts.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Keep continuity across many long agent sessions.\nSetup: agents used in source: Claude.\nSteps:\n1. Keep a text file called SCRATCH.md next to your terminal.\n2. Use it to carry state between sessions.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Kal Petkoff — https://x.com/KalPetkoff/status/2101680531045798291 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Keep a text file called SCRATCH.md next to your terminal.",
    "Use it to carry state between sessions."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 22.9,
   "sources": [
    {
     "author": "Kal Petkoff",
     "handle": "@KalPetkoff",
     "url": "https://x.com/KalPetkoff/status/2101680531045798291",
     "platform": "x",
     "date": "2026-09-20",
     "primary": true
    }
   ]
  },
  {
   "slug": "muse-community-park-proposal",
   "url": "https://agentsetups.dev/use-case/muse-community-park-proposal/",
   "title": "Turn a neighbourhood idea into a proposal with Muse",
   "summary": "@jasteinerman’s Muse researched precedents, mocked up a playground and drafted a funding roadmap and contact list.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Meta Muse"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Go from “wouldn’t it be cool if” to an actual civic proposal.\nSetup: agents used in source: Meta Muse.\nSteps:\n1. Describe the problem and the idea (e.g. a playground instead of a parking lot).\n2. Ask Muse for precedent research from other towns.\n3. Have it mock up what the space could look like.\n4. Ask for a funding roadmap and a map of who to talk to first.\n5. Make every decision yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Jake Steinerman 🌎 — https://x.com/jasteinerman/status/2099559267795702238",
   "steps": [
    "Describe the problem and the idea (e.g. a playground instead of a parking lot).",
    "Ask Muse for precedent research from other towns.",
    "Have it mock up what the space could look like.",
    "Ask for a funding roadmap and a map of who to talk to first.",
    "Make every decision yourself."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-14",
   "trend_score": 22.8,
   "sources": [
    {
     "author": "Jake Steinerman 🌎",
     "handle": "@jasteinerman",
     "url": "https://x.com/jasteinerman/status/2099559267795702238",
     "platform": "x",
     "date": "2026-09-14",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-website-for-dad",
   "url": "https://agentsetups.dev/use-case/claude-code-website-for-dad/",
   "title": "Build a parent’s portfolio site with them beside you",
   "summary": "In five hours with Claude Code and his dad next to him, a son built a site showing off decades of acting, writing and directing.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Give my dad a website for his career in acting, writing and directing.\nSetup: agents used in source: Claude.\nSteps:\n1. Sit with the person whose work it is.\n2. Build the site with Claude Code while they give input.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Brian Grover — https://x.com/briantgrover/status/2104361561875943895 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Sit with the person whose work it is.",
    "Build the site with Claude Code while they give input."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-28",
   "trend_score": 22.0,
   "sources": [
    {
     "author": "Brian Grover",
     "handle": "@briantgrover",
     "url": "https://x.com/briantgrover/status/2104361561875943895",
     "platform": "x",
     "date": "2026-09-28",
     "primary": true
    }
   ]
  },
  {
   "slug": "carousel-design-system-skill",
   "url": "https://agentsetups.dev/use-case/carousel-design-system-skill/",
   "title": "Generate on-brand carousels from text with a skill",
   "summary": "Build a design system once, wrap it in a Claude Code skill, then just write the text and get consistent carousels.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "VS Code"
   ],
   "prompt": "Goal: Make social carousels consistently without redesigning each one.\nSetup: agents used in source: Claude; tools/MCPs stated: VS Code.\nSteps:\n1. Build a design system for your carousels.\n2. Create a Claude Code skill that applies it.\n3. From then on, write the text and let the skill produce the carousels.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Moyo Oluwatuyi — https://x.com/moyoluwatuyi/status/2103825625047822653",
   "steps": [
    "Build a design system for your carousels.",
    "Create a Claude Code skill that applies it.",
    "From then on, write the text and let the skill produce the carousels."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 21.6,
   "sources": [
    {
     "author": "Moyo Oluwatuyi",
     "handle": "@moyoluwatuyi",
     "url": "https://x.com/moyoluwatuyi/status/2103825625047822653",
     "platform": "x",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "study-experts-tune-codex-config",
   "url": "https://agentsetups.dev/use-case/study-experts-tune-codex-config/",
   "title": "Have Codex study experts and tune your config",
   "summary": "One prompt: study an expert’s posts and the OpenAI docs, then propose the best Codex config, AGENTS.md and Amp plugin setup.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Codex",
    "Amp"
   ],
   "models": [],
   "tools": [
    "AGENTS.md"
   ],
   "prompt": "Goal: Optimise my agent setup from the best public advice.\nSetup: agents used in source: Codex, Amp; tools/MCPs stated: AGENTS.md.\nSteps:\n1. Prompt: “Go study <expert>’s posts and the related OpenAI Devs docs and propose the most optimal Codex config, AGENTS.md, and custom Amp plugin setup.”\n2. Review and apply the proposal.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Der.dev 🔥🛠️ — https://x.com/erd0xbc/status/2098511479972466809",
   "steps": [
    "Prompt: “Go study <expert>’s posts and the related OpenAI Devs docs and propose the most optimal Codex config, AGENTS.md, and custom Amp plugin setup.”",
    "Review and apply the proposal."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-11",
   "trend_score": 20.8,
   "sources": [
    {
     "author": "Der.dev 🔥🛠️",
     "handle": "@erd0xbc",
     "url": "https://x.com/erd0xbc/status/2098511479972466809",
     "platform": "x",
     "date": "2026-09-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "game-and-ai-trailer-one-evening",
   "url": "https://agentsetups.dev/use-case/game-and-ai-trailer-one-evening/",
   "title": "Make a game and its trailer in an evening",
   "summary": "A trucking game built with Claude Code, then an AI-made trailer; one evening of human effort plus opinions.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Ship a small game with a promo video.\nSetup: agents used in source: Claude.\nSteps:\n1. Build the game with Claude Code.\n2. Generate a trailer with AI video tools.\n3. Fine-tune both yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Dmitry Kachmar — https://x.com/dmitrykachmar/status/2103799730866135098 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Build the game with Claude Code.",
    "Generate a trailer with AI video tools.",
    "Fine-tune both yourself."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 19.5,
   "sources": [
    {
     "author": "Dmitry Kachmar",
     "handle": "@dmitrykachmar",
     "url": "https://x.com/dmitrykachmar/status/2103799730866135098",
     "platform": "x",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-ad-comment-sweep",
   "url": "https://agentsetups.dev/use-case/grokbot-ad-comment-sweep/",
   "title": "Sweep your Meta ads for negative comments daily",
   "summary": "A Grok Bot set up to sweep Meta ads for negative comments every morning.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Meta Ads"
   ],
   "prompt": "Goal: Catch negative comments on my ads fast.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Meta Ads.\nSteps:\n1. Connect Grok Bot to your Meta ads.\n2. Schedule a morning sweep for negative comments and a report.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Andrew — https://x.com/_andrewmonreal/status/2099861876825899144 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Connect Grok Bot to your Meta ads.",
    "Schedule a morning sweep for negative comments and a report."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-15",
   "trend_score": 19.3,
   "sources": [
    {
     "author": "Andrew",
     "handle": "@_andrewmonreal",
     "url": "https://x.com/_andrewmonreal/status/2099861876825899144",
     "platform": "x",
     "date": "2026-09-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "comet-file-refund-request",
   "url": "https://agentsetups.dev/use-case/comet-file-refund-request/",
   "title": "Have Comet file a refund request while you wait",
   "summary": "Stuck in a drive-thru that wouldn’t take his app order, @RyanJoseph had Comet’s assistant file the refund before he left.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Comet"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Get a refund filed without fighting a support form.\nSetup: agents used in source: Comet.\nSteps:\n1. Ask the Comet assistant to file the refund request for the order.\n2. Let it complete the flow; check for the refund.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Ryan Joseph — https://x.com/RyanJoseph/status/2095595106556359133 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask the Comet assistant to file the refund request for the order.",
    "Let it complete the flow; check for the refund."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-03",
   "trend_score": 19.1,
   "sources": [
    {
     "author": "Ryan Joseph",
     "handle": "@RyanJoseph",
     "url": "https://x.com/RyanJoseph/status/2095595106556359133",
     "platform": "x",
     "date": "2026-09-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-blender-to-threejs-scene",
   "url": "https://agentsetups.dev/use-case/dots-blender-to-threejs-scene/",
   "title": "Model a retro camera in Blender and walk it in Three.js",
   "summary": "A Dot named Max helped model a retro camera (4,998 triangles) and put it in a playable Three.js scene.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "Blender",
    "Three.js"
   ],
   "prompt": "Goal: Make a small 3D interactive scene with my Dot.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Blender, Three.js.\nSteps:\n1. Model the object in Blender and optimise the mesh (here under 5,000 triangles).\n2. Bring it into a Three.js scene with walking and interactions (take a photo, pick up the print).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Gürsel Günacar — https://x.com/mech_eng_dev/status/2105381046044815388 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Model the object in Blender and optimise the mesh (here under 5,000 triangles).",
    "Bring it into a Three.js scene with walking and interactions (take a photo, pick up the print)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 18.5,
   "sources": [
    {
     "author": "Gürsel Günacar",
     "handle": "@mech_eng_dev",
     "url": "https://x.com/mech_eng_dev/status/2105381046044815388",
     "platform": "x",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-design-skills-figma-mcp",
   "url": "https://agentsetups.dev/use-case/claude-design-skills-figma-mcp/",
   "title": "Stop AI-slop landing pages with design skills",
   "summary": "Install the Impeccable and Taste skills, wire up the Figma MCP for references, then let Claude Code build and test.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Impeccable skill",
    "Taste Skill",
    "Figma MCP"
   ],
   "prompt": "Goal: Get Claude to design landing pages that don’t look generic.\nSetup: agents used in source: Claude; tools/MCPs stated: Impeccable skill, Taste Skill, Figma MCP.\nSteps:\n1. Install the Impeccable skill and point it at a designer’s taste (the author uses Emil Kowalski’s) for spacing, type and motion vocabulary.\n2. Add the Taste Skill set for modern UI.\n3. Wire up the Figma MCP so it designs from real references.\n4. Have Claude Code build and test the result, not just describe it.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Massimo — https://x.com/Mas_simooo/status/2102754141831299132",
   "steps": [
    "Install the Impeccable skill and point it at a designer’s taste (the author uses Emil Kowalski’s) for spacing, type and motion vocabulary.",
    "Add the Taste Skill set for modern UI.",
    "Wire up the Figma MCP so it designs from real references.",
    "Have Claude Code build and test the result, not just describe it."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 18.4,
   "sources": [
    {
     "author": "Massimo",
     "handle": "@Mas_simooo",
     "url": "https://x.com/Mas_simooo/status/2102754141831299132",
     "platform": "x",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "agents-shared-memory-energon",
   "url": "https://agentsetups.dev/use-case/agents-shared-memory-energon/",
   "title": "Give Instinct, Muse and Grok Bot one shared memory",
   "summary": "@trevin deployed his own Energon instance, installed its skill in each agent and minted each its own API key.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Grok Bot",
    "Meta Muse",
    "Instinct"
   ],
   "models": [],
   "tools": [
    "Energon"
   ],
   "prompt": "Goal: Let my different personal agents share information with me and with each other.\nSetup: agents used in source: Grok Bot, Meta Muse, Instinct; tools/MCPs stated: Energon.\nSteps:\n1. Deploy your own Energon instance.\n2. Have each agent (Instinct, Muse, Grok Bot) install the agent skill.\n3. Mint each agent its own API key so they can share info.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Trevin Chow — https://x.com/trevin/status/2100817397536137359",
   "steps": [
    "Deploy your own Energon instance.",
    "Have each agent (Instinct, Muse, Grok Bot) install the agent skill.",
    "Mint each agent its own API key so they can share info."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-18",
   "trend_score": 17.9,
   "sources": [
    {
     "author": "Trevin Chow",
     "handle": "@trevin",
     "url": "https://x.com/trevin/status/2100817397536137359",
     "platform": "x",
     "date": "2026-09-18",
     "primary": true
    }
   ]
  },
  {
   "slug": "pi-plugin-compact-tool-output",
   "url": "https://agentsetups.dev/use-case/pi-plugin-compact-tool-output/",
   "title": "Compact tool output in Pi with a plugin",
   "summary": "Moving daily work to Pi, a developer built his first plugin to compact tool output, borrowing the Codex App’s design.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Pi"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Cut noisy tool output in my Pi sessions.\nSetup: agents used in source: Pi.\nSteps:\n1. Write a Pi plugin that compacts tool output (modelled on how the Codex App does it).\n2. Install it into your daily Pi setup.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Mason — https://x.com/chenjingtalk/status/2095096236164665587 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Write a Pi plugin that compacts tool output (modelled on how the Codex App does it).",
    "Install it into your daily Pi setup."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-02",
   "trend_score": 17.5,
   "sources": [
    {
     "author": "Mason",
     "handle": "@chenjingtalk",
     "url": "https://x.com/chenjingtalk/status/2095096236164665587",
     "platform": "x",
     "date": "2026-09-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-budget-gear-research",
   "url": "https://agentsetups.dev/use-case/grokbot-budget-gear-research/",
   "title": "Send Grok Bot back with a budget and a specific job",
   "summary": "First picks were $2–3k cameras; with a budget and “real estate photos” it landed on a used Canon EOS RP + 16mm under $900.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Get practical gear recommendations for a new small business.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Ask for recommendations.\n2. If they’re too expensive, send it back with a budget and the specific job (e.g. listing photos: whole rooms, bright windows, gloomy days).\n3. Iterate a few rounds, then sanity-check the shortlist with practitioners.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Mars 🌿 — https://x.com/MarsHomestead/status/2096654000842297459",
   "steps": [
    "Ask for recommendations.",
    "If they’re too expensive, send it back with a budget and the specific job (e.g. listing photos: whole rooms, bright windows, gloomy days).",
    "Iterate a few rounds, then sanity-check the shortlist with practitioners."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-06",
   "trend_score": 17.4,
   "sources": [
    {
     "author": "Mars 🌿",
     "handle": "@MarsHomestead",
     "url": "https://x.com/MarsHomestead/status/2096654000842297459",
     "platform": "x",
     "date": "2026-09-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "three-models-same-feature-benchmark",
   "url": "https://agentsetups.dev/use-case/three-models-same-feature-benchmark/",
   "title": "Benchmark models by building one feature in your repo",
   "summary": "Same contract, isolated envs: 47 hidden tests, 4 contract mutations and a binary check. Opus killed 4/4 mutants at 100× the cost.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "GPT-5.6 Luna",
    "DeepSeek V4.1 Flash",
    "Claude Opus 5"
   ],
   "tools": [
    "mutation testing"
   ],
   "prompt": "Goal: Pick the right model for my real work, not public benchmarks.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: mutation testing.\nSteps:\n1. Pick a real mid-size slice of your project and write the contract.\n2. Have each model build it in isolated environments (Claude Code and Codex).\n3. Before looking at any build, write hidden tests from the contract alone (47 here).\n4. Mutate the contract (4 mutations) and run each model’s own tests against them.\n5. Check behaviour on the real binary by hand; compare cost and wall time.\n6. Review the contract before dispatching: that’s where the expensive model earned its keep.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Damian Pala — https://x.com/iamdamianpala/status/2098086060081221977",
   "steps": [
    "Pick a real mid-size slice of your project and write the contract.",
    "Have each model build it in isolated environments (Claude Code and Codex).",
    "Before looking at any build, write hidden tests from the contract alone (47 here).",
    "Mutate the contract (4 mutations) and run each model’s own tests against them.",
    "Check behaviour on the real binary by hand; compare cost and wall time.",
    "Review the contract before dispatching: that’s where the expensive model earned its keep."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-10",
   "trend_score": 16.3,
   "sources": [
    {
     "author": "Damian Pala",
     "handle": "@iamdamianpala",
     "url": "https://x.com/iamdamianpala/status/2098086060081221977",
     "platform": "x",
     "date": "2026-09-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "fantasy-auction-repricing-tool",
   "url": "https://agentsetups.dev/use-case/fantasy-auction-repricing-tool/",
   "title": "Win a fantasy auction with a live repricing tool",
   "summary": "Claude Code built a tool that reprices every player after every pick; ~1,000 simulated drafts; #1 projected roster of 16 teams.",
   "category": "data-analysis",
   "category_label": "Data analysis",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Beat a static spreadsheet of player values in a $400 auction draft.\nSetup: agents used in source: Claude.\nSteps:\n1. Build a tool with Claude Code that reprices every player after every pick.\n2. Run ~1,000 simulated drafts against it.\n3. Use it live during the auction.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Spr3adsh33t — https://x.com/spr3adsh33t/status/2095940294277472294 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Build a tool with Claude Code that reprices every player after every pick.",
    "Run ~1,000 simulated drafts against it.",
    "Use it live during the auction."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-04",
   "trend_score": 14.1,
   "sources": [
    {
     "author": "Spr3adsh33t",
     "handle": "@spr3adsh33t",
     "url": "https://x.com/spr3adsh33t/status/2095940294277472294",
     "platform": "x",
     "date": "2026-09-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "gym-remote-mac-mini-agents",
   "url": "https://agentsetups.dev/use-case/gym-remote-mac-mini-agents/",
   "title": "Build from your phone at the gym via a Mac mini",
   "summary": "Running Claude Code and Codex on a home Mac mini from his phone, he built video-editing software during a 45-minute workout.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "GPT-6 Astra"
   ],
   "tools": [
    "Mac mini"
   ],
   "prompt": "Goal: Keep building while I’m away from my desk.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Mac mini.\nSteps:\n1. Run Claude Code and Codex on a Mac mini at home.\n2. Control them from your phone during the workout.\n3. Fix bugs, then update your clip-analysis “brain” (here with Astra: slop, inconsistencies, pacing, attention score).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: darin stewart — https://x.com/bydarinstewart/status/2098196667090743386",
   "steps": [
    "Run Claude Code and Codex on a Mac mini at home.",
    "Control them from your phone during the workout.",
    "Fix bugs, then update your clip-analysis “brain” (here with Astra: slop, inconsistencies, pacing, attention score)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-10",
   "trend_score": 14.0,
   "sources": [
    {
     "author": "darin stewart",
     "handle": "@bydarinstewart",
     "url": "https://x.com/bydarinstewart/status/2098196667090743386",
     "platform": "x",
     "date": "2026-09-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "amp-orbs-watch-github-issues",
   "url": "https://agentsetups.dev/use-case/amp-orbs-watch-github-issues/",
   "title": "Let Amp orbs pick up your team’s GitHub issues",
   "summary": "Small projects on GitHub; Amp orbs monitor issues the team files; Puck handles simple tasks; Vercel deploys main.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Amp"
   ],
   "models": [],
   "tools": [
    "Vercel",
    "Ollama"
   ],
   "prompt": "Goal: Have background agents work issues for a small team.\nSetup: agents used in source: Amp; tools/MCPs stated: Vercel, Ollama.\nSteps:\n1. Host the codebase on GitHub.\n2. Have Amp orbs monitor GitHub issues as your team creates them.\n3. Treat Puck like an infra teammate for simple tasks.\n4. Deploy on Vercel with CI/CD publishing main.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: AriesTheCoder — https://x.com/AriesTheCoder/status/2103973089122116055",
   "steps": [
    "Host the codebase on GitHub.",
    "Have Amp orbs monitor GitHub issues as your team creates them.",
    "Treat Puck like an infra teammate for simple tasks.",
    "Deploy on Vercel with CI/CD publishing main."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 13.7,
   "sources": [
    {
     "author": "AriesTheCoder",
     "handle": "@AriesTheCoder",
     "url": "https://x.com/AriesTheCoder/status/2103973089122116055",
     "platform": "x",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-hindsight-memory-graph",
   "url": "https://agentsetups.dev/use-case/hermes-hindsight-memory-graph/",
   "title": "Give Hermes a long-term memory graph",
   "summary": "Seeding the Hindsight memory plugin cost $0.85 on DeepSeek Flash; day-to-day extraction then ran on local models with a fallback.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Hermes Agent"
   ],
   "models": [
    "DeepSeek Flash"
   ],
   "tools": [
    "Hindsight",
    "Docker",
    "Ollama"
   ],
   "prompt": "Goal: Replace a capped markdown scratchpad with memory that knows what is stale.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: Hindsight, Docker, Ollama.\nSteps:\n1. Run the Hindsight memory provider plugin in a Docker container next to Hermes.\n2. Do the bulk seeding with a cheap cloud model (here ~2 hours, 537 calls, $0.85).\n3. Switch daily extraction to a local model with a lighter fallback machine.\n4. When a fact changes, mark the old memory invalidated with a reason instead of writing more text to contradict it.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/PoppaBear1950 — https://www.reddit.com/r/hermesagent/comments/1wqv98w/giving_hermes_agent_a_longterm_brain_what_seeding/",
   "steps": [
    "Run the Hindsight memory provider plugin in a Docker container next to Hermes.",
    "Do the bulk seeding with a cheap cloud model (here ~2 hours, 537 calls, $0.85).",
    "Switch daily extraction to a local model with a lighter fallback machine.",
    "When a fact changes, mark the old memory invalidated with a reason instead of writing more text to contradict it."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 11.3,
   "sources": [
    {
     "author": "/u/PoppaBear1950",
     "handle": "/u/PoppaBear1950",
     "url": "https://www.reddit.com/r/hermesagent/comments/1wqv98w/giving_hermes_agent_a_longterm_brain_what_seeding/",
     "platform": "reddit",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "cline-plan-mode-parallel-prs",
   "url": "https://agentsetups.dev/use-case/cline-plan-mode-parallel-prs/",
   "title": "Write PR specs first, then build in parallel with Cline",
   "summary": "Three people built a config-driven game: detailed PR descriptions, Plan mode before Act, and a setup PR that locked shared types.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Cline"
   ],
   "models": [],
   "tools": [
    "Plan mode"
   ],
   "prompt": "Goal: Let several people build with agents at once without merge chaos.\nSetup: agents used in source: Cline; tools/MCPs stated: Plan mode.\nSteps:\n1. Before any code, write each PR’s description: files touched, rules, edge cases, what tests should check.\n2. Land one setup PR that locks in the shared types.\n3. Each person takes their own PRs into Cline, starts in Plan mode to confirm the approach, then switches to Act.\n4. Work in separate folders (engine, components, pages); connect everything in the last PR.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Few-Ad-5053 — https://www.reddit.com/r/CLine/comments/1wnrjs6/used_cline_to_build_a_configdriven_game_sandbox/",
   "steps": [
    "Before any code, write each PR’s description: files touched, rules, edge cases, what tests should check.",
    "Land one setup PR that locks in the shared types.",
    "Each person takes their own PRs into Cline, starts in Plan mode to confirm the approach, then switches to Act.",
    "Work in separate folders (engine, components, pages); connect everything in the last PR."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-23",
   "trend_score": 11.0,
   "sources": [
    {
     "author": "/u/Few-Ad-5053",
     "handle": "/u/Few-Ad-5053",
     "url": "https://www.reddit.com/r/CLine/comments/1wnrjs6/used_cline_to_build_a_configdriven_game_sandbox/",
     "platform": "reddit",
     "date": "2026-09-23",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-email-drafts-never-send",
   "url": "https://agentsetups.dev/use-case/n8n-email-drafts-never-send/",
   "title": "Draft email replies with AI but never auto-send",
   "summary": "Skips automated senders, drafts a short reply into Gmail Drafts, and pings Slack for review. Sending stays out of the automation.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "Gmail",
    "Slack",
    "Google Sheets"
   ],
   "prompt": "Goal: Have replies ready to review without risking an AI email going out unchecked.\nSetup: agents used in source: n8n; tools/MCPs stated: Gmail, Slack, Google Sheets.\nSteps:\n1. Filter out automated senders (no-reply, notifications, mailer-daemon, calendar invites, receipts).\n2. Skip threads you already replied to or that already have a draft.\n3. Have the AI draft a short, professional reply and save it to Gmail Drafts.\n4. Send a Slack ping with a one-line reason that the draft is ready.\n5. Optionally log thread id, draft id, recipient, subject and reason to a Google Sheet.\n6. Never wire the send action into the workflow.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Limbox0 — https://www.reddit.com/r/n8n/comments/1wqpkvk/built_an_n8n_workflow_that_drafts_email_replies/",
   "steps": [
    "Filter out automated senders (no-reply, notifications, mailer-daemon, calendar invites, receipts).",
    "Skip threads you already replied to or that already have a draft.",
    "Have the AI draft a short, professional reply and save it to Gmail Drafts.",
    "Send a Slack ping with a one-line reason that the draft is ready.",
    "Optionally log thread id, draft id, recipient, subject and reason to a Google Sheet.",
    "Never wire the send action into the workflow."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 11.0,
   "sources": [
    {
     "author": "/u/Limbox0",
     "handle": "/u/Limbox0",
     "url": "https://www.reddit.com/r/n8n/comments/1wqpkvk/built_an_n8n_workflow_that_drafts_email_replies/",
     "platform": "reddit",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-llm-cost-per-workflow",
   "url": "https://agentsetups.dev/use-case/n8n-llm-cost-per-workflow/",
   "title": "Find which workflow is eating your LLM bill",
   "summary": "Summing token use per n8n workflow showed one Reddit scout was 75% of a $58/month Claude bill; fixing it cut the bill to about $5.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "n8n executions"
   ],
   "prompt": "Goal: Cut LLM spend by measuring cost per workflow instead of per invoice.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n executions.\nSteps:\n1. Sum token usage from your own n8n executions per workflow and per model.\n2. Find the workflow that dominates; check how often it actually runs.\n3. Check what is actually published, not just saved (a saved but unpublished schedule kept the old version running).\n4. Watch editor-assistant usage on the largest model; one day of it cost as much as a month of production.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: The author found downgrading cheap workflows to a smaller model saved only about $1/month.\nBased on: /u/Competitive-Joke-408 — https://www.reddit.com/r/n8n/comments/1wu5xjg/one_workflow_was_75_of_my_llm_bill_how_i_measured/",
   "steps": [
    "Sum token usage from your own n8n executions per workflow and per model.",
    "Find the workflow that dominates; check how often it actually runs.",
    "Check what is actually published, not just saved (a saved but unpublished schedule kept the old version running).",
    "Watch editor-assistant usage on the largest model; one day of it cost as much as a month of production."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 10.8,
   "sources": [
    {
     "author": "/u/Competitive-Joke-408",
     "handle": "/u/Competitive-Joke-408",
     "url": "https://www.reddit.com/r/n8n/comments/1wu5xjg/one_workflow_was_75_of_my_llm_bill_how_i_measured/",
     "platform": "reddit",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-marketplace-deal-hunter",
   "url": "https://agentsetups.dev/use-case/grokbot-marketplace-deal-hunter/",
   "title": "Find Facebook Marketplace deals and message sellers",
   "summary": "A first Grok Bot routine: every morning find absurd tech deals on Facebook Marketplace and message the sellers.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Facebook Marketplace"
   ],
   "prompt": "Goal: Catch underpriced tech before others do.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Facebook Marketplace.\nSteps:\n1. Set up a morning routine to scan Facebook Marketplace for tech deals.\n2. Have it message sellers on your behalf.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: 🇮🇱 Offred 🇺🇦 — https://x.com/OffredPosts/status/2095381620198871194",
   "steps": [
    "Set up a morning routine to scan Facebook Marketplace for tech deals.",
    "Have it message sellers on your behalf."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-03",
   "trend_score": 9.9,
   "sources": [
    {
     "author": "🇮🇱 Offred 🇺🇦",
     "handle": "@OffredPosts",
     "url": "https://x.com/OffredPosts/status/2095381620198871194",
     "platform": "x",
     "date": "2026-09-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "pplx-computer-room-redesign-ikea",
   "url": "https://agentsetups.dev/use-case/pplx-computer-room-redesign-ikea/",
   "title": "Plan a room makeover with IKEA parts in Perplexity Computer",
   "summary": "Before buying anything: five styled, to-scale 3D designs of an 11×11 ft basement room with real IKEA parts and prices, in one chat.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Perplexity Computer"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "IKEA"
   ],
   "prompt": "Goal: Turn my small basement bedroom into an office + treadmill room before buying anything.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: IKEA.\nSteps:\n1. Give Perplexity Computer the room dimensions and the target use.\n2. Ask for several styled 3D designs, to scale, using real IKEA parts with prices.\n3. Have it build and deploy the result as a page you can browse.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Vinay Menon — https://x.com/menonvi/status/2103657912979915174 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give Perplexity Computer the room dimensions and the target use.",
    "Ask for several styled 3D designs, to scale, using real IKEA parts with prices.",
    "Have it build and deploy the result as a page you can browse."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-26",
   "trend_score": 8.9,
   "sources": [
    {
     "author": "Vinay Menon",
     "handle": "@menonvi",
     "url": "https://x.com/menonvi/status/2103657912979915174",
     "platform": "x",
     "date": "2026-09-26",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-product-explainer-video",
   "url": "https://agentsetups.dev/use-case/claude-code-product-explainer-video/",
   "title": "Have Claude Code make a product explainer video",
   "summary": "One prompt, an OpenRouter key capped at $10 and ~2 hours unattended: script, art, voice, music, a JS canvas animation rendered to MP4. ~$4.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "OpenRouter",
    "text-to-speech"
   ],
   "prompt": "Goal: Get a usable 30–60 s explainer for my product without a video team.\nSetup: agents used in source: Claude; tools/MCPs stated: OpenRouter, text-to-speech.\nSteps:\n1. Put an OpenRouter key with a spending cap in the project’s .env.\n2. Prompt Claude Code: create a pure JavaScript animation, 30–60 s, whimsical hand-drawn collage style with audio, as high production value as possible; read the FAQ first; use a high-quality TTS model.\n3. Walk away; it writes the script, generates art, voice, music and effects, syncs beats to words and renders to MP4.\n4. Have another model review the drafts; ask for other language versions afterwards.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Dio-V — https://www.reddit.com/r/ClaudeAI/comments/1wovwao/jaw_literally_dropped_i_ran_the_prompt_from_the/",
   "steps": [
    "Put an OpenRouter key with a spending cap in the project’s .env.",
    "Prompt Claude Code: create a pure JavaScript animation, 30–60 s, whimsical hand-drawn collage style with audio, as high production value as possible; read the FAQ first; use a high-quality TTS model.",
    "Walk away; it writes the script, generates art, voice, music and effects, syncs beats to words and renders to MP4.",
    "Have another model review the drafts; ask for other language versions afterwards."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-24",
   "trend_score": 8.5,
   "sources": [
    {
     "author": "/u/Dio-V",
     "handle": "/u/Dio-V",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wovwao/jaw_literally_dropped_i_ran_the_prompt_from_the/",
     "platform": "reddit",
     "date": "2026-09-24",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-54-hour-minecraft-mod",
   "url": "https://agentsetups.dev/use-case/claude-code-54-hour-minecraft-mod/",
   "title": "Let Claude Code build a full Minecraft mod for 54 hours",
   "summary": "Opus in Claude Code wrote the design doc, code, models and boss AI, built its own test client and used 48 subagents; ~$2,032 at API prices.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "NeoForge",
    "ElevenLabs"
   ],
   "prompt": "Goal: See how far a long unattended agent run can take a game mod.\nSetup: agents used in source: Claude; tools/MCPs stated: NeoForge, ElevenLabs.\nSteps:\n1. Give Claude Code the idea (here a new dimension in four layers, each ending in a boss) and let it run.\n2. Let it write the design doc, then the code, models, animations and boss AI.\n3. Have it build its own test harness: a hidden game client that plays the mod, takes screenshots and checks its work.\n4. Hand heavy lifting to subagents with the main session reviewing their work.\n5. Have it check generated voice lines by transcribing them back.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: The author was on a Max plan; $2,032 is what the usage would have cost at API prices.\nBased on: /u/Bonelessgummybear — https://www.reddit.com/r/vibecoding/comments/1wuh0nz/i_let_opus_55_run_for_54_hours_straight_and_it/",
   "steps": [
    "Give Claude Code the idea (here a new dimension in four layers, each ending in a boss) and let it run.",
    "Let it write the design doc, then the code, models, animations and boss AI.",
    "Have it build its own test harness: a hidden game client that plays the mod, takes screenshots and checks its work.",
    "Hand heavy lifting to subagents with the main session reviewing their work.",
    "Have it check generated voice lines by transcribing them back."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 8.0,
   "sources": [
    {
     "author": "/u/Bonelessgummybear",
     "handle": "/u/Bonelessgummybear",
     "url": "https://www.reddit.com/r/vibecoding/comments/1wuh0nz/i_let_opus_55_run_for_54_hours_straight_and_it/",
     "platform": "reddit",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-whatsapp-voice-notes-to-tasks",
   "url": "https://agentsetups.dev/use-case/n8n-whatsapp-voice-notes-to-tasks/",
   "title": "Turn WhatsApp voice notes into tasks and CRM updates",
   "summary": "Transcribe each voice note, let an LLM classify the intent, then route it to a task, CRM update, archive or human review.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "WhatsApp",
    "CRM"
   ],
   "prompt": "Goal: Stop losing decisions buried in unsearchable voice notes.\nSetup: agents used in source: n8n; tools/MCPs stated: WhatsApp, CRM.\nSteps:\n1. Transcribe incoming WhatsApp voice notes.\n2. Have an LLM analyse each note’s intent.\n3. Route by intent: create a task, update the CRM, archive, or send to human review.\n4. Keep each stage independent so you can swap it for your own process.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Optiflix — https://www.reddit.com/r/n8n/comments/1wn9xlo/built_an_n8n_workflow_that_turns_whatsapp_voice/",
   "steps": [
    "Transcribe incoming WhatsApp voice notes.",
    "Have an LLM analyse each note’s intent.",
    "Route by intent: create a task, update the CRM, archive, or send to human review.",
    "Keep each stage independent so you can swap it for your own process."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-22",
   "trend_score": 7.6,
   "sources": [
    {
     "author": "/u/Optiflix",
     "handle": "/u/Optiflix",
     "url": "https://www.reddit.com/r/n8n/comments/1wn9xlo/built_an_n8n_workflow_that_turns_whatsapp_voice/",
     "platform": "reddit",
     "date": "2026-09-22",
     "primary": true
    }
   ]
  },
  {
   "slug": "atlas-airline-refund-forms",
   "url": "https://agentsetups.dev/use-case/atlas-airline-refund-forms/",
   "title": "Let ChatGPT Atlas fill an airline refund request",
   "summary": "ChatGPT Atlas filled out all the forms and correspondence for an airline refund request.",
   "category": "travel",
   "category_label": "Travel",
   "agents": [
    "ChatGPT Atlas"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Submit an airline refund without doing the forms myself.\nSetup: agents used in source: ChatGPT Atlas.\nSteps:\n1. Open the airline’s refund page in ChatGPT Atlas.\n2. Ask the agent to submit the refund request, filling the forms and writing the correspondence.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: MilesOfFun — https://x.com/MileRadujko/status/2096830088058720424 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Open the airline’s refund page in ChatGPT Atlas.",
    "Ask the agent to submit the refund request, filling the forms and writing the correspondence."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-07",
   "trend_score": 6.5,
   "sources": [
    {
     "author": "MilesOfFun",
     "handle": "@MileRadujko",
     "url": "https://x.com/MileRadujko/status/2096830088058720424",
     "platform": "x",
     "date": "2026-09-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-job-search-engine",
   "url": "https://agentsetups.dev/use-case/claude-code-job-search-engine/",
   "title": "Have Claude Code read job postings against your CV",
   "summary": "A coding agent pulls the day’s postings with a CLI, reads each against your résumé and preferences, and lists good fits with reasons.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Pinloop CLI"
   ],
   "prompt": "Goal: Only spend time on job postings that actually fit me.\nSetup: agents used in source: Claude; tools/MCPs stated: Pinloop CLI.\nSteps:\n1. Install the CLI and let your coding agent run its welcome guide.\n2. Schedule a daily pull of new postings.\n3. Have the agent read each posting against your résumé and preferences and write a verdict with its reasoning.\n4. Check the list of good fits each morning and apply yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/parfumparrot — https://www.reddit.com/r/AI_Agents/comments/1wicroc/i_built_a_job_search_engine_for_claude_code_1000/",
   "steps": [
    "Install the CLI and let your coding agent run its welcome guide.",
    "Schedule a daily pull of new postings.",
    "Have the agent read each posting against your résumé and preferences and write a verdict with its reasoning.",
    "Check the list of good fits each morning and apply yourself."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-16",
   "trend_score": 6.1,
   "sources": [
    {
     "author": "/u/parfumparrot",
     "handle": "/u/parfumparrot",
     "url": "https://www.reddit.com/r/AI_Agents/comments/1wicroc/i_built_a_job_search_engine_for_claude_code_1000/",
     "platform": "reddit",
     "date": "2026-09-16",
     "primary": true
    }
   ]
  },
  {
   "slug": "cowork-sets-up-claude-code-build",
   "url": "https://agentsetups.dev/use-case/cowork-sets-up-claude-code-build/",
   "title": "Have Cowork set up your machine, then Claude Code builds",
   "summary": "Claude turned a Roblox game idea into a 26-step checklist; Cowork ran the setup on the computer, then Claude Code took over.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Roblox"
   ],
   "prompt": "Goal: Go from game idea to a working dev setup without doing the setup myself.\nSetup: agents used in source: Claude; tools/MCPs stated: Roblox.\nSteps:\n1. Describe the game idea to Claude and say Cowork will do the setup.\n2. Have Claude write a step-by-step setup checklist for Cowork.\n3. Let Cowork run through it on your computer.\n4. Hand off to Claude Code to build the game.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Isiah — https://x.com/forevertawl/status/2105271541919322523",
   "steps": [
    "Describe the game idea to Claude and say Cowork will do the setup.",
    "Have Claude write a step-by-step setup checklist for Cowork.",
    "Let Cowork run through it on your computer.",
    "Hand off to Claude Code to build the game."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 5.8,
   "sources": [
    {
     "author": "Isiah",
     "handle": "@forevertawl",
     "url": "https://x.com/forevertawl/status/2105271541919322523",
     "platform": "x",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "codex-runs-canvas-ecom-brand",
   "url": "https://agentsetups.dev/use-case/codex-runs-canvas-ecom-brand/",
   "title": "Let Codex build and run a print-on-demand brand",
   "summary": "GPT-6 Astra in Codex built the brand, 270 artworks, product photos, a storefront and Meta ads; the first $64 order came from its ads.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Codex"
   ],
   "models": [
    "GPT-6 Astra"
   ],
   "tools": [
    "Shopify",
    "Printful",
    "Vercel",
    "Meta Ads Manager"
   ],
   "prompt": "Goal: Test whether an agent can start and run a small e-commerce business with me only reviewing.\nSetup: agents used in source: Codex; tools/MCPs stated: Shopify, Printful, Vercel, Meta Ads Manager.\nSteps:\n1. Have it research top brands in the niche and reverse-engineer their style, site, ads and social.\n2. Generate the art, reject anything that looks obviously AI, and order test prints to inspect quality yourself.\n3. Have it build a storefront connected to Shopify checkout and print-on-demand, mapping every size variant to the right print file.\n4. Have it reverse-engineer winning ads from the ad library and set up the campaign itself in the browser.\n5. Keep accounts, billing, business verification and quality control for yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Rare_Guide_9830 — https://www.reddit.com/r/vibecoding/comments/1wpzale/gpt6_astra_made_me_an_ecom_brand_built_the_ad/",
   "steps": [
    "Have it research top brands in the niche and reverse-engineer their style, site, ads and social.",
    "Generate the art, reject anything that looks obviously AI, and order test prints to inspect quality yourself.",
    "Have it build a storefront connected to Shopify checkout and print-on-demand, mapping every size variant to the right print file.",
    "Have it reverse-engineer winning ads from the ad library and set up the campaign itself in the browser.",
    "Keep accounts, billing, business verification and quality control for yourself."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-25",
   "trend_score": 5.6,
   "sources": [
    {
     "author": "/u/Rare_Guide_9830",
     "handle": "/u/Rare_Guide_9830",
     "url": "https://www.reddit.com/r/vibecoding/comments/1wpzale/gpt6_astra_made_me_an_ecom_brand_built_the_ad/",
     "platform": "reddit",
     "date": "2026-09-25",
     "primary": true
    }
   ]
  },
  {
   "slug": "muse-renters-insurance-quotes",
   "url": "https://agentsetups.dev/use-case/muse-renters-insurance-quotes/",
   "title": "Have Meta Muse compare renters insurance quotes",
   "summary": "Muse found a renters policy was cancelled and overpriced, logged into GEICO, reviewed it and ran 6 quote comparisons in a table.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Meta Muse"
   ],
   "models": [],
   "tools": [
    "GEICO"
   ],
   "prompt": "Goal: Check my renters insurance and find a better price.\nSetup: agents used in source: Meta Muse; tools/MCPs stated: GEICO.\nSteps:\n1. Give the Muse agent your insurer login.\n2. Have it review the current policy.\n3. Have it submit quote comparisons and build a coverage table.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Blake — https://x.com/devwithblake/status/2101757781313548306 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give the Muse agent your insurer login.",
    "Have it review the current policy.",
    "Have it submit quote comparisons and build a coverage table."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-20",
   "trend_score": 4.8,
   "sources": [
    {
     "author": "Blake",
     "handle": "@devwithblake",
     "url": "https://x.com/devwithblake/status/2101757781313548306",
     "platform": "x",
     "date": "2026-09-20",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-spoken-morning-digest",
   "url": "https://agentsetups.dev/use-case/hermes-spoken-morning-digest/",
   "title": "Give your Hermes morning digest a voice",
   "summary": "Hermes’ cron jobs dropped a text digest he scrolled past; adding a voice so it talks to you took about 5 minutes.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "cron"
   ],
   "prompt": "Goal: Actually listen to my morning digest instead of skipping it.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: cron.\nSteps:\n1. Keep the Hermes cron jobs that build the morning digest.\n2. Add a voice output so it speaks the digest.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: AI Music Tools — https://x.com/didieonweb/status/2099408475755540888 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Keep the Hermes cron jobs that build the morning digest.",
    "Add a voice output so it speaks the digest."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-14",
   "trend_score": 4.3,
   "sources": [
    {
     "author": "AI Music Tools",
     "handle": "@didieonweb",
     "url": "https://x.com/didieonweb/status/2099408475755540888",
     "platform": "x",
     "date": "2026-09-14",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-trustpilot-review-alerts",
   "url": "https://agentsetups.dev/use-case/n8n-trustpilot-review-alerts/",
   "title": "Get alerts and a weekly digest of new reviews",
   "summary": "An n8n workflow pulls Trustpilot reviews, saves them to Sheets, alerts Slack on new ones and builds a weekly summary.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "Google Sheets",
    "Slack",
    "scrapio"
   ],
   "prompt": "Goal: Know when a new review lands without checking every day.\nSetup: agents used in source: n8n; tools/MCPs stated: Google Sheets, Slack, scrapio.\nSteps:\n1. Pull reviews on a schedule.\n2. Save them to Google Sheets.\n3. Send a Slack alert for each new review.\n4. Put together a weekly summary.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Cultural-Box-3564 — https://www.reddit.com/r/n8n/comments/1wtwjca/built_a_small_n8n_workflow_for_keeping_up_with/",
   "steps": [
    "Pull reviews on a schedule.",
    "Save them to Google Sheets.",
    "Send a Slack alert for each new review.",
    "Put together a weekly summary."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 4.0,
   "sources": [
    {
     "author": "/u/Cultural-Box-3564",
     "handle": "/u/Cultural-Box-3564",
     "url": "https://www.reddit.com/r/n8n/comments/1wtwjca/built_a_small_n8n_workflow_for_keeping_up_with/",
     "platform": "reddit",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "rogs-ticket-to-pr-skills",
   "url": "https://agentsetups.dev/use-case/rogs-ticket-to-pr-skills/",
   "title": "Ticket in, PR out: four skills and a reviewer in CI",
   "summary": "Six weeks in: 128 PRs, 124 merged; planning a ticket takes about 12 minutes (self-reported).",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "OpenCode"
   ],
   "models": [
    "Claude Opus 5.5 (Fable now and then)",
    "GPT-6 Astra (planning)",
    "GPT-6.1 Sol (executing)",
    "GLM 5.3 / GLM 5.3 Flash"
   ],
   "tools": [],
   "prompt": "Goal: Take a ticket to a reviewed PR with a handful of skills and a dispatcher agent\nSetup: agents used in source: Claude, OpenCode.\nSteps:\n1. Write tickets with an agent, after it audits the code: Problem statement, acceptance criteria, dependencies; it shows you every ticket before creating it.\n2. Ask a read-only dispatcher what to work on next: It ranks tickets by how many others they unblock and lists your waiting PRs first; tiny shell allowlist, no subagents.\n3. Create one worktree per ticket yourself: Branch and directory named after the ticket (worktrunk); .env copied in by a hook.\n4. Run a read-only investigation that ends in a plan: Every acceptance criterion maps to a step; you approve the plan.\n5. Build test-first, then prove it in the browser: Failing test first; Playwright CLI walks each acceptance criterion with screenshots; PR includes human verification steps.\n6. Review every push with a context-fed CI reviewer: Claude Code in GitHub Actions, read-only, fed the PR history and the tickets as the spec.\n7. Address review comments, max two rounds: Treat comments as claims to verify; the fixer never resolves threads.\n8. Run the human verification steps and merge yourself: A human sits at three gates: plan, verification, merge.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: rogs — https://rogs.me/ai/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Write tickets with an agent, after it audits the code: Problem statement, acceptance criteria, dependencies; it shows you every ticket before creating it.",
    "Ask a read-only dispatcher what to work on next: It ranks tickets by how many others they unblock and lists your waiting PRs first; tiny shell allowlist, no subagents.",
    "Create one worktree per ticket yourself: Branch and directory named after the ticket (worktrunk); .env copied in by a hook.",
    "Run a read-only investigation that ends in a plan: Every acceptance criterion maps to a step; you approve the plan.",
    "Build test-first, then prove it in the browser: Failing test first; Playwright CLI walks each acceptance criterion with screenshots; PR includes human verification steps.",
    "Review every push with a context-fed CI reviewer: Claude Code in GitHub Actions, read-only, fed the PR history and the tickets as the spec.",
    "Address review comments, max two rounds: Treat comments as claims to verify; the fixer never resolves threads.",
    "Run the human verification steps and merge yourself: A human sits at three gates: plan, verification, merge."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": "Claude Max $100/month plus ChatGPT Pro 100 ($100/month)",
   "date": "2026-09-30",
   "trend_score": 3.8,
   "sources": [
    {
     "author": "rogs",
     "handle": "rogs",
     "url": "https://rogs.me/ai/",
     "platform": "blog",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  },
  {
   "slug": "flaviocopes-22-mcps",
   "url": "https://agentsetups.dev/use-case/flaviocopes-22-mcps/",
   "title": "Audit 22 connected MCP servers and keep the two you use",
   "summary": "Of 22 connected servers, two are used almost every day (author's inventory, 16 Sep 2026).",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Cursor"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Audit the MCP servers your editor loads and keep only the ones that earn it\nSetup: agents used in source: Cursor.\nBefore you start: Cursor (the same servers work in Codex).\nSteps:\n1. List every server and where it comes from: Global ~/.cursor/mcp.json, per-project .cursor/mcp.json, and Marketplace plugins.\n2. Keep docs servers for fast-moving frameworks, and route to them in rules: A project rule and AGENTS.md tell agents to use the docs server instead of guessing.\n3. Prefer a CLI the agent already has: wrangler beat three Cloudflare servers and gh beat GitHub's for him.\n4. Use read-only modes for anything touching money: e.g. PADDLE_MCP_TOOLS=read-only so the refund tool does not exist in the session.\n5. Keep secrets out of the file: Use ${env:NAME} for tokens in env and headers.\n6. Remove or toggle off idle servers: 22 servers add up to more than 300 tools; the author concludes half should go.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Flavio Copes — https://flaviocopes.com/mcp-servers-i-use/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "List every server and where it comes from: Global ~/.cursor/mcp.json, per-project .cursor/mcp.json, and Marketplace plugins.",
    "Keep docs servers for fast-moving frameworks, and route to them in rules: A project rule and AGENTS.md tell agents to use the docs server instead of guessing.",
    "Prefer a CLI the agent already has: wrangler beat three Cloudflare servers and gh beat GitHub's for him.",
    "Use read-only modes for anything touching money: e.g. PADDLE_MCP_TOOLS=read-only so the refund tool does not exist in the session.",
    "Keep secrets out of the file: Use ${env:NAME} for tokens in env and headers.",
    "Remove or toggle off idle servers: 22 servers add up to more than 300 tools; the author concludes half should go."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-28",
   "trend_score": 3.6,
   "sources": [
    {
     "author": "Flavio Copes",
     "handle": "Flavio Copes",
     "url": "https://flaviocopes.com/mcp-servers-i-use/",
     "platform": "blog",
     "date": "2026-09-28",
     "primary": true
    }
   ]
  },
  {
   "slug": "vanja-opencode-deepseek-glm",
   "url": "https://agentsetups.dev/use-case/vanja-opencode-deepseek-glm/",
   "title": "Run OpenCode on DeepSeek or GLM models",
   "summary": "OpenCode on DeepSeek V4.1 Flash or GLM-5.3 instead of a native seat",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "OpenCode",
    "Claude",
    "Codex"
   ],
   "models": [
    "DeepSeek V4.1 Flash (deepseek-flash)",
    "DeepSeek V4-Pro-0813",
    "GLM-5.3",
    "GLM-5.3-Flash"
   ],
   "tools": [],
   "prompt": "Goal: Run OpenCode on DeepSeek or GLM instead of a native coding seat\nSetup: agents used in source: OpenCode, Claude, Codex.\nBefore you start: A DeepSeek balance, GLM Coding Plan, or OpenCode Go subscription.\nSteps:\n1. Install OpenCode: curl installer, Homebrew or npm.\n2. Connect a provider with /connect: Keys are stored in ~/.local/share/opencode/auth.json.\n3. Pick a model with /models; start on Flash: Confirm the model ID in /models rather than guessing it.\n4. Use the right base URL for your agent: DeepSeek: api.deepseek.com (OpenAI) or /anthropic; GLM plan only meters the coding URL.\n5. Run /init and commit AGENTS.md: It writes build/test commands, repo shape and conventions.\n6. Use Plan vs Build modes: Tab switches Plan (suggest) and Build (edit); /undo and /redo revert.\n7. Work off-peak and keep the prefix stable: Off-peak is half price on DeepSeek; GLM off-peak costs half the credits.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Vanja Petreski — https://vanja.io/deepseek-glm/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install OpenCode: curl installer, Homebrew or npm.",
    "Connect a provider with /connect: Keys are stored in ~/.local/share/opencode/auth.json.",
    "Pick a model with /models; start on Flash: Confirm the model ID in /models rather than guessing it.",
    "Use the right base URL for your agent: DeepSeek: api.deepseek.com (OpenAI) or /anthropic; GLM plan only meters the coding URL.",
    "Run /init and commit AGENTS.md: It writes build/test commands, repo shape and conventions.",
    "Use Plan vs Build modes: Tab switches Plan (suggest) and Build (edit); /undo and /redo revert.",
    "Work off-peak and keep the prefix stable: Off-peak is half price on DeepSeek; GLM off-peak costs half the credits."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": "From $10–$18/month for subscriptions, or pay-as-you-go tokens (prices as of 16 Sep 2026)",
   "date": "2026-09-16",
   "trend_score": 2.8,
   "sources": [
    {
     "author": "Vanja Petreski",
     "handle": "Vanja Petreski",
     "url": "https://vanja.io/deepseek-glm/",
     "platform": "blog",
     "date": "2026-09-16",
     "primary": true
    }
   ]
  },
  {
   "slug": "nadimtuhin-mac-controls-pc-runs",
   "url": "https://agentsetups.dev/use-case/nadimtuhin-mac-controls-pc-runs/",
   "title": "Let a laptop control coding agents that run on a home PC",
   "summary": "Long jobs keep running on the PC after the laptop is closed; you verify and merge next morning (self-reported).",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex",
    "Pi",
    "OpenCode",
    "Hermes Agent"
   ],
   "models": [
    "Any model behind 9Router"
   ],
   "tools": [],
   "prompt": "Goal: Let a laptop control coding agents that run on a home PC\nSetup: agents used in source: Claude, Codex, Pi, OpenCode, Hermes Agent.\nBefore you start: A home Windows PC with WSL2 Ubuntu.\nSteps:\n1. Run Docker inside WSL2 Ubuntu, with limits: Not Docker Desktop; every container gets memory and CPU limits; add a Windows-side keepalive.\n2. Connect devices with Tailscale; browser tools via Cloudflare Tunnel + Access: No open router ports.\n3. Run the Herdr server on the PC, client on the laptop: Each task gets its own pane, usually in its own git worktree; panes survive closing the lid.\n4. Put a gateway (9Router) in front of every model: All agent CLIs talk to one localhost endpoint; combos handle fallback, round robin and fusion.\n5. Launch agents against the gateway with 9agent: Sets Claude Code env vars to gateway models; --sandbox runs in Docker with only the working dir mounted.\n6. Schedule Hermes jobs for upkeep: Nightly CLI updates, security PR scans every six hours, a 30-minute autoheal. Hermes drafts, you send.\n7. Turn corrections into skills: Each fix goes into a skill file with a growing pitfalls section.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Nadim Tuhin — https://www.nadimtuhin.com/blog/ai-coding-agent-setup (summarised from source; the source has no explicit step list)",
   "steps": [
    "Run Docker inside WSL2 Ubuntu, with limits: Not Docker Desktop; every container gets memory and CPU limits; add a Windows-side keepalive.",
    "Connect devices with Tailscale; browser tools via Cloudflare Tunnel + Access: No open router ports.",
    "Run the Herdr server on the PC, client on the laptop: Each task gets its own pane, usually in its own git worktree; panes survive closing the lid.",
    "Put a gateway (9Router) in front of every model: All agent CLIs talk to one localhost endpoint; combos handle fallback, round robin and fusion.",
    "Launch agents against the gateway with 9agent: Sets Claude Code env vars to gateway models; --sandbox runs in Docker with only the working dir mounted.",
    "Schedule Hermes jobs for upkeep: Nightly CLI updates, security PR scans every six hours, a 30-minute autoheal. Hermes drafts, you send.",
    "Turn corrections into skills: Each fix goes into a skill file with a growing pitfalls section."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-01",
   "trend_score": 1.9,
   "sources": [
    {
     "author": "Nadim Tuhin",
     "handle": "Nadim Tuhin",
     "url": "https://www.nadimtuhin.com/blog/ai-coding-agent-setup",
     "platform": "blog",
     "date": "2026-09-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "assistants-watch-social-networks",
   "url": "https://agentsetups.dev/use-case/assistants-watch-social-networks/",
   "title": "Have personal agents monitor X and Facebook for you",
   "summary": "One user has Grok Bot check X daily for certain kinds of posts, and Meta Muse do the same on Facebook.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot",
    "Meta Muse"
   ],
   "models": [],
   "tools": [
    "X",
    "Facebook"
   ],
   "prompt": "Goal: Find specific posts in my networks without scrolling.\nSetup: agents used in source: Grok Bot, Meta Muse; tools/MCPs stated: X, Facebook.\nSteps:\n1. Have Grok Bot check X every day for the kinds of posts you want.\n2. Have Muse check Facebook the same way.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Michael G — https://x.com/insominx/status/2101406908905365988",
   "steps": [
    "Have Grok Bot check X every day for the kinds of posts you want.",
    "Have Muse check Facebook the same way."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-19",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Michael G",
     "handle": "@insominx",
     "url": "https://x.com/insominx/status/2101406908905365988",
     "platform": "x",
     "date": "2026-09-19",
     "primary": true
    }
   ]
  },
  {
   "slug": "cowork-obsidian-mcp-knowledge-base",
   "url": "https://agentsetups.dev/use-case/cowork-obsidian-mcp-knowledge-base/",
   "title": "Build an Obsidian knowledge base in Claude Cowork",
   "summary": "A custom MCP server + skills for Obsidian in Claude Cowork became the most valuable system; teammates report efficiency gains.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Obsidian",
    "MCP"
   ],
   "prompt": "Goal: Give Cowork a knowledge base that improves daily.\nSetup: agents used in source: Claude; tools/MCPs stated: Obsidian, MCP.\nSteps:\n1. Build a custom MCP server for your Obsidian vault.\n2. Add skills for how Cowork should read and write notes.\n3. Onboard teammates to the same knowledge base.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: FiL Dev — https://x.com/FiLHashDev/status/2099973196120207374 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Build a custom MCP server for your Obsidian vault.",
    "Add skills for how Cowork should read and write notes.",
    "Onboard teammates to the same knowledge base."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-15",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "FiL Dev",
     "handle": "@FiLHashDev",
     "url": "https://x.com/FiLHashDev/status/2099973196120207374",
     "platform": "x",
     "date": "2026-09-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-kids-math-worksheets",
   "url": "https://agentsetups.dev/use-case/grokbot-kids-math-worksheets/",
   "title": "Print fresh math worksheets for your kids daily",
   "summary": "Before school, a Grok Bot generates and prints fresh math worksheets for the kids at 6am every day.",
   "category": "education",
   "category_label": "Education",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "printer"
   ],
   "prompt": "Goal: Give my kids daily practice without preparing it myself.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: printer.\nSteps:\n1. Tell Grok Bot each child’s grade level.\n2. Have it generate fresh math worksheets daily.\n3. Schedule printing at 6am so they’re ready before school.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Elon Tesla stock — https://x.com/ElonTeslasw4vu/status/2099825578069155981 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Tell Grok Bot each child’s grade level.",
    "Have it generate fresh math worksheets daily.",
    "Schedule printing at 6am so they’re ready before school."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-09-15",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Elon Tesla stock",
     "handle": "@ElonTeslasw4vu",
     "url": "https://x.com/ElonTeslasw4vu/status/2099825578069155981",
     "platform": "x",
     "date": "2026-09-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-obsidian-ai-os",
   "url": "https://agentsetups.dev/use-case/hermes-obsidian-ai-os/",
   "title": "Run an AI OS on Hermes with an Obsidian graph",
   "summary": "Hermes runs 24/7 across 8 domains via Telegram; a desktop AI builds; every rule and SOP is saved as a note in Obsidian.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "Obsidian",
    "Telegram"
   ],
   "prompt": "Goal: Unify my daily workflows in one agent system.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: Obsidian, Telegram.\nSteps:\n1. Desktop AI handles heavy coding and builds the systems.\n2. Hermes runs 24/7 on a server; chat, monitor and build tools from Telegram.\n3. Use Obsidian as the shared knowledge graph: every rule, asset and SOP is a human-readable note.\n4. When agents solve an issue or learn a rule, they commit it to the graph.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: MGDigital — https://x.com/mgdigitalmktg/status/2099238963978625399",
   "steps": [
    "Desktop AI handles heavy coding and builds the systems.",
    "Hermes runs 24/7 on a server; chat, monitor and build tools from Telegram.",
    "Use Obsidian as the shared knowledge graph: every rule, asset and SOP is a human-readable note.",
    "When agents solve an issue or learn a rule, they commit it to the graph."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-13",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "MGDigital",
     "handle": "@mgdigitalmktg",
     "url": "https://x.com/mgdigitalmktg/status/2099238963978625399",
     "platform": "x",
     "date": "2026-09-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "pplx-computer-morning-inbox-slack",
   "url": "https://agentsetups.dev/use-case/pplx-computer-morning-inbox-slack/",
   "title": "Have Perplexity Computer triage inbox and Slack at 8:45",
   "summary": "Set Perplexity Computer to check inbox + Slack each morning at 8:45 and summarise only what actually needs you.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Perplexity Computer"
   ],
   "models": [],
   "tools": [
    "Slack"
   ],
   "prompt": "Goal: Skip the manual morning triage at work.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: Slack.\nSteps:\n1. Schedule Perplexity Computer for 8:45 every morning.\n2. Have it check your inbox and Slack.\n3. Ask for a summary of only what needs you; ignore the rest.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: suzzie — https://x.com/suzzvsworld/status/2105350886793056444",
   "steps": [
    "Schedule Perplexity Computer for 8:45 every morning.",
    "Have it check your inbox and Slack.",
    "Ask for a summary of only what needs you; ignore the rest."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-09-30",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "suzzie",
     "handle": "@suzzvsworld",
     "url": "https://x.com/suzzvsworld/status/2105350886793056444",
     "platform": "x",
     "date": "2026-09-30",
     "primary": true
    }
   ]
  }
 ]
}