{ "version": "v7", "generated": "2026-10-15", "count": 336, "agents": [ { "name": "Claude", "slug": "claude", "count": 168, "url": "https://agentsetups.dev/agent/claude/" }, { "name": "Codex", "slug": "codex", "count": 69, "url": "https://agentsetups.dev/agent/codex/" }, { "name": "Grok Bot", "slug": "grok-bot", "count": 53, "url": "https://agentsetups.dev/agent/grok-bot/" }, { "name": "Hermes Agent", "slug": "hermes-agent", "count": 25, "url": "https://agentsetups.dev/agent/hermes-agent/" }, { "name": "Meta Muse", "slug": "meta-muse", "count": 19, "url": "https://agentsetups.dev/agent/meta-muse/" }, { "name": "ChatGPT Dots", "slug": "chatgpt-dots", "count": 16, "url": "https://agentsetups.dev/agent/chatgpt-dots/" }, { "name": "n8n", "slug": "n8n", "count": 14, "url": "https://agentsetups.dev/agent/n8n/" }, { "name": "OpenCode", "slug": "opencode", "count": 9, "url": "https://agentsetups.dev/agent/opencode/" }, { "name": "Amp", "slug": "amp", "count": 8, "url": "https://agentsetups.dev/agent/amp/" }, { "name": "Cursor", "slug": "cursor", "count": 8, "url": "https://agentsetups.dev/agent/cursor/" }, { "name": "Perplexity Computer", "slug": "perplexity-computer", "count": 7, "url": "https://agentsetups.dev/agent/perplexity-computer/" }, { "name": "Instinct", "slug": "instinct", "count": 6, "url": "https://agentsetups.dev/agent/instinct/" }, { "name": "Pi", "slug": "pi", "count": 5, "url": "https://agentsetups.dev/agent/pi/" }, { "name": "Antigravity", "slug": "antigravity", "count": 4, "url": "https://agentsetups.dev/agent/antigravity/" }, { "name": "Gemini CLI", "slug": "gemini-cli", "count": 4, "url": "https://agentsetups.dev/agent/gemini-cli/" }, { "name": "OpenClaw", "slug": "openclaw", "count": 4, "url": "https://agentsetups.dev/agent/openclaw/" }, { "name": "Kiro", "slug": "kiro", "count": 3, "url": "https://agentsetups.dev/agent/kiro/" }, { "name": "Manus", "slug": "manus", "count": 3, "url": "https://agentsetups.dev/agent/manus/" }, { "name": "ChatGPT agent", "slug": "chatgpt-agent", "count": 2, "url": "https://agentsetups.dev/agent/chatgpt-agent/" }, { "name": "Command Code", "slug": "command-code", "count": 2, "url": "https://agentsetups.dev/agent/command-code/" }, { "name": "OMP (oh-my-pi)", "slug": "omp-oh-my-pi", "count": 2, "url": "https://agentsetups.dev/agent/omp-oh-my-pi/" }, { "name": "ChatGPT Atlas", "slug": "chatgpt-atlas", "count": 1, "url": "https://agentsetups.dev/agent/chatgpt-atlas/" }, { "name": "Cline", "slug": "cline", "count": 1, "url": "https://agentsetups.dev/agent/cline/" }, { "name": "Comet", "slug": "comet", "count": 1, "url": "https://agentsetups.dev/agent/comet/" }, { "name": "Devin", "slug": "devin", "count": 1, "url": "https://agentsetups.dev/agent/devin/" }, { "name": "Droid", "slug": "droid", "count": 1, "url": "https://agentsetups.dev/agent/droid/" }, { "name": "GitHub Copilot", "slug": "github-copilot", "count": 1, "url": "https://agentsetups.dev/agent/github-copilot/" }, { "name": "Goose", "slug": "goose", "count": 1, "url": "https://agentsetups.dev/agent/goose/" }, { "name": "Muse Code", "slug": "muse-code", "count": 1, "url": "https://agentsetups.dev/agent/muse-code/" } ], "licence_note": "Use-case text is our summary; each item credits and links its sources. Votes are live at /api/votes.", "categories": [ { "slug": "agent-setup", "label": "Agent setup & config", "count": 42, "url": "https://agentsetups.dev/category/agent-setup/" }, { "slug": "coding", "label": "Coding", "count": 39, "url": "https://agentsetups.dev/category/coding/" }, { "slug": "personal-assistant", "label": "Personal assistants", "count": 35, "url": "https://agentsetups.dev/category/personal-assistant/" }, { "slug": "games", "label": "Games", "count": 29, "url": "https://agentsetups.dev/category/games/" }, { "slug": "productivity-ops", "label": "Productivity & ops", "count": 21, "url": "https://agentsetups.dev/category/productivity-ops/" }, { "slug": "content-video", "label": "Content & video", "count": 18, "url": "https://agentsetups.dev/category/content-video/" }, { "slug": "finance-trading", "label": "Finance & trading", "count": 17, "url": "https://agentsetups.dev/category/finance-trading/" }, { "slug": "research-science", "label": "Research & science", "count": 15, "url": "https://agentsetups.dev/category/research-science/" }, { "slug": "design-frontend", "label": "Design & frontend", "count": 15, "url": "https://agentsetups.dev/category/design-frontend/" }, { "slug": "marketing-growth", "label": "Marketing & growth", "count": 15, "url": "https://agentsetups.dev/category/marketing-growth/" }, { "slug": "knowledge-memory", "label": "Knowledge & memory", "count": 14, "url": "https://agentsetups.dev/category/knowledge-memory/" }, { "slug": "personal-life", "label": "Personal life", "count": 13, "url": "https://agentsetups.dev/category/personal-life/" }, { "slug": "hardware-iot", "label": "Hardware & IoT", "count": 11, "url": "https://agentsetups.dev/category/hardware-iot/" }, { "slug": "devops", "label": "DevOps", "count": 11, "url": "https://agentsetups.dev/category/devops/" }, { "slug": "automation-integrations", "label": "Automation & integrations", "count": 10, "url": "https://agentsetups.dev/category/automation-integrations/" }, { "slug": "sales-outreach", "label": "Sales & outreach", "count": 9, "url": "https://agentsetups.dev/category/sales-outreach/" }, { "slug": "security", "label": "Security", "count": 5, "url": "https://agentsetups.dev/category/security/" }, { "slug": "education", "label": "Education", "count": 5, "url": "https://agentsetups.dev/category/education/" }, { "slug": "data-analysis", "label": "Data analysis", "count": 5, "url": "https://agentsetups.dev/category/data-analysis/" }, { "slug": "travel", "label": "Travel", "count": 4, "url": "https://agentsetups.dev/category/travel/" }, { "slug": "health", "label": "Health", "count": 3, "url": "https://agentsetups.dev/category/health/" } ], "usecases": [ { "slug": "find-exoplanet-candidate-tess", "url": "https://agentsetups.dev/use-case/find-exoplanet-candidate-tess/", "title": "Find an exoplanet candidate in NASA TESS data", "summary": "Claude Code ran 74 analyses and 1,000+ scripts; hidden-year transit predictions matched 3/3; Codex reviewed.", "category": "research-science", "category_label": "Research & science", "agents": [ "Claude", "Codex" ], "models": [ "Opus 5.5", "Fable 5.1" ], "tools": [ "TESS data" ], "prompt": "Goal: Search public telescope data for a planet candidate and try hard to disprove it.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: TESS data.\nSteps:\n1. Use the agent to download and parse the TESS data, write the search code and fit transits.\n2. Check nearby stars, look for secondary eclipses and other false positives, plot, and rerun failed tests.\n3. You choose the questions, which tests matter and what counts as pass/fail.\n4. Get independent reviews from a different agent (Codex) and fresh read-only sessions.\n5. Ask it for ways to prove it ISN’T a planet: hide a year, predict its transits from the other years, check only those times.\n6. Search catalogues and literature to see if it is already known; call it a candidate, not a confirmed planet.\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/This_Cell_1829 — https://www.reddit.com/r/ClaudeAI/comments/1wzw8zd/i_think_i_found_a_planet_nobody_knew_existed_i/", "steps": [ "Use the agent to download and parse the TESS data, write the search code and fit transits.", "Check nearby stars, look for secondary eclipses and other false positives, plot, and rerun failed tests.", "You choose the questions, which tests matter and what counts as pass/fail.", "Get independent reviews from a different agent (Codex) and fresh read-only sessions.", "Ask it for ways to prove it ISN’T a planet: hide a year, predict its transits from the other years, check only those times.", "Search catalogues and literature to see if it is already known; call it a candidate, not a confirmed planet." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 100.0, "sources": [ { "author": "/u/This_Cell_1829", "handle": "/u/This_Cell_1829", "url": "https://www.reddit.com/r/ClaudeAI/comments/1wzw8zd/i_think_i_found_a_planet_nobody_knew_existed_i/", "platform": "reddit", "date": "2026-10-07", "primary": true }, { "author": "pyduan", "handle": "pyduan", "url": "https://news.ycombinator.com/item?id=50002665", "platform": "hn", "date": "2026-10-08", "primary": false }, { "author": "NASA Watch", "handle": "@NASAWatch", "url": "https://x.com/NASAWatch/status/2108953701578596847", "platform": "x", "date": "2026-10-10", "primary": false }, { "author": "SciTech Era", "handle": "@SciTechera", "url": "https://x.com/SciTechera/status/2110296881071014279", "platform": "x", "date": "2026-10-14", "primary": false } ] }, { "slug": "gaussian-splats-blender-mcp", "url": "https://agentsetups.dev/use-case/gaussian-splats-blender-mcp/", "title": "Make Gaussian splats with Blender MCP and Lichtfeld Studio", "summary": "GPT-6.1 Astra drove Blender MCP + Lichtfeld Studio to recreate an object as a crisp splat for the web.", "category": "design-frontend", "category_label": "Design & frontend", "agents": [], "models": [ "GPT-6.1 Astra" ], "tools": [ "Blender MCP", "Lichtfeld Studio", "SuperSplat" ], "prompt": "Goal: Create a simple Gaussian splat of an object for the web.\nSetup: tools/MCPs stated: Blender MCP, Lichtfeld Studio, SuperSplat.\nSteps:\n1. Connect Blender MCP and Lichtfeld Studio to your agent.\n2. Ask it to recreate the object (the author recreated an agent “dot” logo).\n3. View and publish it in the SuperSplat editor (PlayCanvas).\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: abstrakt — https://x.com/abstrakt314/status/2105756028935504032", "steps": [ "Connect Blender MCP and Lichtfeld Studio to your agent.", "Ask it to recreate the object (the author recreated an agent “dot” logo).", "View and publish it in the SuperSplat editor (PlayCanvas)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 96.4, "sources": [ { "author": "abstrakt", "handle": "@abstrakt314", "url": "https://x.com/abstrakt314/status/2105756028935504032", "platform": "x", "date": "2026-10-01", "primary": true } ] }, { "slug": "plan-and-book-a-trip", "url": "https://agentsetups.dev/use-case/plan-and-book-a-trip/", "title": "Have your agent plan and book a whole trip", "summary": "Agents researched and booked a Lisbon trip, booked every Japan restaurant and negotiated a dinner slot in Japanese.", "category": "travel", "category_label": "Travel", "agents": [ "Grok Bot", "Meta Muse", "Codex" ], "models": [], "tools": [], "prompt": "Goal: Plan and book my trip.\nSetup: agents used in source: Grok Bot, Meta Muse, Codex.\nSteps:\n1. Ask for the trip (destination, dates, budget).\n2. Let the agent research options and make the bookings (one author let it use his card).\n3. For restaurants and hotels, let it handle the back-and-forth, including in the local language (Muse negotiated in Japanese).\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: SCOTTY BEAM — https://x.com/ScottyBeamIO/status/2109660484144169136 (summarised from source; the source has no explicit step list)", "steps": [ "Ask for the trip (destination, dates, budget).", "Let the agent research options and make the bookings (one author let it use his card).", "For restaurants and hotels, let it handle the back-and-forth, including in the local language (Muse negotiated in Japanese)." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 92.3, "sources": [ { "author": "SCOTTY BEAM", "handle": "@ScottyBeamIO", "url": "https://x.com/ScottyBeamIO/status/2109660484144169136", "platform": "x", "date": "2026-10-12", "primary": true }, { "author": "Han Fang", "handle": "@Han_Fang_", "url": "https://x.com/Han_Fang_/status/2101874865385169348", "platform": "x", "date": "2026-09-21", "primary": false }, { "author": "Atrophius", "handle": "@Atrophius", "url": "https://x.com/Atrophius/status/2096679579398111601", "platform": "x", "date": "2026-09-06", "primary": false } ] }, { "slug": "agents-discover-materials", "url": "https://agentsetups.dev/use-case/agents-discover-materials/", "title": "Run agent teams on materials-science discovery", "summary": "Opus 5.5 agents ran DFT simulations (PBE+U, HSE06) and found two room-temperature magnetic semiconductor candidates.", "category": "research-science", "category_label": "Research & science", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [ "DFT (PBE+U, HSE06)" ], "prompt": "Goal: Use agents to search for materials with target properties.\nSetup: agents used in source: Claude; tools/MCPs stated: DFT (PBE+U, HSE06).\nSteps:\n1. Define the target property window (e.g. band gap, spin splitting, magnetic ordering temperature).\n2. Have agents propose candidate compounds and run density functional theory: a fast pass (PBE+U) then a more accurate one (HSE06).\n3. Calibrate predictions against a known material and report candidates with caveats.\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: Vals AI — https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors (summarised from source; the source has no explicit step list)", "steps": [ "Define the target property window (e.g. band gap, spin splitting, magnetic ordering temperature).", "Have agents propose candidate compounds and run density functional theory: a fast pass (PBE+U) then a more accurate one (HSE06).", "Calibrate predictions against a known material and report candidates with caveats." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-05", "trend_score": 90.9, "sources": [ { "author": "Vals AI", "handle": "vals.ai", "url": "https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors", "platform": "blog", "date": "2026-10-05", "primary": true }, { "author": "outlier99", "handle": "outlier99", "url": "https://news.ycombinator.com/item?id=49970667", "platform": "hn", "date": "2026-10-05", "primary": false } ] }, { "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": "trading-bot-backtest", "url": "https://agentsetups.dev/use-case/trading-bot-backtest/", "title": "Build and backtest a trading bot with no coding background", "summary": "Non-developers have an agent build, backtest and run a trading strategy; claimed results are unverified.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Claude", "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Have the agent help me design, backtest and build a trading strategy from scratch.\nSetup: agents used in source: Claude, Grok Bot.\nSteps:\n1. Explain the market and the strategy idea in plain language; the author started with zero technical background.\n2. Have the agent backtest the strategy (Fable 5 was used for backtesting and building).\n3. Check the backtest for bugs. A separate dev.to write-up found its own backtest had bugs that inflated results.\n4. Run the bot from an agent you can talk to from your phone (GrokBot in the step-by-step source).\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: Profit figures in sources are the authors’ own unverified claims.\nBased on: Davidd Tech — https://x.com/DaviddDotTech/status/2109556174555386014 (summarised from source; the source has no explicit step list)", "steps": [ "Explain the market and the strategy idea in plain language; the author started with zero technical background.", "Have the agent backtest the strategy (Fable 5 was used for backtesting and building).", "Check the backtest for bugs. A separate dev.to write-up found its own backtest had bugs that inflated results.", "Run the bot from an agent you can talk to from your phone (GrokBot in the step-by-step source)." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 89.8, "sources": [ { "author": "Davidd Tech", "handle": "@DaviddDotTech", "url": "https://x.com/DaviddDotTech/status/2109556174555386014", "platform": "x", "date": "2026-10-12", "primary": true }, { "author": "Just a Side Project", "handle": "@just_a_side_project", "url": "https://dev.to/just_a_side_project/debug-log-3-i-had-claude-code-backtest-a-trading-strategy-for-a-week-and-it-found-three-bugs-in-5g50", "platform": "devto", "date": "2026-09-17", "primary": false } ] }, { "slug": "sonnet-main-opus-advisor-split", "url": "https://agentsetups.dev/use-case/sonnet-main-opus-advisor-split/", "title": "Run Sonnet as main, Haiku explorers and Opus as advisor", "summary": "Start Claude Code with --advisor opus: Sonnet 5 codes, Haiku 5.5 subagents search, Opus is consulted only at 3 checkpoints.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude" ], "models": [ "Sonnet 5", "Haiku 5.5", "Opus 5.5" ], "tools": [], "prompt": "Goal: Cut tokens by putting each model only on the work it is best at.\nSetup: agents used in source: Claude.\nSteps:\n1. Start Claude Code with: claude --model sonnet --advisor opus\n2. Create three read-only Haiku 5.5 subagents: search (maps the repo), grep (finds call sites), docs (pulls the API reference).\n3. Add one rule to CLAUDE.md: consult the advisor before locking a plan, after the same error hits twice, and before calling a task done.\n4. Ask Claude Code to show every config change as a diff first, with no edits until you say 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: delost — https://x.com/thedelost/status/2109369295860035641", "steps": [ "Start Claude Code with: claude --model sonnet --advisor opus", "Create three read-only Haiku 5.5 subagents: search (maps the repo), grep (finds call sites), docs (pulls the API reference).", "Add one rule to CLAUDE.md: consult the advisor before locking a plan, after the same error hits twice, and before calling a task done.", "Ask Claude Code to show every config change as a diff first, with no edits until you say go." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 89.4, "sources": [ { "author": "delost", "handle": "@thedelost", "url": "https://x.com/thedelost/status/2109369295860035641", "platform": "x", "date": "2026-10-11", "primary": true } ] }, { "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": "docs-not-memory", "url": "https://agentsetups.dev/use-case/docs-not-memory/", "title": "Give agents documentation instead of memory plugins", "summary": "Have the agent keep specs, plans and indexes in an internal/ folder, read before work and update after.", "category": "knowledge-memory", "category_label": "Knowledge & memory", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Replace RAG “memory” with documentation the agent maintains.\nSetup: agents used in source: Claude.\nSteps:\n1. Create an internal/ folder; ask the agent to write down specs, plans and indexes there.\n2. Task it to always read the relevant docs and index before working, and update them afterwards.\n3. Documentation is written by the working agent while the work is fresh.\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: liao.gg — https://liao.gg/blog/agents-dont-need-memory", "steps": [ "Create an internal/ folder; ask the agent to write down specs, plans and indexes there.", "Task it to always read the relevant docs and index before working, and update them afterwards.", "Documentation is written by the working agent while the work is fresh." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 86.1, "sources": [ { "author": "liao.gg", "handle": "liao.gg", "url": "https://liao.gg/blog/agents-dont-need-memory", "platform": "blog", "date": "2026-10-03", "primary": true }, { "author": "kmeh", "handle": "kmeh", "url": "https://news.ycombinator.com/item?id=49945933", "platform": "hn", "date": "2026-10-03", "primary": false } ] }, { "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": "decompile-fps-agent-swarm", "url": "https://agentsetups.dev/use-case/decompile-fps-agent-swarm/", "title": "Decompile a full game with a long-running agent swarm", "summary": "Over 3 months and 500B tokens, worker + reviewer agents reached 99% of functions, 83% byte-exact.", "category": "games", "category_label": "Games", "agents": [ "Claude", "Codex" ], "models": [ "Sonnet 5", "Opus 5.5", "Luna" ], "tools": [ "Discord" ], "prompt": "Goal: Run a multi-month decompilation with worker and reviewer agents.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Discord.\nSteps:\n1. Start with 3 worker agents decompiling and committing, plus 1 reviewer that coordinates and flags bugs; communicate via Discord.\n2. Trigger compaction earlier (they cut the threshold from 90% to 42% context fill) to save tokens.\n3. Stop the reviewer trusting workers’ comments: verify deviations against the original independently.\n4. Build a verification harness, then scale workers and let them run autonomously.\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: momo5502 — https://momo5502.com/posts/2026-10-09-game-decompilation/", "steps": [ "Start with 3 worker agents decompiling and committing, plus 1 reviewer that coordinates and flags bugs; communicate via Discord.", "Trigger compaction earlier (they cut the threshold from 90% to 42% context fill) to save tokens.", "Stop the reviewer trusting workers’ comments: verify deviations against the original independently.", "Build a verification harness, then scale workers and let them run autonomously." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 81.6, "sources": [ { "author": "momo5502", "handle": "momo5502", "url": "https://momo5502.com/posts/2026-10-09-game-decompilation/", "platform": "blog", "date": "2026-10-09", "primary": true }, { "author": "davikr", "handle": "davikr", "url": "https://news.ycombinator.com/item?id=50039092", "platform": "hn", "date": "2026-10-11", "primary": false } ] }, { "slug": "backtest-trading-strategy-claude", "url": "https://agentsetups.dev/use-case/backtest-trading-strategy-claude/", "title": "Build a strategy backtesting engine with Claude Code", "summary": "Describe entry, exit, stop and size in plain English; include fees and slippage; get win rate, max drawdown and a dashboard.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Claude" ], "models": [], "tools": [ "TradingView" ], "prompt": "Goal: Test a trading strategy on historical data before risking money.\nSetup: agents used in source: Claude; tools/MCPs stated: TradingView.\nSteps:\n1. Open Claude Code and send the backtesting prompt (attached to the post).\n2. Describe your strategy in plain English: entry, exit, stop, position size.\n3. Tell it to include fees and slippage.\n4. Run it and ask for win rate, max drawdown and average R per trade.\n5. Ask for a dashboard to visualise the results.\n6. Quality-check: import the source into TradingView and compare.\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’s claimed returns are his own; past performance isn’t a forecast.\nBased on: Miles Deutscher — https://x.com/milesdeutscher/status/2108079450927833334", "steps": [ "Open Claude Code and send the backtesting prompt (attached to the post).", "Describe your strategy in plain English: entry, exit, stop, position size.", "Tell it to include fees and slippage.", "Run it and ask for win rate, max drawdown and average R per trade.", "Ask for a dashboard to visualise the results.", "Quality-check: import the source into TradingView and compare." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 81.6, "sources": [ { "author": "Miles Deutscher", "handle": "@milesdeutscher", "url": "https://x.com/milesdeutscher/status/2108079450927833334", "platform": "x", "date": "2026-10-08", "primary": true } ] }, { "slug": "coding-hospital-cockroach", "url": "https://agentsetups.dev/use-case/coding-hospital-cockroach/", "title": "Run coding agents like a hospital: Db2 support in 2 days", "summary": "Cockroach Labs’ label-triggered role agents planned 15 sub-issues and shipped Db2 migration for $4,172.", "category": "coding", "category_label": "Coding", "agents": [ "Claude" ], "models": [], "tools": [ "GitHub Actions" ], "prompt": "Goal: Set up role-based agents with hard rules to ship a large feature safely.\nSetup: agents used in source: Claude; tools/MCPs stated: GitHub Actions.\nSteps:\n1. Start from a single GitHub issue describing the ask.\n2. A planning agent decomposes it into sub-issues with an explicit dependency graph.\n3. Applying a label fires a GitHub workflow that loads a role-specific prompt (the agent acts as a hospital employee).\n4. Encode rules in skills: no code before a plan, no plan without review.\n5. Accept slower runs (even 10x) in exchange for well-tested, in-scope code.\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: Cockroach Labs — https://www.cockroachlabs.com/blog/experiment-running-hospital-code/", "steps": [ "Start from a single GitHub issue describing the ask.", "A planning agent decomposes it into sub-issues with an explicit dependency graph.", "Applying a label fires a GitHub workflow that loads a role-specific prompt (the agent acts as a hospital employee).", "Encode rules in skills: no code before a plan, no plan without review.", "Accept slower runs (even 10x) in exchange for well-tested, in-scope code." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 80.4, "sources": [ { "author": "Cockroach Labs", "handle": "cockroachlabs.com", "url": "https://www.cockroachlabs.com/blog/experiment-running-hospital-code/", "platform": "blog", "date": "2026-10-08", "primary": true }, { "author": "rafiss", "handle": "rafiss", "url": "https://news.ycombinator.com/item?id=50021899", "platform": "hn", "date": "2026-10-09", "primary": false } ] }, { "slug": "game-as-agent-harness", "url": "https://agentsetups.dev/use-case/game-as-agent-harness/", "title": "Make your game legible to AI agents", "summary": "Kyle Kukshtel’s talk: engineer the game itself as a harness so agentic iteration on gameplay is faster.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Make my game easier for coding agents to inspect, test and iterate on.\nSetup: agents used in source: Claude.\nSteps:\n1. Treat the game as a harness: expose state and actions the agent can read and drive.\n2. Shorten the loop between a change and a verifiable result.\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: Kyle Kukshtel — https://kylekukshtel.com/ai-harness-engineering-game-development-claude-code (summarised from source; the source has no explicit step list)", "steps": [ "Treat the game as a harness: expose state and actions the agent can read and drive.", "Shorten the loop between a change and a verifiable result." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-10", "trend_score": 80.4, "sources": [ { "author": "Kyle Kukshtel", "handle": "kylekukshtel.com", "url": "https://kylekukshtel.com/ai-harness-engineering-game-development-claude-code", "platform": "blog", "date": "2026-10-10", "primary": true }, { "author": "kkukshtel", "handle": "kkukshtel", "url": "https://news.ycombinator.com/item?id=50072120", "platform": "hn", "date": "2026-10-13", "primary": false } ] }, { "slug": "dots-as-project-manager", "url": "https://agentsetups.dev/use-case/dots-as-project-manager/", "title": "Run your ChatGPT Dot as a project manager", "summary": "@AlexFinn says Dots get far more useful as a project manager than as an assistant, using the desktop app’s tools.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [ "ChatGPT desktop app" ], "prompt": "Goal: Set my ChatGPT Dot up to manage a project, not just answer requests.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: ChatGPT desktop app.\nSteps:\n1. Work from the ChatGPT desktop app, which gives the Dot the most tools.\n2. Give the Dot the project to own and manage, rather than treating it as a general assistant.\n3. Use the skill the author links in the post as the starting brief.\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 cut off after the setup idea; open it for the linked skill.\nBased on: Alex Finn — https://x.com/AlexFinn/status/2105702256075276523 (summarised from source; the source has no explicit step list)", "steps": [ "Work from the ChatGPT desktop app, which gives the Dot the most tools.", "Give the Dot the project to own and manage, rather than treating it as a general assistant.", "Use the skill the author links in the post as the starting brief." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 79.5, "sources": [ { "author": "Alex Finn", "handle": "@AlexFinn", "url": "https://x.com/AlexFinn/status/2105702256075276523", "platform": "x", "date": "2026-10-01", "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": "paid-web-app-playbook", "url": "https://agentsetups.dev/use-case/paid-web-app-playbook/", "title": "Build paid web apps with an Opus front end and Codex", "summary": "The founder’s playbook behind $100K MRR: one-shot a baseline, name the stack, use a quality reference per feature, self-score.", "category": "coding", "category_label": "Coding", "agents": [ "Claude", "Codex" ], "models": [ "Opus 5.5" ], "tools": [ "Supabase", "Stripe" ], "prompt": "Goal: Build a paid web app with AI agents.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Supabase, Stripe.\nSteps:\n1. Find ideas in tools you use every day: what is missing in Codex, Cursor or Figma?\n2. Use Opus 5.5 for the front end and Codex for the harness.\n3. One-shot a baseline, then break the work into parts.\n4. Name your stack and future needs up front (React + Vite, Supabase, Stripe).\n5. Give one quality reference per feature (Figma, Spline, Linear).\n6. Add an AI layer through APIs so the tool generates, not just displays.\n7. Have the AI score its work out of 10 and screenshot its own mistakes.\n8. Record a demo, post it everywhere, paste the feedback into your agent, and ship.\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: Meng To — https://x.com/MengTo/status/2107862479548403806", "steps": [ "Find ideas in tools you use every day: what is missing in Codex, Cursor or Figma?", "Use Opus 5.5 for the front end and Codex for the harness.", "One-shot a baseline, then break the work into parts.", "Name your stack and future needs up front (React + Vite, Supabase, Stripe).", "Give one quality reference per feature (Figma, Spline, Linear).", "Add an AI layer through APIs so the tool generates, not just displays.", "Have the AI score its work out of 10 and screenshot its own mistakes.", "Record a demo, post it everywhere, paste the feedback into your agent, and ship." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 79.2, "sources": [ { "author": "Meng To", "handle": "@MengTo", "url": "https://x.com/MengTo/status/2107862479548403806", "platform": "x", "date": "2026-10-07", "primary": true } ] }, { "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": "j2me-shooter-one-prompt", "url": "https://agentsetups.dev/use-case/j2me-shooter-one-prompt/", "title": "Make a 3D shooter for 20-year-old phones in one prompt", "summary": "Opus 5.5 wrote an integer-math Java engine, its own sprite renderer, 4 maps, 8 MIDI tracks and TTS voice lines.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [ "ffmpeg", "J2ME" ], "prompt": "Goal: Build a retro 3D shooter for old J2ME phones.\nSetup: agents used in source: Claude; tools/MCPs stated: ffmpeg, J2ME.\nSteps:\n1. Ask for a Duke Nukem 3D-style shooter for old J2ME phones.\n2. Expect an integer-math 3D engine in Java so old phones can run it.\n3. Let it write its own 3D renderer in Python to model and render sprites; generate textures and skies in code.\n4. Have it design maps, compose MIDI tracks, and make voice lines with TTS edited via ffmpeg.\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/wollymonjac — https://www.reddit.com/r/ClaudeAI/comments/1x120gj/opus_55_can_make_games_for_2_decade_old_phones/", "steps": [ "Ask for a Duke Nukem 3D-style shooter for old J2ME phones.", "Expect an integer-math 3D engine in Java so old phones can run it.", "Let it write its own 3D renderer in Python to model and render sprites; generate textures and skies in code.", "Have it design maps, compose MIDI tracks, and make voice lines with TTS edited via ffmpeg." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 78.1, "sources": [ { "author": "/u/wollymonjac", "handle": "/u/wollymonjac", "url": "https://www.reddit.com/r/ClaudeAI/comments/1x120gj/opus_55_can_make_games_for_2_decade_old_phones/", "platform": "reddit", "date": "2026-10-08", "primary": true }, { "author": "/u/HugoDzz", "handle": "/u/HugoDzz", "url": "https://www.reddit.com/r/ClaudeAI/comments/1wv2r73/made_a_destroy_any_website_stickman_game/", "platform": "reddit", "date": "2026-10-01", "primary": false } ] }, { "slug": "one-shot-invisible-cities-viz", "url": "https://agentsetups.dev/use-case/one-shot-invisible-cities-viz/", "title": "Give one prompt and 6 hours for a 3D visualisation", "summary": "Same prompt to GPT-6 Astra in Codex and Opus 5.5 in Claude Code; Opus ran 6 subagents and finished a three.js piece in 1h25.", "category": "design-frontend", "category_label": "Design & frontend", "agents": [ "Claude", "Codex" ], "models": [ "Opus 5.5", "GPT-6 Astra" ], "tools": [ "three.js", "pnpm" ], "prompt": "Goal: Compare how models handle a long one-shot design task.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: three.js, pnpm.\nSteps:\n1. Prompt: “Make a three.js (pnpm) visualization of all Invisible Cities by Italo Calvino. Don’t ask questions, it is a one-shot task. You have 6h of work, use it until it becomes a masterpiece.”\n2. Run it in Codex (GPT-6 Astra) and in Claude Code (Opus 5.5).\n3. Compare: Opus used 6 parallel subagents (~7 agent-hours) and stopped after 1h25.\n4. Try the same prompt on other models and harnesses.\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: Piotr Migdał — https://quesma.com/blog/invisible-cities-one-shot/", "steps": [ "Prompt: “Make a three.js (pnpm) visualization of all Invisible Cities by Italo Calvino. Don’t ask questions, it is a one-shot task. You have 6h of work, use it until it becomes a masterpiece.”", "Run it in Codex (GPT-6 Astra) and in Claude Code (Opus 5.5).", "Compare: Opus used 6 parallel subagents (~7 agent-hours) and stopped after 1h25.", "Try the same prompt on other models and harnesses." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 77.9, "sources": [ { "author": "Piotr Migdał", "handle": "quesma.com", "url": "https://quesma.com/blog/invisible-cities-one-shot/", "platform": "blog", "date": "2026-10-07", "primary": true }, { "author": "stared", "handle": "stared", "url": "https://news.ycombinator.com/item?id=50004790", "platform": "hn", "date": "2026-10-08", "primary": false } ] }, { "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": "perplexity-computer-port-windows-app", "url": "https://agentsetups.dev/use-case/perplexity-computer-port-windows-app/", "title": "Port a Windows-only app to Linux with Perplexity Computer", "summary": "Computer decompiled a keyboard app with headless Ghidra and rebuilt it in Rust for Linux, with music-synced lighting and macros.", "category": "coding", "category_label": "Coding", "agents": [ "Perplexity Computer" ], "models": [], "tools": [ "Ghidra", "Rust", "PipeWire" ], "prompt": "Goal: Get a Linux version of a Windows-only app with no docs.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: Ghidra, Rust, PipeWire.\nSteps:\n1. Have Computer download the binary into its cloud sandbox and decompile it with headless Ghidra.\n2. Have it read the decompiled code to learn how the app drives the hardware.\n3. Rebuild it piece by piece as a native Rust app (here: lighting synced to music via PipeWire, 3D view, key remapping, macros, profiles).\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: Vendor CEO post describing a user’s project.\nBased on: Aravind Srinivas — https://x.com/AravSrinivas/status/2110389625277813212", "steps": [ "Have Computer download the binary into its cloud sandbox and decompile it with headless Ghidra.", "Have it read the decompiled code to learn how the app drives the hardware.", "Rebuild it piece by piece as a native Rust app (here: lighting synced to music via PipeWire, 3D view, key remapping, macros, profiles)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-14", "trend_score": 77.2, "sources": [ { "author": "Aravind Srinivas", "handle": "@AravSrinivas", "url": "https://x.com/AravSrinivas/status/2110389625277813212", "platform": "x", "date": "2026-10-14", "primary": true } ] }, { "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": "grokbot-run-solo-business-stack", "url": "https://agentsetups.dev/use-case/grokbot-run-solo-business-stack/", "title": "Run a one-person business on Grok Bot plugins", "summary": "@Av1dlive’s $165/mo stack: Whop, Vercel+GitHub, draft-only inbox and writer bots, Notion CRM, chief-of-staff report.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Grok Bot", "Cursor" ], "models": [ "Opus 5.5" ], "tools": [ "Whop", "Vercel", "GitHub", "Gmail", "Notion", "Cursor cloud agents", "Klaviyo" ], "prompt": "Goal: Run my online business with a team of Grok Bot bots and plugins.\nSetup: agents used in source: Grok Bot, Cursor; tools/MCPs stated: Whop, Vercel, GitHub, Gmail, Notion, Cursor cloud agents, Klaviyo.\nSteps:\n1. Required: money via the Whop plugin; site via Vercel + GitHub plugins; inbox via Gmail + an inbox bot that drafts, never sends.\n2. CRM in Notion inboxes built with Grok Bot; content via the X plugin + draft-only writer bots; numbers in Notion.\n3. Oversight: a chief-of-staff morning report, plus a bot that audits every other bot.\n4. Add later as needed: support inbox bot, Klaviyo + Grok Bot routines for email, lead bots, builder + reviewer bots, scheduling routines with a content calendar.\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: Avid — https://x.com/Av1dlive/status/2110329712715182092", "steps": [ "Required: money via the Whop plugin; site via Vercel + GitHub plugins; inbox via Gmail + an inbox bot that drafts, never sends.", "CRM in Notion inboxes built with Grok Bot; content via the X plugin + draft-only writer bots; numbers in Notion.", "Oversight: a chief-of-staff morning report, plus a bot that audits every other bot.", "Add later as needed: support inbox bot, Klaviyo + Grok Bot routines for email, lead bots, builder + reviewer bots, scheduling routines with a content calendar." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-14", "trend_score": 74.9, "sources": [ { "author": "Avid", "handle": "@Av1dlive", "url": "https://x.com/Av1dlive/status/2110329712715182092", "platform": "x", "date": "2026-10-14", "primary": true } ] }, { "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": "social-publication-engine", "url": "https://agentsetups.dev/use-case/social-publication-engine/", "title": "Run a social publication engine from your agent", "summary": "A publication skill prepares the reel, cover and caption; you give feedback; it publishes via the Buffer API, then verifies and archives.", "category": "content-video", "category_label": "Content & video", "agents": [ "Claude", "Codex" ], "models": [], "tools": [ "Buffer API", "upload-post API", "Claude Code routines" ], "prompt": "Goal: Prepare, review and publish social posts from my agent.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Buffer API, upload-post API, Claude Code routines.\nSteps:\n1. Input: project context plus an automated screencast.\n2. Use a publication skill that holds your visual and copy rules.\n3. Prepare a vertical reel (headline, music, intro footage), plus a cover and caption.\n4. Review it: give text feedback, get a revision, then approve.\n5. Publish via the Buffer API to Instagram. Then check the live post and save the MP4, caption, render settings and post URL.\n6. Variant: a daily Claude Code routine turns the latest blog post into LinkedIn, X and Reddit posts and publishes them via the upload-post API.\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: AmirMušić — https://x.com/AmirMushich/status/2106716622761189875", "steps": [ "Input: project context plus an automated screencast.", "Use a publication skill that holds your visual and copy rules.", "Prepare a vertical reel (headline, music, intro footage), plus a cover and caption.", "Review it: give text feedback, get a revision, then approve.", "Publish via the Buffer API to Instagram. Then check the live post and save the MP4, caption, render settings and post URL.", "Variant: a daily Claude Code routine turns the latest blog post into LinkedIn, X and Reddit posts and publishes them via the upload-post API." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 73.9, "sources": [ { "author": "AmirMušić", "handle": "@AmirMushich", "url": "https://x.com/AmirMushich/status/2106716622761189875", "platform": "x", "date": "2026-10-04", "primary": true }, { "author": "Ayush 🙏", "handle": "@ayushtweetshere", "url": "https://x.com/ayushtweetshere/status/2096832340110856297", "platform": "x", "date": "2026-09-07", "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": "codex-rebuild-personal-website-s3", "url": "https://agentsetups.dev/use-case/codex-rebuild-personal-website-s3/", "title": "Rebuild your personal site with Codex and a deploy tool", "summary": "After ~5 failed rebuilds, Codex built the site plus a small tool to add writing and deploy the static site to S3.", "category": "design-frontend", "category_label": "Design & frontend", "agents": [ "Codex" ], "models": [], "tools": [], "prompt": "Goal: Replace my old simple website setup without losing its simplicity.\nSetup: agents used in source: Codex.\nSteps:\n1. Have Codex build the static site.\n2. Ask it for a small tool to add new writing.\n3. Have the same tool deploy the static site to S3.\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: Karri Saarinen — https://x.com/karrisaarinen/status/2107356889990504672 (summarised from source; the source has no explicit step list)", "steps": [ "Have Codex build the static site.", "Ask it for a small tool to add new writing.", "Have the same tool deploy the static site to S3." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-06", "trend_score": 72.6, "sources": [ { "author": "Karri Saarinen", "handle": "@karrisaarinen", "url": "https://x.com/karrisaarinen/status/2107356889990504672", "platform": "x", "date": "2026-10-06", "primary": true } ] }, { "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": "voice-assistant-on-claude-p", "url": "https://agentsetups.dev/use-case/voice-assistant-on-claude-p/", "title": "Build a hold-to-talk Mac assistant on claude -p", "summary": "Atticus moves windows, finds files and shops in Chrome using your Claude plan; repeated asks become no-AI shortcuts.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Claude" ], "models": [], "tools": [ "claude -p" ], "prompt": "Goal: Control my Mac by voice using the Claude plan I already have.\nSetup: agents used in source: Claude; tools/MCPs stated: claude -p.\nSteps:\n1. Install Atticus; it runs through Claude Code (claude -p), no API key.\n2. Hold the hotkey, say what you need, let go.\n3. Repeated actions become learned shortcuts that skip the AI (e.g. 5.5s → 0.4s).\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: SaarthRanka — https://news.ycombinator.com/item?id=50049588", "steps": [ "Install Atticus; it runs through Claude Code (claude -p), no API key.", "Hold the hotkey, say what you need, let go.", "Repeated actions become learned shortcuts that skip the AI (e.g. 5.5s → 0.4s)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 71.4, "sources": [ { "author": "SaarthRanka", "handle": "SaarthRanka", "url": "https://news.ycombinator.com/item?id=50049588", "platform": "hn", "date": "2026-10-12", "primary": true } ] }, { "slug": "manus-travel-footage-vlog", "url": "https://agentsetups.dev/use-case/manus-travel-footage-vlog/", "title": "Turn 2 hours of travel clips into a vlog with Manus", "summary": "From 125 clips, one prompt gave a 12:48 first cut following the trip; the finished vlog added captions, music and effects.", "category": "content-video", "category_label": "Content & video", "agents": [ "Manus" ], "models": [], "tools": [ "Manus Video" ], "prompt": "Goal: Edit a pile of travel footage into a story-driven vlog.\nSetup: agents used in source: Manus; tools/MCPs stated: Manus Video.\nSteps:\n1. Upload all clips.\n2. One prompt: find the highlights and make a first cut that follows the trip.\n3. Add captions, music and effects for the final version.\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: Vendor post about a user’s project.\nBased on: Manus — https://x.com/ManusAI/status/2107105397781963086 (summarised from source; the source has no explicit step list)", "steps": [ "Upload all clips.", "One prompt: find the highlights and make a first cut that follows the trip.", "Add captions, music and effects for the final version." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-05", "trend_score": 70.5, "sources": [ { "author": "Manus", "handle": "@ManusAI", "url": "https://x.com/ManusAI/status/2107105397781963086", "platform": "x", "date": "2026-10-05", "primary": true } ] }, { "slug": "grokbot-curate-x-follow-list", "url": "https://agentsetups.dev/use-case/grokbot-curate-x-follow-list/", "title": "Ask Grok Bot to build your X follow list", "summary": "@FundamentEdge asked Grok Bot for 50 accounts to follow to keep up with AI, each with a one-line reason.", "category": "research-science", "category_label": "Research & science", "agents": [ "Grok Bot" ], "models": [], "tools": [ "X" ], "prompt": "Goal: Build a high-signal timeline on a topic.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: X.\nSteps:\n1. Ask your Grok Bot to recommend 50 people to follow on a topic, grouped by theme with a one-line reason each.\n2. Crowdsource what it missed in replies.\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: Brett Caughran — https://x.com/FundamentEdge/status/2109412745045242352", "steps": [ "Ask your Grok Bot to recommend 50 people to follow on a topic, grouped by theme with a one-line reason each.", "Crowdsource what it missed in replies." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 70.4, "sources": [ { "author": "Brett Caughran", "handle": "@FundamentEdge", "url": "https://x.com/FundamentEdge/status/2109412745045242352", "platform": "x", "date": "2026-10-11", "primary": true } ] }, { "slug": "grokbot-personal-cfo-monthly", "url": "https://agentsetups.dev/use-case/grokbot-personal-cfo-monthly/", "title": "Set up a read-only personal CFO agent", "summary": "Shane Mac’s Grok Bot CFO sent monthly money reports, until it posted them to a work Slack channel with the same name.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Grok Bot" ], "models": [], "tools": [ "Slack" ], "prompt": "Goal: Get a monthly personal-finance review from an agent, safely.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Slack.\nSteps:\n1. Ask the agent: balances, monthly expenses, recurring expenses, anything suspicious, ways to save; “what would you say to me every month as my financial advisor?”.\n2. Give it read-only access to checking and savings, and tell it to message only you.\n3. Run it weekly at first to test.\n4. Lesson: agents can share connections, so a work Slack channel with the same name as your private chat got the report. Use distinct channel names and require explicit permission before cross-channel posts.\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: Shane Mac (as told to Business Insider) — https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10", "steps": [ "Ask the agent: balances, monthly expenses, recurring expenses, anything suspicious, ways to save; “what would you say to me every month as my financial advisor?”.", "Give it read-only access to checking and savings, and tell it to message only you.", "Run it weekly at first to test.", "Lesson: agents can share connections, so a work Slack channel with the same name as your private chat got the report. Use distinct channel names and require explicit permission before cross-channel posts." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-10", "trend_score": 70.0, "sources": [ { "author": "Shane Mac (as told to Business Insider)", "handle": "Business Insider", "url": "https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10", "platform": "blog", "date": "2026-10-10", "primary": true }, { "author": "bhrlady", "handle": "bhrlady", "url": "https://news.ycombinator.com/item?id=50033517", "platform": "hn", "date": "2026-10-10", "primary": false } ] }, { "slug": "grokbot-book-dentist-insurance", "url": "https://agentsetups.dev/use-case/grokbot-book-dentist-insurance/", "title": "Have Grok Bot book a dentist that takes your insurance", "summary": "A Grok Bot found a dentist that accepts the family’s insurance and booked the appointment from its own browser.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Grok Bot" ], "models": [], "tools": [ "web browser" ], "prompt": "Goal: Book a medical appointment without phoning around about insurance.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: web browser.\nSteps:\n1. Ask your Grok Bot to search for dentists near you that accept your insurance.\n2. Let it book the appointment from its web browser.\n3. Check the confirmation email and text.\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: Texas Twins Dad — https://x.com/Texas_Twins_Dad/status/2110562649586983246", "steps": [ "Ask your Grok Bot to search for dentists near you that accept your insurance.", "Let it book the appointment from its web browser.", "Check the confirmation email and text." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 69.9, "sources": [ { "author": "Texas Twins Dad", "handle": "@Texas_Twins_Dad", "url": "https://x.com/Texas_Twins_Dad/status/2110562649586983246", "platform": "x", "date": "2026-10-15", "primary": true } ] }, { "slug": "mine-agent-session-logs", "url": "https://agentsetups.dev/use-case/mine-agent-session-logs/", "title": "Mine hundreds of agent sessions for consequential moments", "summary": "A Hermes plugin developer had the agent review 491 sessions for “consequential moments”.", "category": "knowledge-memory", "category_label": "Knowledge & memory", "agents": [ "Hermes Agent" ], "models": [], "tools": [], "prompt": "Goal: Review my saved agent sessions for useful patterns.\nSetup: agents used in source: Hermes Agent.\nSteps:\n1. Point your agent at your sessions data.\n2. Ask it to review the sessions for “consequential moments”.\n3. Use the patterns to guide the plugins and tools you build.\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: mr_r0b0t — https://x.com/mr_r0b0t/status/2109089421203050864 (summarised from source; the source has no explicit step list)", "steps": [ "Point your agent at your sessions data.", "Ask it to review the sessions for “consequential moments”.", "Use the patterns to guide the plugins and tools you build." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 69.6, "sources": [ { "author": "mr_r0b0t", "handle": "@mr_r0b0t", "url": "https://x.com/mr_r0b0t/status/2109089421203050864", "platform": "x", "date": "2026-10-11", "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": "codex-drives-real-iphone", "url": "https://agentsetups.dev/use-case/codex-drives-real-iphone/", "title": "Let Codex operate a real iPhone over USB", "summary": "iPhone-use: guided install, app automation, live screen and screenshot fallback for Codex.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Codex" ], "models": [], "tools": [], "prompt": "Goal: Let my agent operate apps on my iPhone.\nSetup: agents used in source: Codex.\nSteps:\n1. Install iPhone-use and connect the iPhone by USB.\n2. Let Codex automate the app via the live screen.\n3. Fall back to screenshots when needed.\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: zhongerxin — https://github.com/zhongerxin/iPhone-use (summarised from source; the source has no explicit step list)", "steps": [ "Install iPhone-use and connect the iPhone by USB.", "Let Codex automate the app via the live screen.", "Fall back to screenshots when needed." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-06", "trend_score": 69.1, "sources": [ { "author": "zhongerxin", "handle": "zhongerxin", "url": "https://github.com/zhongerxin/iPhone-use", "platform": "github", "date": "2026-10-06", "primary": true } ] }, { "slug": "archive-search-dodo-discovery", "url": "https://agentsetups.dev/use-case/archive-search-dodo-discovery/", "title": "Find unknown sources in a historical archive", "summary": "A historian embedded the VOC archive, used semantic search plus Opus 5.5 ranking, and found a 1615 dodo hunting report.", "category": "research-science", "category_label": "Research & science", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [ "GLOBALISE archive", "embedding model" ], "prompt": "Goal: Use agents to surface overlooked primary sources for a research question.\nSetup: agents used in source: Claude; tools/MCPs stated: GLOBALISE archive, embedding model.\nSteps:\n1. Start from your own specialist knowledge to define a specific research question.\n2. Pick a large, free, well-edited corpus (here the GLOBALISE Dutch East India Company archive).\n3. Download it and run it through an embedding model for semantic search.\n4. Surface candidate passages; have frontier models read them and rank the best matches for human review.\n5. Iterate on promising passages, or try new archives and terms. Give the agent an API key so it can run its own embedding searches on new sources.\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/using-opus-55-to-discover-a-new-eyewitness", "steps": [ "Start from your own specialist knowledge to define a specific research question.", "Pick a large, free, well-edited corpus (here the GLOBALISE Dutch East India Company archive).", "Download it and run it through an embedding model for semantic search.", "Surface candidate passages; have frontier models read them and rank the best matches for human review.", "Iterate on promising passages, or try new archives and terms. Give the agent an API key so it can run its own embedding searches on new sources." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 69.0, "sources": [ { "author": "Benjamin Breen", "handle": "Res Obscura", "url": "https://resobscura.substack.com/p/using-opus-55-to-discover-a-new-eyewitness", "platform": "blog", "date": "2026-10-01", "primary": true }, { "author": "benbreen", "handle": "benbreen", "url": "https://news.ycombinator.com/item?id=49926917", "platform": "hn", "date": "2026-10-01", "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": "bookkeeping-for-accountant", "url": "https://agentsetups.dev/use-case/bookkeeping-for-accountant/", "title": "Prepare your books for the accountant with computer use", "summary": "Codex matched every transaction to an invoice across subscriptions and API top-ups, then built a summary site.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Claude", "Codex" ], "models": [ "GPT-6.1 Sol" ], "tools": [ "Google Drive", "QuickBooks Online" ], "prompt": "Goal: Match every transaction to its receipt and prepare everything for my accountant.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Google Drive, QuickBooks Online.\nSteps:\n1. Collect the receipts for subscriptions and API credit top-ups.\n2. Give the agent bank and payment-processor access. The source used API keys and browser sessions; think hard before sharing credentials.\n3. Match every transaction to its invoice.\n4. Produce a summary for the accountant, with the files in Google Drive.\n5. Variant: connect QuickBooks Online through an app created in the QuickBooks developer portal (~20 min).\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/2106022667694612530", "steps": [ "Collect the receipts for subscriptions and API credit top-ups.", "Give the agent bank and payment-processor access. The source used API keys and browser sessions; think hard before sharing credentials.", "Match every transaction to its invoice.", "Produce a summary for the accountant, with the files in Google Drive.", "Variant: connect QuickBooks Online through an app created in the QuickBooks developer portal (~20 min)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 68.6, "sources": [ { "author": "Machina", "handle": "@EXM7777", "url": "https://x.com/EXM7777/status/2106022667694612530", "platform": "x", "date": "2026-10-02", "primary": true }, { "author": "Fil", "handle": "@BallinFil", "url": "https://x.com/BallinFil/status/2106789537653694771", "platform": "x", "date": "2026-10-04", "primary": false } ] }, { "slug": "clone-app-replica-skills", "url": "https://agentsetups.dev/use-case/clone-app-replica-skills/", "title": "Clone an app and fix what its users hate", "summary": "Eleven free Claude skills: reverse-engineer an app, rebuild it, test for bugs, then fix user complaints.", "category": "coding", "category_label": "Coding", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Rebuild an app and improve on its weak points.\nSetup: agents used in source: Claude.\nSteps:\n1. Reverse-engineer the target app.\n2. Rebuild it.\n3. Test it for bugs.\n4. Fix what its users complain about.\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: Jakeschincariol — https://github.com/Jakeschincariol/replica-skill (summarised from source; the source has no explicit step list)", "steps": [ "Reverse-engineer the target app.", "Rebuild it.", "Test it for bugs.", "Fix what its users complain about." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 67.8, "sources": [ { "author": "Jakeschincariol", "handle": "Jakeschincariol", "url": "https://github.com/Jakeschincariol/replica-skill", "platform": "github", "date": "2026-10-03", "primary": true } ] }, { "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": "n8n-long-tail-keywords", "url": "https://agentsetups.dev/use-case/n8n-long-tail-keywords/", "title": "Automate long-tail keyword research", "summary": "n8n + Airtable + YepAPI expand a seed keyword into related searches, autocomplete ideas and SEO metrics.", "category": "marketing-growth", "category_label": "Marketing & growth", "agents": [ "n8n" ], "models": [], "tools": [ "n8n", "Airtable", "YepAPI" ], "prompt": "Goal: Turn a seed keyword into a researched list of long-tail keywords.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n, Airtable, YepAPI.\nSteps:\n1. Start from a seed keyword.\n2. Explore related searches and autocomplete suggestions.\n3. Collect SEO metrics and store results in Airtable.\n4. Related: generate an ICP first (Gemini + Perplexity) so keywords match who you’re writing for.\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/1x2yb1l/i_got_tired_of_researching_keywords_manually_so_i/", "steps": [ "Start from a seed keyword.", "Explore related searches and autocomplete suggestions.", "Collect SEO metrics and store results in Airtable.", "Related: generate an ICP first (Gemini + Perplexity) so keywords match who you’re writing for." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 66.6, "sources": [ { "author": "/u/cuebicai", "handle": "/u/cuebicai", "url": "https://www.reddit.com/r/n8n/comments/1x2yb1l/i_got_tired_of_researching_keywords_manually_so_i/", "platform": "reddit", "date": "2026-10-11", "primary": true }, { "author": "/u/cuebicai", "handle": "/u/cuebicai", "url": "https://www.reddit.com/r/n8n/comments/1wwe6ig/what_if_you_could_automatically_research_a/", "platform": "reddit", "date": "2026-10-03", "primary": false } ] }, { "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": "lego-model-generator-agents", "url": "https://agentsetups.dev/use-case/lego-model-generator-agents/", "title": "Have agents design buildable LEGO models", "summary": "Agents write Python that generates LDraw, not raw geometry; outputs include 3D/VR views and Blender-editable glTF.", "category": "design-frontend", "category_label": "Design & frontend", "agents": [ "Claude" ], "models": [ "Opus 5.5", "GPT-6 Astra" ], "tools": [ "LDraw", "Docker", "Blender" ], "prompt": "Goal: Get an agent to design physical builds that are actually buildable.\nSetup: agents used in source: Claude; tools/MCPs stated: LDraw, Docker, Blender.\nSteps:\n1. Don’t ask agents to do geometry maths directly; give them Python tooling that generates LDraw sources.\n2. Let them learn from Python code that produces models, not from the models themselves.\n3. Run the open-source app in Docker (clone ldraw-nova and ldraw-nova-docker at the same tag, docker compose build, up -d).\n4. Guide the agent; export 3D/VR views and a Blender glTF.\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: antelocnova — https://news.ycombinator.com/item?id=49937916", "steps": [ "Don’t ask agents to do geometry maths directly; give them Python tooling that generates LDraw sources.", "Let them learn from Python code that produces models, not from the models themselves.", "Run the open-source app in Docker (clone ldraw-nova and ldraw-nova-docker at the same tag, docker compose build, up -d).", "Guide the agent; export 3D/VR views and a Blender glTF." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 65.8, "sources": [ { "author": "antelocnova", "handle": "antelocnova", "url": "https://news.ycombinator.com/item?id=49937916", "platform": "hn", "date": "2026-10-02", "primary": true } ] }, { "slug": "switch-accessible-hub", "url": "https://agentsetups.dev/use-case/switch-accessible-hub/", "title": "Build a switch-accessible hub for a nonspeaking brother", "summary": "A non-programmer built keyboards, phrase boards, texting, streaming pickers and games for his brother.", "category": "personal-life", "category_label": "Personal life", "agents": [ "Claude" ], "models": [], "tools": [ "VS Code" ], "prompt": "Goal: Build accessible tools and games for someone who uses switch access.\nSetup: agents used in source: Claude; tools/MCPs stated: VS Code.\nSteps:\n1. Use Claude as a thought partner to plan games and write GDDs and spec sheets before building.\n2. Build in VS Code with the Claude Code extension: describe what the person needs; let it write the code.\n3. Start with a keyboard and phrase boards, then texting, web search, show/movie picking and games.\n4. Test with the person and iterate.\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/acrolicious — https://www.reddit.com/r/ClaudeAI/comments/1x0x5wo/my_brother_went_nearly_10_years_without_a_way_to/", "steps": [ "Use Claude as a thought partner to plan games and write GDDs and spec sheets before building.", "Build in VS Code with the Claude Code extension: describe what the person needs; let it write the code.", "Start with a keyboard and phrase boards, then texting, web search, show/movie picking and games.", "Test with the person and iterate." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 65.4, "sources": [ { "author": "/u/acrolicious", "handle": "/u/acrolicious", "url": "https://www.reddit.com/r/ClaudeAI/comments/1x0x5wo/my_brother_went_nearly_10_years_without_a_way_to/", "platform": "reddit", "date": "2026-10-08", "primary": true } ] }, { "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": "do-comments-help-agents", "url": "https://agentsetups.dev/use-case/do-comments-help-agents/", "title": "Test whether code comments help your agent", "summary": "Deleting 168k lines of comments: same scores, ~22% fewer tokens on a small task, three runs per branch.", "category": "coding", "category_label": "Coding", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Measure whether comments in my codebase help or hurt my agent.\nSetup: agents used in source: Claude.\nSteps:\n1. Make a copy of the codebase with every comment removed.\n2. Ask the agent to build the same features on both versions, three times each.\n3. Score with lint, type checks, existing tests and a hidden test; compare tokens and cost.\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: openstation.blog — https://openstation.blog/2026/10/13/i-deleted-168000-lines-of-comments-my-ai-agent-didnt-notice/", "steps": [ "Make a copy of the codebase with every comment removed.", "Ask the agent to build the same features on both versions, three times each.", "Score with lint, type checks, existing tests and a hidden test; compare tokens and cost." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 63.3, "sources": [ { "author": "openstation.blog", "handle": "openstation.blog", "url": "https://openstation.blog/2026/10/13/i-deleted-168000-lines-of-comments-my-ai-agent-didnt-notice/", "platform": "blog", "date": "2026-10-13", "primary": true }, { "author": "epeicher", "handle": "epeicher", "url": "https://news.ycombinator.com/item?id=50090484", "platform": "hn", "date": "2026-10-14", "primary": false } ] }, { "slug": "llm-council-design-review", "url": "https://agentsetups.dev/use-case/llm-council-design-review/", "title": "Rank models with a blind LLM design-review council", "summary": "A Sonnet 5 “president” has Codex and Claude Code members review, blind-rate each other and aggregate votes.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude", "Codex" ], "models": [ "GPT-6.1 Sol", "GPT-6 Astra", "Opus", "Fable 5.1", "Sonnet 5" ], "tools": [ "orca" ], "prompt": "Goal: Find out which model actually does my design reviews best.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: orca.\nSteps:\n1. Build a council with an orchestrator (here orca’s built-in one).\n2. Use a Sonnet 5 “president” agent to trigger members (Codex and Claude Code models) on the same review task.\n3. Have members rate each other’s work blind.\n4. Aggregate the votes; repeat across several runs before concluding.\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: jinjingliang — https://x.com/JinjingLiang/status/2107537480945942954", "steps": [ "Build a council with an orchestrator (here orca’s built-in one).", "Use a Sonnet 5 “president” agent to trigger members (Codex and Claude Code models) on the same review task.", "Have members rate each other’s work blind.", "Aggregate the votes; repeat across several runs before concluding." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-06", "trend_score": 63.2, "sources": [ { "author": "jinjingliang", "handle": "@JinjingLiang", "url": "https://x.com/JinjingLiang/status/2107537480945942954", "platform": "x", "date": "2026-10-06", "primary": true } ] }, { "slug": "one-prompt-playable-game", "url": "https://agentsetups.dev/use-case/one-prompt-playable-game/", "title": "Build and publish a playable game from one prompt", "summary": "Manus 2.0 built a 3D world, combat, soundtrack and SFX, then playtested and published “Echo Isle”.", "category": "games", "category_label": "Games", "agents": [ "Manus" ], "models": [], "tools": [], "prompt": "Goal: Build a playable game from one idea.\nSetup: agents used in source: Manus.\nSteps:\n1. Give one idea (e.g. “an open-world game where music is your weapon”).\n2. Have it build the world, characters, combat, soundtrack and SFX.\n3. Have it playtest and publish.\n4. Variant: Claude Code recreated a film scene in three.js, generating textures/SFX/music and self-verifying with screenshots.\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: Min Choi — https://x.com/minchoi/status/2109669169234944325", "steps": [ "Give one idea (e.g. “an open-world game where music is your weapon”).", "Have it build the world, characters, combat, soundtrack and SFX.", "Have it playtest and publish.", "Variant: Claude Code recreated a film scene in three.js, generating textures/SFX/music and self-verifying with screenshots." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 62.7, "sources": [ { "author": "Min Choi", "handle": "@minchoi", "url": "https://x.com/minchoi/status/2109669169234944325", "platform": "x", "date": "2026-10-12", "primary": true } ] }, { "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": "one-prompt-motion-video", "url": "https://agentsetups.dev/use-case/one-prompt-motion-video/", "title": "Make a 30-second motion-graphics video from one prompt", "summary": "One Claude Code prompt rendered a 1080p60 three.js video in 26 min for $6.74; others render particles in headless Chromium.", "category": "content-video", "category_label": "Content & video", "agents": [ "Claude" ], "models": [ "Sonnet 5.5", "Opus 5.5" ], "tools": [ "three.js", "headless Chromium" ], "prompt": "Goal: Make a motion-graphics video in code.\nSetup: agents used in source: Claude; tools/MCPs stated: three.js, headless Chromium.\nSteps:\n1. Prompt: “make a dynamic 30-second motion graphics video about . not too fast, people should actually understand what it’s about. use three.js”.\n2. Let it render frames (another author rendered 900 frames in headless Chromium on CPU).\n3. Or point Claude Code at a launch video you like and have it build your own version.\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: Artem — https://x.com/sl1ma4/status/2105592053874700360", "steps": [ "Prompt: “make a dynamic 30-second motion graphics video about . not too fast, people should actually understand what it’s about. use three.js”.", "Let it render frames (another author rendered 900 frames in headless Chromium on CPU).", "Or point Claude Code at a launch video you like and have it build your own version." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 62.1, "sources": [ { "author": "Artem", "handle": "@sl1ma4", "url": "https://x.com/sl1ma4/status/2105592053874700360", "platform": "x", "date": "2026-10-01", "primary": true }, { "author": "qibaz", "handle": "@QibazX", "url": "https://x.com/QibazX/status/2106116277936787516", "platform": "x", "date": "2026-10-02", "primary": false }, { "author": "LN", "handle": "@ln_dev7", "url": "https://x.com/ln_dev7/status/2105357508684415159", "platform": "x", "date": "2026-09-30", "primary": false } ] }, { "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": "xp-agent-skills-pack", "url": "https://agentsetups.dev/use-case/xp-agent-skills-pack/", "title": "Adopt 22 daily-driver engineering skills", "summary": "Open-source skills for TDD, review, debugging, refactoring, security, Docker, worktrees and subagent orchestration.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude", "Codex" ], "models": [], "tools": [], "prompt": "Goal: Set up skills that keep changes simple, small and verified.\nSetup: agents used in source: Claude, Codex.\nSteps:\n1. Install the skills for TDD, code review, debugging, refactoring, legacy code, testing, security, Docker, worktrees and repo cleanup.\n2. Use the orchestration skills: split parallel work, pick the right agent, give it a clear mission, verify, integrate.\n3. Keep only the skills that survive daily use.\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: Rafael Bittencourt — https://x.com/rafaelobitten/status/2107098718033871285", "steps": [ "Install the skills for TDD, code review, debugging, refactoring, legacy code, testing, security, Docker, worktrees and repo cleanup.", "Use the orchestration skills: split parallel work, pick the right agent, give it a clear mission, verify, integrate.", "Keep only the skills that survive daily use." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-05", "trend_score": 61.0, "sources": [ { "author": "Rafael Bittencourt", "handle": "@rafaelobitten", "url": "https://x.com/rafaelobitten/status/2107098718033871285", "platform": "x", "date": "2026-10-05", "primary": true } ] }, { "slug": "simcity-clone-ghidra-subagents", "url": "https://agentsetups.dev/use-case/simcity-clone-ghidra-subagents/", "title": "Clone a classic game by decompiling it with subagents", "summary": "Opus 5.5 decompiled SimCity 2000 with Ghidra using 27 subagents, then verified 10,000 game days via a Unicorn emulator.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [ "Ghidra", "Unicorn", "GPT Image 2" ], "prompt": "Goal: Build a faithful modern replica of an old game from its original binary.\nSetup: agents used in source: Claude; tools/MCPs stated: Ghidra, Unicorn, GPT Image 2.\nSteps:\n1. Prompt: “create a typescript webgl low-poly version (full replica of game logic) of . the original is available here for inspection”.\n2. Let it decompile with Ghidra and translate native code function by function using subagents.\n3. Follow up: “make sure all aspects of the game is implemented correctly and accurately” — it built an emulator harness to compare game state over 10,000 days.\n4. Polish; generate 3D/vector assets in code and bitmaps with an image model.\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: drdator — https://news.ycombinator.com/item?id=49977886", "steps": [ "Prompt: “create a typescript webgl low-poly version (full replica of game logic) of . the original is available here for inspection”.", "Let it decompile with Ghidra and translate native code function by function using subagents.", "Follow up: “make sure all aspects of the game is implemented correctly and accurately” — it built an emulator harness to compare game state over 10,000 days.", "Polish; generate 3D/vector assets in code and bitmaps with an image model." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-06", "trend_score": 61.0, "sources": [ { "author": "drdator", "handle": "drdator", "url": "https://news.ycombinator.com/item?id=49977886", "platform": "hn", "date": "2026-10-06", "primary": true } ] }, { "slug": "compare-models-on-real-task", "url": "https://agentsetups.dev/use-case/compare-models-on-real-task/", "title": "Benchmark model/reasoning combos on your real task", "summary": "16 combinations across ChatGPT Plus, Claude Pro and Google AI Pro on one Unity investigation: 1–20% allowance.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude" ], "models": [], "tools": [ "Unity" ], "prompt": "Goal: Find which model and reasoning mode gives the most useful work per subscription.\nSetup: agents used in source: Claude; tools/MCPs stated: Unity.\nSteps:\n1. Pick one real task from your project as the benchmark.\n2. Run it on each model/reasoning combination.\n3. Record allowance used and quality of result.\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/AlexXx52 — https://www.reddit.com/r/ChatGPTCoding/comments/1x1jbry/i_tested_16_ai_modelreasoning_combinations_on_the/", "steps": [ "Pick one real task from your project as the benchmark.", "Run it on each model/reasoning combination.", "Record allowance used and quality of result." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 60.9, "sources": [ { "author": "/u/AlexXx52", "handle": "/u/AlexXx52", "url": "https://www.reddit.com/r/ChatGPTCoding/comments/1x1jbry/i_tested_16_ai_modelreasoning_combinations_on_the/", "platform": "reddit", "date": "2026-10-09", "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": "personal-whisper-app", "url": "https://agentsetups.dev/use-case/personal-whisper-app/", "title": "Build your own transcription app for your workflow", "summary": "A YouTuber replaced terminal faster-whisper with a Claude Code-built app; transcripts feed video descriptions.", "category": "content-video", "category_label": "Content & video", "agents": [ "Claude" ], "models": [], "tools": [ "faster-whisper" ], "prompt": "Goal: Build a desktop transcription app for my videos.\nSetup: agents used in source: Claude; tools/MCPs stated: faster-whisper.\nSteps:\n1. Describe the workflow you use today (e.g. running faster-whisper in a terminal).\n2. Have Claude Code build an app around it and test it in the background.\n3. Feed transcripts into AI to generate video descriptions.\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/AcrillixOfficial — https://www.reddit.com/r/ClaudeAI/comments/1wx7nnw/claude_has_enabled_me_to_make_apps_for_personal/ (summarised from source; the source has no explicit step list)", "steps": [ "Describe the workflow you use today (e.g. running faster-whisper in a terminal).", "Have Claude Code build an app around it and test it in the background.", "Feed transcripts into AI to generate video descriptions." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 59.6, "sources": [ { "author": "/u/AcrillixOfficial", "handle": "/u/AcrillixOfficial", "url": "https://www.reddit.com/r/ClaudeAI/comments/1wx7nnw/claude_has_enabled_me_to_make_apps_for_personal/", "platform": "reddit", "date": "2026-10-04", "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": "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-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": "dots-relay-slack-for-you", "url": "https://agentsetups.dev/use-case/dots-relay-slack-for-you/", "title": "Let your Dot post updates to Slack and bring replies back", "summary": "At Every, @danshipper’s Dot posted his model-testing results to Slack and relayed the replies, so he never opened Slack.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [ "Slack" ], "prompt": "Goal: Protect my attention: have my Dot handle Slack back-and-forth while I keep working.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Slack.\nSteps:\n1. Connect Slack to your Dot.\n2. Ask it to post your results or update in the right channel.\n3. Have it collect the replies and bring them back to you in ChatGPT, so you don’t open Slack.\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: Dan Shipper — https://x.com/danshipper/status/2107890633486582208 (summarised from source; the source has no explicit step list)", "steps": [ "Connect Slack to your Dot.", "Ask it to post your results or update in the right channel.", "Have it collect the replies and bring them back to you in ChatGPT, so you don’t open Slack." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 56.6, "sources": [ { "author": "Dan Shipper", "handle": "@danshipper", "url": "https://x.com/danshipper/status/2107890633486582208", "platform": "x", "date": "2026-10-07", "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": "cowork-job-search-pipeline", "url": "https://agentsetups.dev/use-case/cowork-job-search-pipeline/", "title": "Run a job search on Cowork scheduled tasks", "summary": "Apps Script scrapes ~9,000 career pages; Cowork matches roles, keeps an interview tracker from Gmail and drafts follow-ups. 3 offers.", "category": "personal-life", "category_label": "Personal life", "agents": [ "Claude" ], "models": [], "tools": [ "Google Sheets", "Apps Script", "Gmail", "Claude in Chrome" ], "prompt": "Goal: Stay early on new roles while keeping applications personal.\nSetup: agents used in source: Claude; tools/MCPs stated: Google Sheets, Apps Script, Gmail, Claude in Chrome.\nSteps:\n1. Scrape career pages with Apps Script inside the sheet, not with the agent.\n2. Have Cowork match new roles, open the best ones in tabs each morning, and keep an interview tracker current from Gmail and calendar.\n3. Have it draft a recruiter follow-up after each application and save it to Gmail for review.\n4. When writing into Sheets via Claude in Chrome: plain text only, map columns by header name.\n5. Keep each automation as a markdown skill file; when it breaks, give Claude the file and the error to fix it.\n6. Do the applications 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/Lovamelin — https://www.reddit.com/r/ClaudeCowork/comments/1x557lz/my_job_search_ran_on_cowork_scheduled_tasks_for/", "steps": [ "Scrape career pages with Apps Script inside the sheet, not with the agent.", "Have Cowork match new roles, open the best ones in tabs each morning, and keep an interview tracker current from Gmail and calendar.", "Have it draft a recruiter follow-up after each application and save it to Gmail for review.", "When writing into Sheets via Claude in Chrome: plain text only, map columns by header name.", "Keep each automation as a markdown skill file; when it breaks, give Claude the file and the error to fix it.", "Do the applications yourself." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 56.5, "sources": [ { "author": "/u/Lovamelin", "handle": "/u/Lovamelin", "url": "https://www.reddit.com/r/ClaudeCowork/comments/1x557lz/my_job_search_ran_on_cowork_scheduled_tasks_for/", "platform": "reddit", "date": "2026-10-13", "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": "pi-extensions-council-voice", "url": "https://agentsetups.dev/use-case/pi-extensions-council-voice/", "title": "Extend Pi with council, voice and TTS extensions", "summary": "Community Pi extensions: /council asks several models in parallel, local voice input, Turkish TTS.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Pi" ], "models": [ "Opus 5.5", "GPT-6 Astra" ], "tools": [ "pi-voice" ], "prompt": "Goal: Add useful extensions to my Pi agent.\nSetup: agents used in source: Pi; tools/MCPs stated: pi-voice.\nSteps:\n1. Install Pi Agent Council and use /council to compare advice from several models side by side.\n2. Install pi-voice (pi install npm:@earendil-works/pi-voice) for local speech-to-text.\n3. Optionally add a TTS extension that reads only text inside tags.\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: Melvin Vivas — https://x.com/melvindvivas/status/2105645508186570807", "steps": [ "Install Pi Agent Council and use /council to compare advice from several models side by side.", "Install pi-voice (pi install npm:@earendil-works/pi-voice) for local speech-to-text.", "Optionally add a TTS extension that reads only text inside tags." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 54.8, "sources": [ { "author": "Melvin Vivas", "handle": "@melvindvivas", "url": "https://x.com/melvindvivas/status/2105645508186570807", "platform": "x", "date": "2026-10-01", "primary": true }, { "author": "Swarogan", "handle": "@swarogan", "url": "https://x.com/swarogan/status/2104530944061309040", "platform": "x", "date": "2026-09-28", "primary": false }, { "author": "Ilker", "handle": "@ilkerulusoy", "url": "https://x.com/ilkerulusoy/status/2107853780481917156", "platform": "x", "date": "2026-10-07", "primary": false } ] }, { "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": "hermes-copy-muse-memory-setup", "url": "https://agentsetups.dev/use-case/hermes-copy-muse-memory-setup/", "title": "Give your Hermes agent Muse-style memory", "summary": "A Hermes user copied Muse’s memory design (daily logs, derived memory stores, nightly “dreaming”) and got much better weekly reflections.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Hermes Agent", "Meta Muse" ], "models": [], "tools": [ "markdown memory files" ], "prompt": "Goal: Get a life-management agent to spot patterns, not just recap my week.\nSetup: agents used in source: Hermes Agent, Meta Muse; tools/MCPs stated: markdown memory files.\nSteps:\n1. Have the agent write a daily memory log as a markdown file.\n2. Keep derived memory stores about the concepts that matter to you.\n3. Add a nightly “dream” job that synthesises the day’s logs into those stores.\n4. Run weekly and monthly reflections on top of that memory and compare them with what you got before.\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/normVectorsNotHate — https://www.reddit.com/r/hermesagent/comments/1wxu98g/i_copied_muses_memory_setup_for_my_own_hermes/", "steps": [ "Have the agent write a daily memory log as a markdown file.", "Keep derived memory stores about the concepts that matter to you.", "Add a nightly “dream” job that synthesises the day’s logs into those stores.", "Run weekly and monthly reflections on top of that memory and compare them with what you got before." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 53.9, "sources": [ { "author": "/u/normVectorsNotHate", "handle": "/u/normVectorsNotHate", "url": "https://www.reddit.com/r/hermesagent/comments/1wxu98g/i_copied_muses_memory_setup_for_my_own_hermes/", "platform": "reddit", "date": "2026-10-04", "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": "muse-inbox-triage-hill-climb", "url": "https://agentsetups.dev/use-case/muse-inbox-triage-hill-climb/", "title": "Let Muse tune its own inbox-triage model", "summary": "@OmarShahine’s Muse triages email via a decision model; it hill-climbed a cheaper model from 52% to 88% on his labels.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Meta Muse" ], "models": [ "Jev", "Decision-1" ], "tools": [ "OpenRouter" ], "prompt": "Goal: Have my Muse triage my inbox daily with a cheap model it tunes itself.\nSetup: agents used in source: Meta Muse; tools/MCPs stated: OpenRouter.\nSteps:\n1. Give Muse a decision model through OpenRouter for daily inbox triage.\n2. Label a set of your emails as ground truth.\n3. Ask Muse to hill-climb a cheaper model against those labels until it beats the current one, then switch.\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 Shahine — https://x.com/OmarShahine/status/2109402421185167491", "steps": [ "Give Muse a decision model through OpenRouter for daily inbox triage.", "Label a set of your emails as ground truth.", "Ask Muse to hill-climb a cheaper model against those labels until it beats the current one, then switch." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 53.6, "sources": [ { "author": "Omar Shahine", "handle": "@OmarShahine", "url": "https://x.com/OmarShahine/status/2109402421185167491", "platform": "x", "date": "2026-10-11", "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-home-inventory-insurance", "url": "https://agentsetups.dev/use-case/grokbot-home-inventory-insurance/", "title": "Inventory your belongings for insurance with Grok Bot", "summary": "Use Grok Bot to build an inventory of your important stuff, with the details insurers ask for: what it was, brand and more.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Have a list of what I own in case of flood, fire or burglary.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Photograph your important belongings.\n2. Have Grok Bot build an inventory from them with the details insurers want (item, brand, …).\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 Roemmele — https://x.com/BrianRoemmele/status/2110580579628650928 (summarised from source; the source has no explicit step list)", "steps": [ "Photograph your important belongings.", "Have Grok Bot build an inventory from them with the details insurers want (item, brand, …)." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 52.6, "sources": [ { "author": "Brian Roemmele", "handle": "@BrianRoemmele", "url": "https://x.com/BrianRoemmele/status/2110580579628650928", "platform": "x", "date": "2026-10-15", "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": "hermes-agent-on-iphone", "url": "https://agentsetups.dev/use-case/hermes-agent-on-iphone/", "title": "Run a Hermes agent on your phone, no server", "summary": "A Hermes agent living on the phone thinks in the Dynamic Island, asks before risky commands and builds 3D apps.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Hermes Agent" ], "models": [], "tools": [], "prompt": "Goal: Carry a personal agent on my phone without a laptop or server.\nSetup: agents used in source: Hermes Agent.\nSteps:\n1. Run Hermes Agent on the phone itself.\n2. Have it ask before running risky commands.\n3. Use it to build live 3D apps and Canvas, and to remember what you tell 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: Mark Keeper — https://x.com/markkeeper2/status/2106873833978540280 (summarised from source; the source has no explicit step list)", "steps": [ "Run Hermes Agent on the phone itself.", "Have it ask before running risky commands.", "Use it to build live 3D apps and Canvas, and to remember what you tell it." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 51.9, "sources": [ { "author": "Mark Keeper", "handle": "@markkeeper2", "url": "https://x.com/markkeeper2/status/2106873833978540280", "platform": "x", "date": "2026-10-04", "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": "dots-build-personal-chatgpt-apps", "url": "https://agentsetups.dev/use-case/dots-build-personal-chatgpt-apps/", "title": "Build personal ChatGPT apps with your Dot", "summary": "@_simonsmith’s Dot built a news app and a Spanish vocab app: Sites MCP server backend, plugin-with-extensions front end.", "category": "coding", "category_label": "Coding", "agents": [ "Claude", "Meta Muse", "ChatGPT Dots" ], "models": [], "tools": [ "ChatGPT Sites", "MCP" ], "prompt": "Goal: Have my Dot build a small personal app that runs inside ChatGPT.\nSetup: agents used in source: Claude, Meta Muse, ChatGPT Dots; tools/MCPs stated: ChatGPT Sites, MCP.\nSteps:\n1. Ask the Dot to build the backend as an MCP server hosted on ChatGPT Sites.\n2. Have it build the front end as a ChatGPT plugin with extensions.\n3. Start with one app (e.g. a personalised news feed with thumbs up/down), then iterate on the rough edges.\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 Smith — https://x.com/_simonsmith/status/2110425007059017830 (summarised from source; the source has no explicit step list)", "steps": [ "Ask the Dot to build the backend as an MCP server hosted on ChatGPT Sites.", "Have it build the front end as a ChatGPT plugin with extensions.", "Start with one app (e.g. a personalised news feed with thumbs up/down), then iterate on the rough edges." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-14", "trend_score": 51.6, "sources": [ { "author": "Simon Smith", "handle": "@_simonsmith", "url": "https://x.com/_simonsmith/status/2110425007059017830", "platform": "x", "date": "2026-10-14", "primary": true }, { "author": "Simon Smith", "handle": "@_simonsmith", "url": "https://x.com/_simonsmith/status/2108672854460072099", "platform": "x", "date": "2026-10-09", "primary": false }, { "author": "Simon Smith", "handle": "@_simonsmith", "url": "https://x.com/_simonsmith/status/2108622812474683426", "platform": "x", "date": "2026-10-09", "primary": false } ] }, { "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": "one-shot-ad-codex-suno", "url": "https://agentsetups.dev/use-case/one-shot-ad-codex-suno/", "title": "One-shot a product ad with Codex and Suno", "summary": "Animations, captions, structure in Codex and the song via Suno, done in under 3 hours on a flight.", "category": "content-video", "category_label": "Content & video", "agents": [ "Codex" ], "models": [], "tools": [ "Suno" ], "prompt": "Goal: Make a short product ad entirely with AI.\nSetup: agents used in source: Codex; tools/MCPs stated: Suno.\nSteps:\n1. Generate the song in Suno.\n2. Have Codex build the animations, captions and structure.\n3. Variant: a “remake this video 100% in code” prompt rebuilds a reference video frame by frame and zips code, motion data and assets.\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 — https://x.com/aaronmtrx/status/2110400280164721106", "steps": [ "Generate the song in Suno.", "Have Codex build the animations, captions and structure.", "Variant: a “remake this video 100% in code” prompt rebuilds a reference video frame by frame and zips code, motion data and assets." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-14", "trend_score": 50.9, "sources": [ { "author": "Aaron", "handle": "@aaronmtrx", "url": "https://x.com/aaronmtrx/status/2110400280164721106", "platform": "x", "date": "2026-10-14", "primary": true }, { "author": "Justin Lord", "handle": "@Justin_lords", "url": "https://x.com/Justin_lords/status/2097729022277173535", "platform": "x", "date": "2026-09-09", "primary": false } ] }, { "slug": "ai-agent-on-feature-phone", "url": "https://agentsetups.dev/use-case/ai-agent-on-feature-phone/", "title": "Put an AI agent on a Nokia feature phone", "summary": "With Codex’s help, a dev reverse-engineered Nokia 110 4G firmware; a chat app runs from RAM and can call, set alarms and toggle the torch.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Codex" ], "models": [], "tools": [ "DeepSeek API" ], "prompt": "Goal: Run an agent with native phone functions on a basic phone.\nSetup: agents used in source: Codex; tools/MCPs stated: DeepSeek API.\nSteps:\n1. Study the firmware and boot process; get custom code running in RAM through an existing app entry point (Calculator) without flashing.\n2. Turn it into a chat app that sends messages to a model API and maps tool calls to phone functions: answer questions, battery, torch, call, alarm.\n3. Trace the firmware’s response callbacks when requests go out but answers don’t come back.\n4. Use a coding agent (here Codex) to help build; test on the handset.\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: anupray — https://news.ycombinator.com/item?id=50006114", "steps": [ "Study the firmware and boot process; get custom code running in RAM through an existing app entry point (Calculator) without flashing.", "Turn it into a chat app that sends messages to a model API and maps tool calls to phone functions: answer questions, battery, torch, call, alarm.", "Trace the firmware’s response callbacks when requests go out but answers don’t come back.", "Use a coding agent (here Codex) to help build; test on the handset." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 50.9, "sources": [ { "author": "anupray", "handle": "anupray", "url": "https://news.ycombinator.com/item?id=50006114", "platform": "hn", "date": "2026-10-08", "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": "muse-text-on-your-behalf", "url": "https://agentsetups.dev/use-case/muse-text-on-your-behalf/", "title": "Let your agent text for you, behind an approval gate", "summary": "Muse texts via iMessage from an always-on Mac/VM; an approval gate guards every device action.", "category": "personal-life", "category_label": "Personal life", "agents": [ "Meta Muse" ], "models": [], "tools": [ "iMessage" ], "prompt": "Goal: Let my agent send iMessages for me, safely.\nSetup: agents used in source: Meta Muse; tools/MCPs stated: iMessage.\nSteps:\n1. Use a computer you can leave on (or iCloud in a VM) and connect it to Muse.\n2. Give the access needed; tell the agent which number belongs to whom.\n3. Set an approval gate for any action on the connected device.\n4. Write ground rules: never spend, send, delete or share details without asking; research only for trades.\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: JJ Englert — https://x.com/JJEnglert/status/2109803033362108493", "steps": [ "Use a computer you can leave on (or iCloud in a VM) and connect it to Muse.", "Give the access needed; tell the agent which number belongs to whom.", "Set an approval gate for any action on the connected device.", "Write ground rules: never spend, send, delete or share details without asking; research only for trades." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 49.7, "sources": [ { "author": "JJ Englert", "handle": "@JJEnglert", "url": "https://x.com/JJEnglert/status/2109803033362108493", "platform": "x", "date": "2026-10-13", "primary": true }, { "author": "MJ", "handle": "@Mj4Stocks", "url": "https://x.com/Mj4Stocks/status/2104420369868222758", "platform": "x", "date": "2026-09-28", "primary": false } ] }, { "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": "agent-auditor-stops-waste", "url": "https://agentsetups.dev/use-case/agent-auditor-stops-waste/", "title": "Make one agent audit the others for wasted spend", "summary": "After agents burned $200 of credits chatting, an auditor agent lists every agent and what it costs.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Act as my agent auditor and find agents that waste money.\nSetup: agents used in source: Claude.\nSteps:\n1. Give one agent the auditor job. In Claude Code the author pastes a prompt that starts “You’re my agent auditor. List every…”.\n2. List every running agent, what it does and what it costs.\n3. Flag agents that talk to each other without producing anything; the author lost $200 of credits this 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: Davidd Tech — https://x.com/DaviddDotTech/status/2109201220766253205 (summarised from source; the source has no explicit step list)", "steps": [ "Give one agent the auditor job. In Claude Code the author pastes a prompt that starts “You’re my agent auditor. List every…”.", "List every running agent, what it does and what it costs.", "Flag agents that talk to each other without producing anything; the author lost $200 of credits this way." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 49.6, "sources": [ { "author": "Davidd Tech", "handle": "@DaviddDotTech", "url": "https://x.com/DaviddDotTech/status/2109201220766253205", "platform": "x", "date": "2026-10-11", "primary": true } ] }, { "slug": "dots-small-errands-brag-log", "url": "https://agentsetups.dev/use-case/dots-small-errands-brag-log/", "title": "Use your Dot for email, meetings, coupons and a brag log", "summary": "@simpsoka uses her Dot to organise email, book meetings, find coupon codes and keep a weekly log of wins for her boss.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [], "prompt": "Goal: Hand my Dot the small recurring chores.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Ask it to organise your email.\n2. Have it book meetings.\n3. Ask it to find coupon codes before you buy.\n4. Keep a running log of interesting things you did this week to share with your boss.\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: Kath Korevec — https://x.com/simpsoka/status/2106152475439026388", "steps": [ "Ask it to organise your email.", "Have it book meetings.", "Ask it to find coupon codes before you buy.", "Keep a running log of interesting things you did this week to share with your boss." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 49.0, "sources": [ { "author": "Kath Korevec", "handle": "@simpsoka", "url": "https://x.com/simpsoka/status/2106152475439026388", "platform": "x", "date": "2026-10-02", "primary": true } ] }, { "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": "manus-analyse-complex-dataset", "url": "https://agentsetups.dev/use-case/manus-analyse-complex-dataset/", "title": "Point Manus at a complex dataset", "summary": "In one reviewer’s test, Manus aggregated and tabulated a complex dataset, explained findings and suggested next lookups.", "category": "data-analysis", "category_label": "Data analysis", "agents": [ "Manus" ], "models": [], "tools": [], "prompt": "Goal: Get a quick analysis of a messy dataset.\nSetup: agents used in source: Manus.\nSteps:\n1. Give Manus the dataset.\n2. Ask it to aggregate, tabulate, explain what it found and suggest what to look up next.\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: emelu — https://x.com/emelucrypto/status/2105666507040518362 (summarised from source; the source has no explicit step list)", "steps": [ "Give Manus the dataset.", "Ask it to aggregate, tabulate, explain what it found and suggest what to look up next." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 48.4, "sources": [ { "author": "emelu", "handle": "@emelucrypto", "url": "https://x.com/emelucrypto/status/2105666507040518362", "platform": "x", "date": "2026-10-01", "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": "dots-family-school-alerts", "url": "https://agentsetups.dev/use-case/dots-family-school-alerts/", "title": "Have your Dot surface school and family changes", "summary": "With Google connected, @danveloper’s Dot proactively flagged his son’s English assignment and a changed pick-up time.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [ "Google (Gmail/Calendar)" ], "prompt": "Goal: Get proactive alerts about family logistics hidden in my email and calendar.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Google (Gmail/Calendar).\nSteps:\n1. Connect your Google account to ChatGPT so the Dot can read mail and calendar.\n2. Let it run proactively; it messages you only about things that matter (assignments, pick-up time 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: Dan Woods — https://x.com/danveloper/status/2106475882877694364 (summarised from source; the source has no explicit step list)", "steps": [ "Connect your Google account to ChatGPT so the Dot can read mail and calendar.", "Let it run proactively; it messages you only about things that matter (assignments, pick-up time changes)." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 48.2, "sources": [ { "author": "Dan Woods", "handle": "@danveloper", "url": "https://x.com/danveloper/status/2106475882877694364", "platform": "x", "date": "2026-10-03", "primary": true } ] }, { "slug": "docs-crawler-mcp-for-agents", "url": "https://agentsetups.dev/use-case/docs-crawler-mcp-for-agents/", "title": "Give agents a crawler that saves docs as Markdown", "summary": "pulpie-mcp saved 60 doc pages as clean Markdown in ~49s with a local 210M model, writing files instead of flooding context.", "category": "knowledge-memory", "category_label": "Knowledge & memory", "agents": [ "Claude", "Codex" ], "models": [ "pulpie-orange-small" ], "tools": [ "pulpie-mcp", "uv" ], "prompt": "Goal: Let my coding agents pull full documentation sites into local Markdown.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: pulpie-mcp, uv.\nSteps:\n1. Install: uv tool install git+https://github.com/pinkpixel-dev/pulpie-mcp\n2. Add to Claude Code: claude mcp add --scope user pulpie -- pulpie-mcp (or add it to ~/.codex/config.toml for Codex).\n3. Ask the agent to crawl_docs a documentation site; it checks robots.txt and sitemaps first.\n4. Pages are saved to files and only a summary returns, so the agent searches and reads them when needed.\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: Jessica Doering — https://dev.to/sizzlebop/i-gave-my-ai-agents-their-own-documentation-crawler-and-pulled-60-pages-of-clean-markdown-in-49-2cl7", "steps": [ "Install: uv tool install git+https://github.com/pinkpixel-dev/pulpie-mcp", "Add to Claude Code: claude mcp add --scope user pulpie -- pulpie-mcp (or add it to ~/.codex/config.toml for Codex).", "Ask the agent to crawl_docs a documentation site; it checks robots.txt and sitemaps first.", "Pages are saved to files and only a summary returns, so the agent searches and reads them when needed." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-05", "trend_score": 48.0, "sources": [ { "author": "Jessica Doering", "handle": "@sizzlebop", "url": "https://dev.to/sizzlebop/i-gave-my-ai-agents-their-own-documentation-crawler-and-pulled-60-pages-of-clean-markdown-in-49-2cl7", "platform": "devto", "date": "2026-10-05", "primary": true } ] }, { "slug": "runlevel-state-survive-compaction", "url": "https://agentsetups.dev/use-case/runlevel-state-survive-compaction/", "title": "Keep agent state in init.d-style files to survive compaction", "summary": "Instead of one PROGRESS.md, ordered runlevel-style state files plus fork/wait subagents survived two 230k-token compactions.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude", "Cursor", "Gemini CLI", "Antigravity" ], "models": [], "tools": [], "prompt": "Goal: Stop long agent sessions from losing their place after context compaction.\nSetup: agents used in source: Claude, Cursor, Gemini CLI, Antigravity.\nSteps:\n1. Don’t trust the auto-summary after compaction; keep state on disk.\n2. Avoid a single TODO.md/PROGRESS.md scratchpad; it gets stale or overwritten.\n3. Use ordered, lexically numbered state files per step, like SysV /etc/init.d runlevels, that the agent re-reads to resume.\n4. Push heavy work into forked subagents and wait on results, so the main context stays small.\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: Randal L. Schwartz — https://dev.to/gde/surviving-the-200k-token-lobotomy-how-unix-initd-and-memento-made-my-ai-coding-agent-immune-to-2f74 (summarised from source; the source has no explicit step list)", "steps": [ "Don’t trust the auto-summary after compaction; keep state on disk.", "Avoid a single TODO.md/PROGRESS.md scratchpad; it gets stale or overwritten.", "Use ordered, lexically numbered state files per step, like SysV /etc/init.d runlevels, that the agent re-reads to resume.", "Push heavy work into forked subagents and wait on results, so the main context stays small." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-10", "trend_score": 48.0, "sources": [ { "author": "Randal L. Schwartz", "handle": "@randalschwartz", "url": "https://dev.to/gde/surviving-the-200k-token-lobotomy-how-unix-initd-and-memento-made-my-ai-coding-agent-immune-to-2f74", "platform": "devto", "date": "2026-10-10", "primary": true } ] }, { "slug": "agent-inbox-mac-app", "url": "https://agentsetups.dev/use-case/agent-inbox-mac-app/", "title": "Watch and approve all your agents from one inbox", "summary": "littleguys, a free Mac app, shows which OpenClaw/Hermes/Claude Code/Codex/ACP agent is working or needs you.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude", "Codex", "OpenClaw", "Hermes Agent" ], "models": [], "tools": [ "littleguys", "ACP" ], "prompt": "Goal: See which agents need me and reply or approve quickly.\nSetup: agents used in source: Claude, Codex, OpenClaw, Hermes Agent; tools/MCPs stated: littleguys, ACP.\nSteps:\n1. Install littleguys (free, open-source).\n2. Connect your ACP agents.\n3. Reply in a few keystrokes and approve in one click.\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: Herval in the Metaverse of Madness ᯅ — https://x.com/herval/status/2109022124182491203 (summarised from source; the source has no explicit step list)", "steps": [ "Install littleguys (free, open-source).", "Connect your ACP agents.", "Reply in a few keystrokes and approve in one click." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-10", "trend_score": 47.9, "sources": [ { "author": "Herval in the Metaverse of Madness ᯅ", "handle": "@herval", "url": "https://x.com/herval/status/2109022124182491203", "platform": "x", "date": "2026-10-10", "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": "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": "chatgpt-agent-subscription-tracker", "url": "https://agentsetups.dev/use-case/chatgpt-agent-subscription-tracker/", "title": "Find every subscription in a year of receipts", "summary": "@alicialyttle’s ChatGPT agent reads 12 months of Gmail receipts, tables them, flags recurring charges and recommends cuts.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "ChatGPT agent" ], "models": [], "tools": [ "Gmail" ], "prompt": "Goal: See every subscription I’m paying for.\nSetup: agents used in source: ChatGPT agent; tools/MCPs stated: Gmail.\nSteps:\n1. Lock down privacy first: turn on MFA, and turn off model training in Data & privacy.\n2. Connect Gmail under Settings → Connectors.\n3. In the prompt box, click + and choose agent mode.\n4. Ask it to analyse receipts from the past 12 months, put them in a table, mark recurring subscriptions and recommend which need attention.\n5. Keep the chat private.\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: Alicia Lyttle — https://x.com/alicialyttle/status/2106031008239792532", "steps": [ "Lock down privacy first: turn on MFA, and turn off model training in Data & privacy.", "Connect Gmail under Settings → Connectors.", "In the prompt box, click + and choose agent mode.", "Ask it to analyse receipts from the past 12 months, put them in a table, mark recurring subscriptions and recommend which need attention.", "Keep the chat private." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 47.8, "sources": [ { "author": "Alicia Lyttle", "handle": "@alicialyttle", "url": "https://x.com/alicialyttle/status/2106031008239792532", "platform": "x", "date": "2026-10-02", "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": "claude-code-router-cheap-model", "url": "https://agentsetups.dev/use-case/claude-code-router-cheap-model/", "title": "Point Claude Code at a cheaper model with Router v3", "summary": "Set up Claude Code Router v3.1.1 to send a side project’s traffic to a cheaper model.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude" ], "models": [], "tools": [ "Claude Code Router" ], "prompt": "Goal: Use a cheaper model for a side project inside Claude Code.\nSetup: agents used in source: Claude; tools/MCPs stated: Claude Code Router.\nSteps:\n1. Install Claude Code Router v3.\n2. Configure the provider and model routing.\n3. Run Claude Code through the router.\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: Zara Menon — https://dev.to/zaramenon/claude-code-router-v3-what-changed-and-how-i-set-it-up-now-mj7 (summarised from source; the source has no explicit step list)", "steps": [ "Install Claude Code Router v3.", "Configure the provider and model routing.", "Run Claude Code through the router." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 47.7, "sources": [ { "author": "Zara Menon", "handle": "@zaramenon", "url": "https://dev.to/zaramenon/claude-code-router-v3-what-changed-and-how-i-set-it-up-now-mj7", "platform": "devto", "date": "2026-10-07", "primary": true } ] }, { "slug": "dots-catch-booking-mistakes", "url": "https://agentsetups.dev/use-case/dots-catch-booking-mistakes/", "title": "Let your Dot catch mistakes in your bookings", "summary": "@dkundel’s Dot spotted a missing second train ticket; @CtrlAltDwayne’s flagged a Fiji stay booked for the wrong month.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [], "prompt": "Goal: Have my Dot double-check purchases and bookings against my plans.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Give the Dot access to the inbox where confirmations land.\n2. Let it compare confirmations with what you planned and flag gaps (e.g. one ticket where two were needed, or a stay booked in the wrong month).\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: dominik kundel — https://x.com/dkundel/status/2110432654638333987 (summarised from source; the source has no explicit step list)", "steps": [ "Give the Dot access to the inbox where confirmations land.", "Let it compare confirmations with what you planned and flag gaps (e.g. one ticket where two were needed, or a stay booked in the wrong month)." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-14", "trend_score": 47.6, "sources": [ { "author": "dominik kundel", "handle": "@dkundel", "url": "https://x.com/dkundel/status/2110432654638333987", "platform": "x", "date": "2026-10-14", "primary": true }, { "author": "Dwayne", "handle": "@CtrlAltDwayne", "url": "https://x.com/CtrlAltDwayne/status/2105603794293887167", "platform": "x", "date": "2026-10-01", "primary": false } ] }, { "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": "context-bar-mod", "url": "https://agentsetups.dev/use-case/context-bar-mod/", "title": "Build a Claude Code mod without writing code", "summary": "One prompt produced an always-visible context-window bar; Claude wrote, validated and hot-reloaded the mod.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude" ], "models": [], "tools": [ "Claude Code mods" ], "prompt": "Goal: Show my context window fill level above the prompt at all times.\nSetup: agents used in source: Claude; tools/MCPs stated: Claude Code mods.\nSteps:\n1. Ask Claude to write a Claude Code mod (a JS/TS module in a plugin) for it.\n2. Have it validate and hot-reload 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: Pawel — https://dev.to/pawel_nowak/i-built-my-first-claude-code-mod-without-writing-code-claude-wrote-it-validated-it-and-2mh7", "steps": [ "Ask Claude to write a Claude Code mod (a JS/TS module in a plugin) for it.", "Have it validate and hot-reload the mod." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 46.7, "sources": [ { "author": "Pawel", "handle": "@pawel_nowak", "url": "https://dev.to/pawel_nowak/i-built-my-first-claude-code-mod-without-writing-code-claude-wrote-it-validated-it-and-2mh7", "platform": "devto", "date": "2026-10-03", "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": "muse-shop-recall-marketplace", "url": "https://agentsetups.dev/use-case/muse-shop-recall-marketplace/", "title": "Let Muse shop, book a recall fix and sell on Marketplace", "summary": "@IanAndrewsDC’s Muse bought furniture via Stripe Link, booked a recall appointment and listed items on Facebook Marketplace.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Meta Muse" ], "models": [], "tools": [ "Stripe Link", "Facebook Marketplace" ], "prompt": "Goal: Hand my Muse real purchases, appointments and selling.\nSetup: agents used in source: Meta Muse; tools/MCPs stated: Stripe Link, Facebook Marketplace.\nSteps:\n1. Furniture: send photos of the room and a description; review its 4 options, give feedback, let it search again, then let it buy (via Stripe Link).\n2. When it proactively flags a recall on your car, ask it to find a dealership and book the appointment.\n3. Marketplace: hand it links to the items and let it list them (expect a Facebook identity check), then monitor and reply to inquiries.\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 Andrews — https://x.com/IanAndrewsDC/status/2106109552047337870", "steps": [ "Furniture: send photos of the room and a description; review its 4 options, give feedback, let it search again, then let it buy (via Stripe Link).", "When it proactively flags a recall on your car, ask it to find a dealership and book the appointment.", "Marketplace: hand it links to the items and let it list them (expect a Facebook identity check), then monitor and reply to inquiries." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 45.3, "sources": [ { "author": "Ian Andrews", "handle": "@IanAndrewsDC", "url": "https://x.com/IanAndrewsDC/status/2106109552047337870", "platform": "x", "date": "2026-10-02", "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": "pi-dot-matrix-dashboard", "url": "https://agentsetups.dev/use-case/pi-dot-matrix-dashboard/", "title": "Feed a Raspberry Pi dot-matrix display from your agent", "summary": "A 90s-pinball style display shows weather, lake fishing conditions, bird reports, local shows, sports and AI news.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Hermes Agent" ], "models": [], "tools": [ "Raspberry Pi 5" ], "prompt": "Goal: Build a small display that my agent keeps updated.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: Raspberry Pi 5.\nSteps:\n1. Build the display (Raspberry Pi 5 dot-matrix; or Pi Zero 2 W with a 1.3\" screen).\n2. Have the agent feed it: weather, fishing conditions, a hyperlocal bird report, local shows, sports on TV and AI news.\n3. Variant: show Claude Code weekly quota, 5-hour window and model usage on screens you flip with a joystick.\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: Zachary Taylor — https://x.com/ztaylor/status/2108289455228616868", "steps": [ "Build the display (Raspberry Pi 5 dot-matrix; or Pi Zero 2 W with a 1.3\" screen).", "Have the agent feed it: weather, fishing conditions, a hyperlocal bird report, local shows, sports on TV and AI news.", "Variant: show Claude Code weekly quota, 5-hour window and model usage on screens you flip with a joystick." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 45.2, "sources": [ { "author": "Zachary Taylor", "handle": "@ztaylor", "url": "https://x.com/ztaylor/status/2108289455228616868", "platform": "x", "date": "2026-10-08", "primary": true } ] }, { "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": "alexa-skill-for-agent", "url": "https://agentsetups.dev/use-case/alexa-skill-for-agent/", "title": "Talk to your agents through Alexa", "summary": "Debbie O’Brien had her agent guide her through building an Alexa skill that talks to Grok Bot.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Grok Bot" ], "models": [], "tools": [ "Alexa" ], "prompt": "Goal: Build an Alexa skill that talks to my agent.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Alexa.\nSteps:\n1. Clone the alexa-grok-bot-skill repo; add your skill ID and webhook; deploy.\n2. When stuck in a console, ask the agent which box to click.\n3. Design around Alexa’s response-time limits.\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: Debbie O'Brien — https://dev.to/debs_obrien/talk-to-my-bots-through-alexa-building-an-alexa-skill-for-grok-bot-kak", "steps": [ "Clone the alexa-grok-bot-skill repo; add your skill ID and webhook; deploy.", "When stuck in a console, ask the agent which box to click.", "Design around Alexa’s response-time limits." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 44.0, "sources": [ { "author": "Debbie O'Brien", "handle": "@debs_obrien", "url": "https://dev.to/debs_obrien/talk-to-my-bots-through-alexa-building-an-alexa-skill-for-grok-bot-kak", "platform": "devto", "date": "2026-10-13", "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": "hermes-close-gaps-with-dots-grok", "url": "https://agentsetups.dev/use-case/hermes-close-gaps-with-dots-grok/", "title": "Close the gaps between Hermes and Dots or Grok Bot", "summary": "A gap analysis for Hermes users: persistent responsibilities, a read-only Scout routine, an autonomy policy file and persistent specialists.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Hermes Agent" ], "models": [], "tools": [ "cron", "webhooks", "pre_tool_call hooks", "Kanban" ], "prompt": "Goal: Make a self-hosted agent behave more like a proactive personal assistant.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: cron, webhooks, pre_tool_call hooks, Kanban.\nSteps:\n1. Add a small “responsibility” layer (objective, owner, triggers, skill, autonomy level, reporting policy) and let cron/events create durable tasks under it.\n2. Build a read-only Scout routine that checks authorised sources (email, calendar, GitHub, notes, feeds) and the web, then ignores, saves, attaches or notifies.\n3. Write an autonomy policy file enforced by pre_tool_call hooks, e.g. email.read auto, email.send ask, purchase ask, credentials human only.\n4. Use persistent specialist profiles plus temporary subagents under a coordinator.\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 analysis was produced with ChatGPT and depersonalised by the author.\nBased on: /u/MJ_Ali45 — https://www.reddit.com/r/hermesagent/comments/1wumxde/closing_most_gaps_between_hermes_vs_dots_and_grok/", "steps": [ "Add a small “responsibility” layer (objective, owner, triggers, skill, autonomy level, reporting policy) and let cron/events create durable tasks under it.", "Build a read-only Scout routine that checks authorised sources (email, calendar, GitHub, notes, feeds) and the web, then ignores, saves, attaches or notifies.", "Write an autonomy policy file enforced by pre_tool_call hooks, e.g. email.read auto, email.send ask, purchase ask, credentials human only.", "Use persistent specialist profiles plus temporary subagents under a coordinator." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 43.8, "sources": [ { "author": "/u/MJ_Ali45", "handle": "/u/MJ_Ali45", "url": "https://www.reddit.com/r/hermesagent/comments/1wumxde/closing_most_gaps_between_hermes_vs_dots_and_grok/", "platform": "reddit", "date": "2026-10-01", "primary": true } ] }, { "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": "parallel-sessions-one-checkout", "url": "https://agentsetups.dev/use-case/parallel-sessions-one-checkout/", "title": "Run three Claude Code sessions on one checkout", "summary": "No worktrees: sessions agree on a split, stage only their own hunks by id, and stop if the hunk count changes.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude" ], "models": [], "tools": [ "git" ], "prompt": "Goal: Let several agent sessions share one repo safely.\nSetup: agents used in source: Claude; tools/MCPs stated: git.\nSteps:\n1. Have sessions agree on a split by message and list the files each will touch.\n2. For shared files, stage only your own changes hunk by hunk, matched by an id in the changed lines.\n3. Use a small command that lists hunks and stages matching ones; if the hunk count changed between listing and staging, stage nothing and stop.\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/three-claude-code-sessions-share-one-git-checkout-in-our-repo-with-no-worktrees-how-do-you-keep-5dce", "steps": [ "Have sessions agree on a split by message and list the files each will touch.", "For shared files, stage only your own changes hunk by hunk, matched by an id in the changed lines.", "Use a small command that lists hunks and stages matching ones; if the hunk count changed between listing and staging, stage nothing and stop." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 43.0, "sources": [ { "author": "Rulestack", "handle": "@rulestack", "url": "https://dev.to/rulestack/three-claude-code-sessions-share-one-git-checkout-in-our-repo-with-no-worktrees-how-do-you-keep-5dce", "platform": "devto", "date": "2026-10-08", "primary": true } ] }, { "slug": "unreal-engine-game", "url": "https://agentsetups.dev/use-case/unreal-engine-game/", "title": "Build an Unreal Engine game mission with Claude Code", "summary": "Loadout menus, shooting mechanics, bullet effects and ragdoll physics built in Unreal with Claude Code.", "category": "games", "category_label": "Games", "agents": [ "Claude", "Antigravity" ], "models": [], "tools": [ "Unreal Engine" ], "prompt": "Goal: Build a playable mission in a real game engine.\nSetup: agents used in source: Claude, Antigravity; tools/MCPs stated: Unreal Engine.\nSteps:\n1. Set up the engine project.\n2. Have the agent build loadout menus, shooting, effects and physics.\n3. Play the mission and iterate.\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: Brendan Jowett — https://x.com/jowettbrendan/status/2109538818210799979 (summarised from source; the source has no explicit step list)", "steps": [ "Set up the engine project.", "Have the agent build loadout menus, shooting, effects and physics.", "Play the mission and iterate." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 42.9, "sources": [ { "author": "Brendan Jowett", "handle": "@jowettbrendan", "url": "https://x.com/jowettbrendan/status/2109538818210799979", "platform": "x", "date": "2026-10-12", "primary": true }, { "author": "Chouaieb Nemri", "handle": "@c_nemri", "url": "https://x.com/c_nemri/status/2104472843815735362", "platform": "x", "date": "2026-09-28", "primary": false } ] }, { "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": "obsidian-claude-shared-memory", "url": "https://agentsetups.dev/use-case/obsidian-claude-shared-memory/", "title": "Use Obsidian folders as Claude Code’s shared memory", "summary": "Inbox, projects (each with CLAUDE.md), a memory tree for people/decisions/bugs, and docs Claude reads.", "category": "knowledge-memory", "category_label": "Knowledge & memory", "agents": [ "Claude" ], "models": [], "tools": [ "Obsidian" ], "prompt": "Goal: Organise my vault so Claude Code uses it as memory.\nSetup: agents used in source: Claude; tools/MCPs stated: Obsidian.\nSteps:\n1. Create /00-inbox, /01-projects (each with its own CLAUDE.md), /02-memory and /03-docs.\n2. Keep people, decisions and bugs in the memory tree.\n3. Put stack and rules in each project’s CLAUDE.md.\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: v. Splicer — https://dev.to/numbpill3d/obsidian-claude-code-the-shared-memory-stack-i-actually-use-8m", "steps": [ "Create /00-inbox, /01-projects (each with its own CLAUDE.md), /02-memory and /03-docs.", "Keep people, decisions and bugs in the memory tree.", "Put stack and rules in each project’s CLAUDE.md." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 41.5, "sources": [ { "author": "v. Splicer", "handle": "@numbpill3d", "url": "https://dev.to/numbpill3d/obsidian-claude-code-the-shared-memory-stack-i-actually-use-8m", "platform": "devto", "date": "2026-10-08", "primary": true } ] }, { "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": "pwa-game-in-a-day", "url": "https://agentsetups.dev/use-case/pwa-game-in-a-day/", "title": "Ship a PWA game in a day from a three-sentence idea", "summary": "Opus 5.5 in Claude Code shipped a browser game using about half a daily allotment; the harness mattered.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [], "prompt": "Goal: Turn a short idea into a shipped browser game in a day.\nSetup: agents used in source: Claude.\nSteps:\n1. Start from a short idea, but set up the harness: structure, checks and a playable loop.\n2. Iterate with the agent and deploy as a PWA.\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: Tiago Vilas Boas (Montanha) — https://dev.to/tiagovilasboas/i-built-a-full-pwa-game-in-one-day-with-claude-opus-55-and-claude-code-here-is-the-real-token-41p7 (summarised from source; the source has no explicit step list)", "steps": [ "Start from a short idea, but set up the harness: structure, checks and a playable loop.", "Iterate with the agent and deploy as a PWA." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 40.9, "sources": [ { "author": "Tiago Vilas Boas (Montanha)", "handle": "@tiagovilasboas", "url": "https://dev.to/tiagovilasboas/i-built-a-full-pwa-game-in-one-day-with-claude-opus-55-and-claude-code-here-is-the-real-token-41p7", "platform": "devto", "date": "2026-10-04", "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": "muse-price-drop-watch", "url": "https://agentsetups.dev/use-case/muse-price-drop-watch/", "title": "Ask Muse for the best product and get price-drop alerts", "summary": "@chrissev asked Muse for the best walking pad; two weeks later it told him, unprompted, it was on sale for $93.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Meta Muse" ], "models": [], "tools": [], "prompt": "Goal: Research a purchase and get told when the price drops.\nSetup: agents used in source: Meta Muse.\nSteps:\n1. Ask Muse for the best option in a category.\n2. Let it keep the request in memory; it may alert you to a sale without being asked.\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 Sev — https://x.com/chrissev/status/2107917341455729040 (summarised from source; the source has no explicit step list)", "steps": [ "Ask Muse for the best option in a category.", "Let it keep the request in memory; it may alert you to a sale without being asked." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 38.8, "sources": [ { "author": "Chris Sev", "handle": "@chrissev", "url": "https://x.com/chrissev/status/2107917341455729040", "platform": "x", "date": "2026-10-07", "primary": true } ] }, { "slug": "grokbot-track-launch-feedback-x", "url": "https://agentsetups.dev/use-case/grokbot-track-launch-feedback-x/", "title": "Have Grok Bot track feedback on your launches", "summary": "Grok Bot found five of a builder’s launched projects, analysed replies, quotes and mentions, then set a daily check.", "category": "marketing-growth", "category_label": "Marketing & growth", "agents": [ "Grok Bot" ], "models": [], "tools": [ "X" ], "prompt": "Goal: Never miss product feedback people leave on X.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: X.\nSteps:\n1. Ask Grok Bot to find the products you launched on X and analyse replies, quotes and mentions for feedback you missed.\n2. Have it set up a daily routine to check for new feedback, spot new launches and alert you when something needs attention.\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: Karata — https://x.com/karatademada/status/2108094746392494217", "steps": [ "Ask Grok Bot to find the products you launched on X and analyse replies, quotes and mentions for feedback you missed.", "Have it set up a daily routine to check for new feedback, spot new launches and alert you when something needs attention." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 38.6, "sources": [ { "author": "Karata", "handle": "@karatademada", "url": "https://x.com/karatademada/status/2108094746392494217", "platform": "x", "date": "2026-10-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": "amp-debug-token-migrate-node", "url": "https://agentsetups.dev/use-case/amp-debug-token-migrate-node/", "title": "Let Amp find a deploy bug and upgrade Node", "summary": "Amp traced a bad API token from headers alone, reproduced it, migrated deps and code to Node.js v24; first PR all green.", "category": "coding", "category_label": "Coding", "agents": [ "Amp" ], "models": [], "tools": [ "Node.js" ], "prompt": "Goal: Get a broken project re-deployable.\nSetup: agents used in source: Amp; tools/MCPs stated: Node.js.\nSteps:\n1. Give Amp the failing project and symptoms.\n2. Let it diagnose from the request headers and reproduce the issue.\n3. Have it migrate dependencies and code to Node.js v24.\n4. Review the PR once checks are green.\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: Liran Tal — https://x.com/liran_tal/status/2109636209374904758", "steps": [ "Give Amp the failing project and symptoms.", "Let it diagnose from the request headers and reproduce the issue.", "Have it migrate dependencies and code to Node.js v24.", "Review the PR once checks are green." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 38.0, "sources": [ { "author": "Liran Tal", "handle": "@liran_tal", "url": "https://x.com/liran_tal/status/2109636209374904758", "platform": "x", "date": "2026-10-12", "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": "warcraft3-map-sim-from-phone", "url": "https://agentsetups.dev/use-case/warcraft3-map-sim-from-phone/", "title": "Build a big project mostly from your phone with Amp", "summary": "A TypeScript simulator that runs any Warcraft 3 custom map in the browser with multiplayer, 95% prompted from a phone.", "category": "games", "category_label": "Games", "agents": [ "Amp" ], "models": [], "tools": [ "TypeScript" ], "prompt": "Goal: Drive a large coding project from my phone.\nSetup: agents used in source: Amp; tools/MCPs stated: TypeScript.\nSteps:\n1. Run the project in Amp and prompt it from your phone.\n2. Iterate on bugs and performance as they come 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: Richard Artoul — https://x.com/richardartoul/status/2105821616899015035 (summarised from source; the source has no explicit step list)", "steps": [ "Run the project in Amp and prompt it from your phone.", "Iterate on bugs and performance as they come up." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 37.7, "sources": [ { "author": "Richard Artoul", "handle": "@richardartoul", "url": "https://x.com/richardartoul/status/2105821616899015035", "platform": "x", "date": "2026-10-02", "primary": true } ] }, { "slug": "meta-ads-dashboard", "url": "https://agentsetups.dev/use-case/meta-ads-dashboard/", "title": "Build your own Meta Ads dashboard with Claude Code", "summary": "A System User token with ads_read lets Claude Code pull the Marketing API into a custom dashboard.", "category": "marketing-growth", "category_label": "Marketing & growth", "agents": [ "Claude" ], "models": [], "tools": [ "Meta Marketing API" ], "prompt": "Goal: Build a dashboard of the Meta Ads numbers I actually care about.\nSetup: agents used in source: Claude; tools/MCPs stated: Meta Marketing API.\nSteps:\n1. In Meta Business Settings, create a System User.\n2. Give it access to your ad account and generate a token with ads_read permission.\n3. Hand the token to Claude Code and tell it what you want to track (leading indicators, per-campaign and creative performance).\n4. It pulls data from the Meta Marketing API and builds the dashboard around your numbers.\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: @dukedoesai reports £35.8k spend → £129.6k revenue, run from Claude Code (own claim).\nBased on: Chris Panteli (Co-Founder) — https://x.com/Linkifi_/status/2105935542315528437", "steps": [ "In Meta Business Settings, create a System User.", "Give it access to your ad account and generate a token with ads_read permission.", "Hand the token to Claude Code and tell it what you want to track (leading indicators, per-campaign and creative performance).", "It pulls data from the Meta Marketing API and builds the dashboard around your numbers." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 37.5, "sources": [ { "author": "Chris Panteli (Co-Founder)", "handle": "@Linkifi_", "url": "https://x.com/Linkifi_/status/2105935542315528437", "platform": "x", "date": "2026-10-02", "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": "kiro-unattended-s3-lambda-loop", "url": "https://agentsetups.dev/use-case/kiro-unattended-s3-lambda-loop/", "title": "Check event triggers before leaving Kiro unattended", "summary": "Kiro’s thumbnail feature wrote back into the bucket that triggered it; AWS caught the recursive Lambda loop. Use separate buckets.", "category": "devops", "category_label": "DevOps", "agents": [ "Kiro" ], "models": [], "tools": [ "AWS Lambda", "S3", "Terraform", "Go" ], "prompt": "Goal: Let an agent build serverless features without creating runaway loops.\nSetup: agents used in source: Kiro; tools/MCPs stated: AWS Lambda, S3, Terraform, Go.\nSteps:\n1. Before walking away, review what triggers each function and where its outputs land.\n2. Break write-back loops: separate buckets for originals and derivatives, or filter the trigger by prefix.\n3. “It deployed and the happy path worked” isn’t “safe to walk away”; test the side effects.\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: pmalmirae — https://dev.to/aws-builders/dont-try-this-at-home-what-happened-when-i-sent-kiro-to-work-and-went-gardening-131c", "steps": [ "Before walking away, review what triggers each function and where its outputs land.", "Break write-back loops: separate buckets for originals and derivatives, or filter the trigger by prefix.", "“It deployed and the happy path worked” isn’t “safe to walk away”; test the side effects." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 37.4, "sources": [ { "author": "pmalmirae", "handle": "@pmalmirae", "url": "https://dev.to/aws-builders/dont-try-this-at-home-what-happened-when-i-sent-kiro-to-work-and-went-gardening-131c", "platform": "devto", "date": "2026-10-13", "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": "local-model-judges-shell-commands", "url": "https://agentsetups.dev/use-case/local-model-judges-shell-commands/", "title": "Have a small local model vet agent shell commands", "summary": "A hook sends every command to a 322M local model that returns allow, review or block; tuned against false blocks and chained commands.", "category": "security", "category_label": "Security", "agents": [ "Claude", "Cursor" ], "models": [], "tools": [ "laya-guard" ], "prompt": "Goal: Catch dangerous commands from my coding agent locally, without cloud calls.\nSetup: agents used in source: Claude, Cursor; tools/MCPs stated: laya-guard.\nSteps:\n1. Run a small local server that classifies each tool call as allow, review or block; the agent’s hook calls it before execution.\n2. Test on everyday commands: the first version blocked ls -la and npm run build, so add a careful allowlist.\n3. Don’t allowlist by command name alone (git log --output can write files); split command chains (&&, |) and check every part.\n4. Know the trade-off: it fails open if the server is down.\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: Changsu Seong — https://dev.to/scs0209/i-let-a-322m-local-model-judge-every-shell-command-my-coding-agent-runs-2hf6", "steps": [ "Run a small local server that classifies each tool call as allow, review or block; the agent’s hook calls it before execution.", "Test on everyday commands: the first version blocked ls -la and npm run build, so add a careful allowlist.", "Don’t allowlist by command name alone (git log --output can write files); split command chains (&&, |) and check every part.", "Know the trade-off: it fails open if the server is down." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 37.0, "sources": [ { "author": "Changsu Seong", "handle": "@scs0209", "url": "https://dev.to/scs0209/i-let-a-322m-local-model-judge-every-shell-command-my-coding-agent-runs-2hf6", "platform": "devto", "date": "2026-10-11", "primary": true } ] }, { "slug": "grokbot-cancel-unused-subscriptions", "url": "https://agentsetups.dev/use-case/grokbot-cancel-unused-subscriptions/", "title": "Cancel unused subscriptions with Grok Bot", "summary": "Grok Bot read email and bank data, found every subscription and cancelled unused ones (Audible, Uber One, SiriusXM): ~$1,700/yr.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Grok Bot" ], "models": [], "tools": [ "email", "bank" ], "prompt": "Goal: Stop paying for subscriptions I don’t use.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: email, bank.\nSteps:\n1. Give Grok Bot access to your email and bank.\n2. Have it list every subscription you pay for.\n3. Have it cancel the unused ones, emailing providers where needed (it cited BC consumer rules to SiriusXM).\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: Devin Olsen — https://x.com/DevinOlsenn/status/2110595533891067938 (summarised from source; the source has no explicit step list)", "steps": [ "Give Grok Bot access to your email and bank.", "Have it list every subscription you pay for.", "Have it cancel the unused ones, emailing providers where needed (it cited BC consumer rules to SiriusXM)." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 36.2, "sources": [ { "author": "Devin Olsen", "handle": "@DevinOlsenn", "url": "https://x.com/DevinOlsenn/status/2110595533891067938", "platform": "x", "date": "2026-10-15", "primary": true } ] }, { "slug": "grokbot-fix-mac-going-offline", "url": "https://agentsetups.dev/use-case/grokbot-fix-mac-going-offline/", "title": "Ask Grok Bot why your Mac keeps going offline", "summary": "@Kevin_Logan’s Grok Bot found why his Mac kept sleeping and breaking automations, wrote the fix and installed it.", "category": "devops", "category_label": "DevOps", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Keep the machine my automations run on awake and online.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Ask your bot why the Mac keeps going offline.\n2. Let it find the cause, write the fix and install 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: Kevin Logan — https://x.com/Kevin_Logan/status/2109084141417300385 (summarised from source; the source has no explicit step list)", "steps": [ "Ask your bot why the Mac keeps going offline.", "Let it find the cause, write the fix and install it." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 36.1, "sources": [ { "author": "Kevin Logan", "handle": "@Kevin_Logan", "url": "https://x.com/Kevin_Logan/status/2109084141417300385", "platform": "x", "date": "2026-10-11", "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": "multi-agent-vps-solana-mvp", "url": "https://agentsetups.dev/use-case/multi-agent-vps-solana-mvp/", "title": "Run a multi-agent dev system on a cheap VPS", "summary": "Hermes, Orca, Engram/MCP, Claude Code and Codex with git worktrees, tmux and a human gate shipped a Solana escrow MVP.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude", "Codex", "Hermes Agent" ], "models": [], "tools": [ "Oracle Cloud", "Orca", "Engram", "git worktrees", "tmux" ], "prompt": "Goal: Build an MVP with several agents outside the IDE.\nSetup: agents used in source: Claude, Codex, Hermes Agent; tools/MCPs stated: Oracle Cloud, Orca, Engram, git worktrees, tmux.\nSteps:\n1. Set up a VPS (here Oracle Cloud).\n2. Run Hermes, Orca, Engram/MCP, Claude Code and Codex there.\n3. Isolate work in git worktrees and tmux sessions.\n4. Keep a human gate before merges.\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: Yhona e/acc — https://x.com/thisnotmeeme/status/2106946532880589115", "steps": [ "Set up a VPS (here Oracle Cloud).", "Run Hermes, Orca, Engram/MCP, Claude Code and Codex there.", "Isolate work in git worktrees and tmux sessions.", "Keep a human gate before merges." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-05", "trend_score": 35.6, "sources": [ { "author": "Yhona e/acc", "handle": "@thisnotmeeme", "url": "https://x.com/thisnotmeeme/status/2106946532880589115", "platform": "x", "date": "2026-10-05", "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": "grokbot-investigate-phishing-email", "url": "https://agentsetups.dev/use-case/grokbot-investigate-phishing-email/", "title": "Have Grok Bot investigate a suspicious email", "summary": "An email passed SPF, DKIM and DMARC, but Grok Bot found the hidden phishing link and explained why the checks passed.", "category": "security", "category_label": "Security", "agents": [ "Grok Bot" ], "models": [], "tools": [ "email" ], "prompt": "Goal: Check a suspicious email before clicking anything in it.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: email.\nSteps:\n1. Ask your bot to investigate the email.\n2. Have it look for hidden links and explain why authentication checks (SPF, DKIM, DMARC) passed anyway.\n3. Have it suggest a fix or prepare 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.\nNote: A single shared example; it says nothing about how reliably it catches scams.\nBased on: Alex — https://x.com/alexmichaelio/status/2110574355256394089", "steps": [ "Ask your bot to investigate the email.", "Have it look for hidden links and explain why authentication checks (SPF, DKIM, DMARC) passed anyway.", "Have it suggest a fix or prepare a report." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 34.9, "sources": [ { "author": "Alex", "handle": "@alexmichaelio", "url": "https://x.com/alexmichaelio/status/2110574355256394089", "platform": "x", "date": "2026-10-15", "primary": true }, { "author": "Winter", "handle": "@ghosttrends", "url": "https://x.com/ghosttrends/status/2110544969262084330", "platform": "x", "date": "2026-10-15", "primary": false } ] }, { "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": "coding-agent-inside-android-app", "url": "https://agentsetups.dev/use-case/coding-agent-inside-android-app/", "title": "Run a coding agent inside an Android app", "summary": "AndroPI wraps the open-source pi agent in Flutter, with a rootless Debian userland, DNS-over-HTTPS and a live HTML preview.", "category": "coding", "category_label": "Coding", "agents": [ "Pi" ], "models": [], "tools": [ "Flutter", "Node.js", "Debian userland" ], "prompt": "Goal: Use a real coding agent on an Android phone.\nSetup: agents used in source: Pi; tools/MCPs stated: Flutter, Node.js, Debian userland.\nSteps:\n1. Wrap the pi agent in a Flutter UI.\n2. Android won’t execute binaries from app storage, so run a Debian or Alpine userland without root so the agent can apt, pip and npm.\n3. Add DNS-over-HTTPS if your ISP tampers with lookups.\n4. Expect Play Store pushback on all-files access; keep a live HTML preview for web 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: Taqin — https://dev.to/abdulm/i-put-an-ai-coding-agent-inside-an-android-app-heres-everything-that-fought-back-lpk", "steps": [ "Wrap the pi agent in a Flutter UI.", "Android won’t execute binaries from app storage, so run a Debian or Alpine userland without root so the agent can apt, pip and npm.", "Add DNS-over-HTTPS if your ISP tampers with lookups.", "Expect Play Store pushback on all-files access; keep a live HTML preview for web work." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 34.8, "sources": [ { "author": "Taqin", "handle": "@abdulm", "url": "https://dev.to/abdulm/i-put-an-ai-coding-agent-inside-an-android-app-heres-everything-that-fought-back-lpk", "platform": "devto", "date": "2026-10-02", "primary": true } ] }, { "slug": "grokbot-freelancer-invoices-poland", "url": "https://agentsetups.dev/use-case/grokbot-freelancer-invoices-poland/", "title": "Move a one-person business’s paperwork to Grok Bot", "summary": "16 agents handle invoices, deals, contracts and X content; the move used ~5% of a weekly limit. National e-invoicing is the hard part.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Grok Bot" ], "models": [], "tools": [ "KSeF" ], "prompt": "Goal: Run invoicing, contracts and content for my sole proprietorship with agents.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: KSeF.\nSteps:\n1. Set up agents for invoices, deals, creator contracts, approvals and X content.\n2. Expect friction where systems are built for paper: national e-invoicing (KSeF) needs certificates and a clunky API; accountants may only take PDFs.\n3. Let the agent draft invoices, then carry them through those systems yourself.\n4. Save repeatable jobs as skills (his reads invoices, converts currency, checks screenshots for leaks and writes the post).\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: ＺＥＦＩ — https://x.com/zefirium/status/2108547389120221411", "steps": [ "Set up agents for invoices, deals, creator contracts, approvals and X content.", "Expect friction where systems are built for paper: national e-invoicing (KSeF) needs certificates and a clunky API; accountants may only take PDFs.", "Let the agent draft invoices, then carry them through those systems yourself.", "Save repeatable jobs as skills (his reads invoices, converts currency, checks screenshots for leaks and writes the post)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 34.6, "sources": [ { "author": "ＺＥＦＩ", "handle": "@zefirium", "url": "https://x.com/zefirium/status/2108547389120221411", "platform": "x", "date": "2026-10-09", "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": "woocommerce-mcp-with-approvals", "url": "https://agentsetups.dev/use-case/woocommerce-mcp-with-approvals/", "title": "Let an agent manage a WooCommerce store with approvals", "summary": "A WordPress plugin turns the store into an MCP server with OAuth 2.1; Muse Spark proposes a product and you approve it.", "category": "automation-integrations", "category_label": "Automation & integrations", "agents": [ "Muse Code" ], "models": [ "Muse Spark" ], "tools": [ "WordPress", "WooCommerce", "MCP", "OAuth 2.1" ], "prompt": "Goal: Give an AI agent controlled access to my online store.\nSetup: agents used in source: Muse Code; tools/MCPs stated: WordPress, WooCommerce, MCP, OAuth 2.1.\nSteps:\n1. Install an MCP bridge plugin (the author’s MuseSpark MCP Bridge) to expose selected WordPress/WooCommerce tools.\n2. Authorise the agent via the plugin’s OAuth 2.1 server.\n3. Have the agent propose actions (e.g. create a product with price, stock, SKU, categories and SEO).\n4. Review and approve each action in the admin dashboard before it 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: Joni Ilman Pahmi — https://dev.to/joni_ilman12/i-turned-my-wordpress-store-into-an-mcp-server-now-an-ai-agent-runs-my-business-with-my-1i3c", "steps": [ "Install an MCP bridge plugin (the author’s MuseSpark MCP Bridge) to expose selected WordPress/WooCommerce tools.", "Authorise the agent via the plugin’s OAuth 2.1 server.", "Have the agent propose actions (e.g. create a product with price, stock, SKU, categories and SEO).", "Review and approve each action in the admin dashboard before it runs." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 34.4, "sources": [ { "author": "Joni Ilman Pahmi", "handle": "@joni_ilman12", "url": "https://dev.to/joni_ilman12/i-turned-my-wordpress-store-into-an-mcp-server-now-an-ai-agent-runs-my-business-with-my-1i3c", "platform": "devto", "date": "2026-10-09", "primary": true } ] }, { "slug": "three-layer-claude-code-safety", "url": "https://agentsetups.dev/use-case/three-layer-claude-code-safety/", "title": "Protect files with sandbox, hooks and checkpoints", "summary": "Turn on /sandbox, block destructive commands with hooks, and keep git checkpoints so one bad command is a one-step rollback.", "category": "security", "category_label": "Security", "agents": [ "Claude" ], "models": [], "tools": [ "Seatbelt", "bubblewrap", "git" ], "prompt": "Goal: Let Claude Code run real commands without risking my files.\nSetup: agents used in source: Claude; tools/MCPs stated: Seatbelt, bubblewrap, git.\nSteps:\n1. Layer 1: run /sandbox in a session; writes are confined to the project at OS level (Seatbelt on macOS, bubblewrap on Linux/WSL2). Not on native Windows.\n2. Layer 2: add hooks that stop destructive commands (force-push to main, DROP TABLE, reset --hard) or make Claude ask first.\n3. Layer 3: keep git checkpoints so you can roll back in one command if something slips through.\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: anassBld — https://dev.to/anasbuilds997/claude-code-can-delete-your-files-the-3-layer-setup-i-run-sandbox-hooks-git-checkpoints-188h", "steps": [ "Layer 1: run /sandbox in a session; writes are confined to the project at OS level (Seatbelt on macOS, bubblewrap on Linux/WSL2). Not on native Windows.", "Layer 2: add hooks that stop destructive commands (force-push to main, DROP TABLE, reset --hard) or make Claude ask first.", "Layer 3: keep git checkpoints so you can roll back in one command if something slips through." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 34.2, "sources": [ { "author": "anassBld", "handle": "@anasbuilds997", "url": "https://dev.to/anasbuilds997/claude-code-can-delete-your-files-the-3-layer-setup-i-run-sandbox-hooks-git-checkpoints-188h", "platform": "devto", "date": "2026-10-08", "primary": true } ] }, { "slug": "dots-find-emails-that-slipped", "url": "https://agentsetups.dev/use-case/dots-find-emails-that-slipped/", "title": "Ask your Dot for emails that fell through the cracks", "summary": "@arpans’ Dot found a document he owed his CPA plus vendor and appointment follow-ups; another user’s Dot nudges each new email.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [], "prompt": "Goal: Find what I forgot to act on in my personal inbox.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Connect your personal inbox.\n2. Ask: find emails that fell through the cracks.\n3. Review what it surfaces: documents to forward (e.g. to your accountant), appointment and vendor follow-ups.\n4. Optionally let it nudge you on each new email and ask it to send emails or update sheets and docs for you.\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: Arpan Shah — https://x.com/arpans/status/2109885241989218560", "steps": [ "Connect your personal inbox.", "Ask: find emails that fell through the cracks.", "Review what it surfaces: documents to forward (e.g. to your accountant), appointment and vendor follow-ups.", "Optionally let it nudge you on each new email and ask it to send emails or update sheets and docs for you." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 33.5, "sources": [ { "author": "Arpan Shah", "handle": "@arpans", "url": "https://x.com/arpans/status/2109885241989218560", "platform": "x", "date": "2026-10-13", "primary": true }, { "author": "Ali", "handle": "@somehowali", "url": "https://x.com/somehowali/status/2107195622562373662", "platform": "x", "date": "2026-10-05", "primary": false } ] }, { "slug": "find-wasted-disk-space", "url": "https://agentsetups.dev/use-case/find-wasted-disk-space/", "title": "Find 112 GB of wasted disk space without deleting anything", "summary": "A pasteable prompt sorts repos, build outputs, node_modules, caches, Xcode and old worktrees into tables before any deletion.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Find what is eating my disk.\nSetup: agents used in source: Claude.\nSteps:\n1. Check repos, gitignored build outputs, node_modules, caches, Xcode, simulators and old worktrees.\n2. Don’t delete anything yet.\n3. Give me tables, starting with “safe to delete” and “rebuildable”, so I can choose.\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: Dante — https://x.com/dantegaleazzi/status/2109587379266990278", "steps": [ "Check repos, gitignored build outputs, node_modules, caches, Xcode, simulators and old worktrees.", "Don’t delete anything yet.", "Give me tables, starting with “safe to delete” and “rebuildable”, so I can choose." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 33.1, "sources": [ { "author": "Dante", "handle": "@dantegaleazzi", "url": "https://x.com/dantegaleazzi/status/2109587379266990278", "platform": "x", "date": "2026-10-12", "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": "three-js-game-zero-assets", "url": "https://agentsetups.dev/use-case/three-js-game-zero-assets/", "title": "Build a cozy three.js game with zero imported assets", "summary": "Every cat, bowl, pond and tree made in code with Claude Code; the trick is the agent never guesses — it’s all written down first.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [], "tools": [ "three.js" ], "prompt": "Goal: Make a cute 3D restaurant game without any asset packs.\nSetup: agents used in source: Claude; tools/MCPs stated: three.js.\nSteps:\n1. Write one brief before building.\n2. Write down everything the agent needs so it never guesses.\n3. Have Claude Code build every model procedurally in three.js.\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: anul agarwal — https://x.com/anulagarwal/status/2110599427656429939 (summarised from source; the source has no explicit step list)", "steps": [ "Write one brief before building.", "Write down everything the agent needs so it never guesses.", "Have Claude Code build every model procedurally in three.js." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 32.5, "sources": [ { "author": "anul agarwal", "handle": "@anulagarwal", "url": "https://x.com/anulagarwal/status/2110599427656429939", "platform": "x", "date": "2026-10-15", "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": "family-business-erp-claude-code", "url": "https://agentsetups.dev/use-case/family-business-erp-claude-code/", "title": "Build your family business’s own ERP with Claude Code", "summary": "A car-wash service firm replaced its ERP and runs agents; humans approve anything with money, from a phone.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Claude" ], "models": [], "tools": [ "SQL" ], "prompt": "Goal: Replace commercial business software with our own, built with AI.\nSetup: agents used in source: Claude; tools/MCPs stated: SQL.\nSteps:\n1. Write procedures down; every incident becomes a dated rule the agents read.\n2. Use an approval loop: review the day’s decisions from your phone; nothing with money moves without a human click.\n3. Keep production and testing in separate copies with separate databases.\n4. Test the money logic: invoice numbering per series, VAT, rounding, against real SQL on many random documents.\n5. Use one session per topic with a short hand-over note; long sessions waste tokens. Keep local models to small mechanical jobs.\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: Jorge Garzón — https://dev.to/satgarzon/two-years-in-a-family-car-wash-service-company-running-its-own-erp-and-ai-agents-built-with-claude-89a", "steps": [ "Write procedures down; every incident becomes a dated rule the agents read.", "Use an approval loop: review the day’s decisions from your phone; nothing with money moves without a human click.", "Keep production and testing in separate copies with separate databases.", "Test the money logic: invoice numbering per series, VAT, rounding, against real SQL on many random documents.", "Use one session per topic with a short hand-over note; long sessions waste tokens. Keep local models to small mechanical jobs." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 31.8, "sources": [ { "author": "Jorge Garzón", "handle": "@satgarzon", "url": "https://dev.to/satgarzon/two-years-in-a-family-car-wash-service-company-running-its-own-erp-and-ai-agents-built-with-claude-89a", "platform": "devto", "date": "2026-10-09", "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": "supply-chain-ops-agent", "url": "https://agentsetups.dev/use-case/supply-chain-ops-agent/", "title": "Run supply-chain paperwork with an ops agent team", "summary": "Officer Can handles co-packer paperwork, vendor forms, COAs, POs and chasing docs for a beverage brand.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Claude", "Codex" ], "models": [], "tools": [], "prompt": "Goal: Build an operations team that does my supply-chain busywork.\nSetup: agents used in source: Claude, Codex.\nSteps:\n1. Hand the Officer Can playbook to Claude Code or Codex to build the system for your business.\n2. Roles: Inbox Clerk (sorts email), Form Filler (remembers your answers), Negotiator (replies from the facts), File Clerk (files attachments, watches expiry dates).\n3. Focus your time on relationships while it does the papers.\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 Cauble — https://x.com/thecauble/status/2105674557407281490", "steps": [ "Hand the Officer Can playbook to Claude Code or Codex to build the system for your business.", "Roles: Inbox Clerk (sorts email), Form Filler (remembers your answers), Negotiator (replies from the facts), File Clerk (files attachments, watches expiry dates).", "Focus your time on relationships while it does the papers." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 31.2, "sources": [ { "author": "Matt Cauble", "handle": "@thecauble", "url": "https://x.com/thecauble/status/2105674557407281490", "platform": "x", "date": "2026-10-01", "primary": true } ] }, { "slug": "esp32-wake-time-skill", "url": "https://agentsetups.dev/use-case/esp32-wake-time-skill/", "title": "Cut an ESP32 display’s wake time from 7s to 0.9s", "summary": "Applying Anthropic’s “how we made it faster” method; battery life goes from ~1 month to ~10. Packaged as a Claude Code skill.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Claude" ], "models": [], "tools": [ "ESP32" ], "prompt": "Goal: Make a slow device or program start faster.\nSetup: agents used in source: Claude; tools/MCPs stated: ESP32.\nSteps:\n1. Apply Anthropic’s published speed-up method to your software (here a battery-powered ESP32 display).\n2. Measure wake time and battery impact before and after.\n3. Turn the method into a Claude Code skill to reuse on any software.\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: Steve Dakh — https://x.com/stevedakh/status/2109702526845014040 (summarised from source; the source has no explicit step list)", "steps": [ "Apply Anthropic’s published speed-up method to your software (here a battery-powered ESP32 display).", "Measure wake time and battery impact before and after.", "Turn the method into a Claude Code skill to reuse on any software." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 31.2, "sources": [ { "author": "Steve Dakh", "handle": "@stevedakh", "url": "https://x.com/stevedakh/status/2109702526845014040", "platform": "x", "date": "2026-10-12", "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": "cheap-models-as-claude-subagents", "url": "https://agentsetups.dev/use-case/cheap-models-as-claude-subagents/", "title": "Use cheap models as subagents inside Claude Code", "summary": "Many cheap models speak the Anthropic API, so a small tool (cameo) lets Opus delegate to them as subagents.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude", "Codex" ], "models": [ "Opus 5.5", "Fable 5.1" ], "tools": [ "cameo", "herdr" ], "prompt": "Goal: Use spare quotas on cheaper models without leaving Claude Code.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: cameo, herdr.\nSteps:\n1. Note that many cheap models expose Anthropic-compatible endpoints.\n2. Wrap each one so Claude Code can launch it as a subagent (the author’s cameo, built by Opus in one shot from a short prompt).\n3. Keep your main session on Claude; delegate grunt work to the cheaper subagents.\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: Maple — https://dev.to/maple/using-third-party-models-as-subagents-alongside-claude-in-claude-code-4i38 (summarised from source; the source has no explicit step list)", "steps": [ "Note that many cheap models expose Anthropic-compatible endpoints.", "Wrap each one so Claude Code can launch it as a subagent (the author’s cameo, built by Opus in one shot from a short prompt).", "Keep your main session on Claude; delegate grunt work to the cheaper subagents." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 30.4, "sources": [ { "author": "Maple", "handle": "@maple", "url": "https://dev.to/maple/using-third-party-models-as-subagents-alongside-claude-in-claude-code-4i38", "platform": "devto", "date": "2026-10-03", "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": "agent-fleet-rate-limit-resilience", "url": "https://agentsetups.dev/use-case/agent-fleet-rate-limit-resilience/", "title": "Keep an agent fleet alive through rate limits", "summary": "Classify errors, use jittered backoff with a retry budget, one shared circuit breaker, and checkpoint-and-park instead of crash.", "category": "devops", "category_label": "DevOps", "agents": [ "Claude" ], "models": [], "tools": [ "Python" ], "prompt": "Goal: Stop API rate limits and outages from killing my 24/7 coding agents.\nSetup: agents used in source: Claude; tools/MCPs stated: Python.\nSteps:\n1. Classify errors before retrying (rate limit vs. overload vs. real failure).\n2. Use exponential backoff with full jitter and a retry budget; honour retry-after.\n3. Share one circuit breaker across the fleet so agents don’t all probe a struggling provider.\n4. When a task runs out of budget, write a checkpoint and park it instead of failing.\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-made-my-autonomous-coding-agent-survive-api-rate-limits-and-outages-3912", "steps": [ "Classify errors before retrying (rate limit vs. overload vs. real failure).", "Use exponential backoff with full jitter and a retry budget; honour retry-after.", "Share one circuit breaker across the fleet so agents don’t all probe a struggling provider.", "When a task runs out of budget, write a checkpoint and park it instead of failing." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-06", "trend_score": 29.6, "sources": [ { "author": "yureki_lab", "handle": "@yureki_lab", "url": "https://dev.to/yureki_lab/how-i-made-my-autonomous-coding-agent-survive-api-rate-limits-and-outages-3912", "platform": "devto", "date": "2026-10-06", "primary": true } ] }, { "slug": "do-once-then-script-then-cron", "url": "https://agentsetups.dev/use-case/do-once-then-script-then-cron/", "title": "Turn tasks into cron scripts after doing them once", "summary": "Do a task once with Claude Code next to you, argue until it’s right, then say “turn what we just did into a script” and cron it.", "category": "automation-integrations", "category_label": "Automation & integrations", "agents": [ "Claude" ], "models": [], "tools": [ "cron" ], "prompt": "Goal: Build an AI stack of automations without planning one.\nSetup: agents used in source: Claude; tools/MCPs stated: cron.\nSteps:\n1. Do the task once with Claude Code, arguing until the output is right.\n2. At the end say: “turn what we just did into a script.”\n3. Put the script on a cron: daily, weekly, whatever the task needs.\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 jennings — https://x.com/andrew_jennings/status/2107594359579537634 (summarised from source; the source has no explicit step list)", "steps": [ "Do the task once with Claude Code, arguing until the output is right.", "At the end say: “turn what we just did into a script.”", "Put the script on a cron: daily, weekly, whatever the task needs." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-06", "trend_score": 29.6, "sources": [ { "author": "andrew jennings", "handle": "@andrew_jennings", "url": "https://x.com/andrew_jennings/status/2107594359579537634", "platform": "x", "date": "2026-10-06", "primary": true } ] }, { "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": "codex-revive-old-ios-game", "url": "https://agentsetups.dev/use-case/codex-revive-old-ios-game/", "title": "Revive an old iOS game on web, Watch and Vision Pro", "summary": "A dev brought back a 12-year-old iOS game with Codex and shipped it to the browser, Apple Watch and Vision Pro.", "category": "games", "category_label": "Games", "agents": [ "Codex" ], "models": [], "tools": [ "Apple Watch", "Vision Pro" ], "prompt": "Goal: Bring my old game back on new platforms.\nSetup: agents used in source: Codex; tools/MCPs stated: Apple Watch, Vision Pro.\nSteps:\n1. Point Codex at the old iOS game.\n2. Port it to the browser, Apple Watch and Vision Pro.\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: 大西瓜焚岚 — https://x.com/deadseafu/status/2108028084641558916 (summarised from source; the source has no explicit step list)", "steps": [ "Point Codex at the old iOS game.", "Port it to the browser, Apple Watch and Vision Pro." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 29.5, "sources": [ { "author": "大西瓜焚岚", "handle": "@deadseafu", "url": "https://x.com/deadseafu/status/2108028084641558916", "platform": "x", "date": "2026-10-08", "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": "diff-budget-scope-creep", "url": "https://agentsetups.dev/use-case/diff-budget-scope-creep/", "title": "Cap scope creep with a per-task diff budget", "summary": "Each task declares allowed paths and a size budget; a pre-edit hook blocks out-of-scope writes and a parking lot keeps ideas.", "category": "coding", "category_label": "Coding", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Keep small agent tasks small.\nSetup: agents used in source: Claude.\nSteps:\n1. Every task spec declares a scope block: allowed paths and a diff size budget.\n2. A Claude Code PreToolUse hook blocks edits outside the allowed paths before they land.\n3. A post-run check enforces the size budget inside the allowed directory.\n4. Give the agent a parking lot file to note out-of-scope problems instead of fixing 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: yureki_lab — https://dev.to/yureki_lab/how-i-stopped-my-ai-coding-agents-scope-creep-with-a-diff-budget-47lj", "steps": [ "Every task spec declares a scope block: allowed paths and a diff size budget.", "A Claude Code PreToolUse hook blocks edits outside the allowed paths before they land.", "A post-run check enforces the size budget inside the allowed directory.", "Give the agent a parking lot file to note out-of-scope problems instead of fixing them." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 28.9, "sources": [ { "author": "yureki_lab", "handle": "@yureki_lab", "url": "https://dev.to/yureki_lab/how-i-stopped-my-ai-coding-agents-scope-creep-with-a-diff-budget-47lj", "platform": "devto", "date": "2026-10-03", "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": "replace-paid-push-service", "url": "https://agentsetups.dev/use-case/replace-paid-push-service/", "title": "Replace a newly paid SaaS with your own build", "summary": "When OneSignal’s pricing went to ~$100/month for him, a builder and Codex built their own push-notification service.", "category": "coding", "category_label": "Coding", "agents": [ "Codex" ], "models": [], "tools": [], "prompt": "Goal: Stop paying for a service whose free tier disappeared.\nSetup: agents used in source: Codex.\nSteps:\n1. Ask Codex to assess what you actually use from the service.\n2. Build your own replacement for that subset.\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: Runemir — https://x.com/RunemirQi/status/2106626111182426602 (summarised from source; the source has no explicit step list)", "steps": [ "Ask Codex to assess what you actually use from the service.", "Build your own replacement for that subset." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 28.2, "sources": [ { "author": "Runemir", "handle": "@RunemirQi", "url": "https://x.com/RunemirQi/status/2106626111182426602", "platform": "x", "date": "2026-10-04", "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": "ralph-loop-network-sandbox", "url": "https://agentsetups.dev/use-case/ralph-loop-network-sandbox/", "title": "Sandbox an unattended Claude Code loop", "summary": "ralph-sandbox: internal Docker network with an allowlist proxy, no Docker socket, host-side snapshots, read-only QA agent.", "category": "security", "category_label": "Security", "agents": [ "Claude", "Codex" ], "models": [], "tools": [ "Docker", "git bundle" ], "prompt": "Goal: Run a coding agent with skipped permissions without risking my machine.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Docker, git bundle.\nSteps:\n1. Put the agent in a container on a Docker --internal network; the only way out is an allowlist proxy that tunnels TLS on 443.\n2. Never mount the Docker socket; run as an unprivileged user; keep webhook URLs out and post notifications from the host.\n3. Before each run, snapshot the repo to a hidden git ref plus a git bundle outside the mount.\n4. Run the Ralph loop: same prompt, fresh session, one task per iteration until the PRD is done.\n5. Give the QA agent no edit tools; if Claude hits a usage limit, let Codex take over with its own three attempts.\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: Jean Manzo — https://x.com/jdevmanzo/status/2107865498230706527", "steps": [ "Put the agent in a container on a Docker --internal network; the only way out is an allowlist proxy that tunnels TLS on 443.", "Never mount the Docker socket; run as an unprivileged user; keep webhook URLs out and post notifications from the host.", "Before each run, snapshot the repo to a hidden git ref plus a git bundle outside the mount.", "Run the Ralph loop: same prompt, fresh session, one task per iteration until the PRD is done.", "Give the QA agent no edit tools; if Claude hits a usage limit, let Codex take over with its own three attempts." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 27.3, "sources": [ { "author": "Jean Manzo", "handle": "@jdevmanzo", "url": "https://x.com/jdevmanzo/status/2107865498230706527", "platform": "x", "date": "2026-10-07", "primary": true } ] }, { "slug": "backup-claude-code-setup", "url": "https://agentsetups.dev/use-case/backup-claude-code-setup/", "title": "Back up your whole Claude Code setup to GitHub", "summary": "CLAUDE.md files, skills, hooks, settings and memory go into a private repo, with one install script to restore on a new Mac.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude" ], "models": [], "tools": [ "GitHub" ], "prompt": "Goal: Never lose my agent configuration.\nSetup: agents used in source: Claude; tools/MCPs stated: GitHub.\nSteps:\n1. Collect CLAUDE.md files, skills, hooks, settings and memory into one private GitHub repo.\n2. Write one install script that puts everything back on a new 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: Tejas Kalpande — https://x.com/tejaskalpande/status/2108568392173318432", "steps": [ "Collect CLAUDE.md files, skills, hooks, settings and memory into one private GitHub repo.", "Write one install script that puts everything back on a new machine." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 27.0, "sources": [ { "author": "Tejas Kalpande", "handle": "@tejaskalpande", "url": "https://x.com/tejaskalpande/status/2108568392173318432", "platform": "x", "date": "2026-10-09", "primary": true } ] }, { "slug": "extract-memories-across-harnesses", "url": "https://agentsetups.dev/use-case/extract-memories-across-harnesses/", "title": "Extract your memories from thousands of chats", "summary": "Instead of an agent run, a builder had Opus 5.5 extract memories across Claude, Cursor and Codex chats to stay portable.", "category": "knowledge-memory", "category_label": "Knowledge & memory", "agents": [ "Claude", "Codex", "Cursor" ], "models": [ "Opus 5.5" ], "tools": [], "prompt": "Goal: Keep my memory portable when I switch harnesses often.\nSetup: agents used in source: Claude, Codex, Cursor.\nSteps:\n1. Export chats from Claude, Cursor and Codex.\n2. Have Opus 5.5 extract memories across them (cheaper than an agent loop).\n3. Load the result into whichever harness you use next.\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: shawn — https://x.com/shawnbuilds/status/2107473164641210720 (summarised from source; the source has no explicit step list)", "steps": [ "Export chats from Claude, Cursor and Codex.", "Have Opus 5.5 extract memories across them (cheaper than an agent loop).", "Load the result into whichever harness you use next." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-06", "trend_score": 26.7, "sources": [ { "author": "shawn", "handle": "@shawnbuilds", "url": "https://x.com/shawnbuilds/status/2107473164641210720", "platform": "x", "date": "2026-10-06", "primary": true } ] }, { "slug": "game-while-claude-works", "url": "https://agentsetups.dev/use-case/game-while-claude-works/", "title": "Build a multiplayer mini-game to play while Claude works", "summary": "With Claude Code mods, a builder made an FPS that launches while you wait; other players are people waiting on Claude too.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Use agent wait time for something fun.\nSetup: agents used in source: Claude.\nSteps:\n1. Use Claude Code’s mods to launch a game while the agent works.\n2. Make it multiplayer so other waiting users join; works on Windows too.\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: XHabib — https://x.com/XHabib/status/2106440637004300297 (summarised from source; the source has no explicit step list)", "steps": [ "Use Claude Code’s mods to launch a game while the agent works.", "Make it multiplayer so other waiting users join; works on Windows too." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 26.7, "sources": [ { "author": "XHabib", "handle": "@XHabib", "url": "https://x.com/XHabib/status/2106440637004300297", "platform": "x", "date": "2026-10-03", "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": "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": "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": "grokbot-kids-halloween-game", "url": "https://agentsetups.dev/use-case/grokbot-kids-halloween-game/", "title": "Make a Halloween browser game from one sentence", "summary": "@Frank_AI_Lab gave Grok Bot one sentence; it built a swipe-and-smash game with combos, ghosts, a skull bomb and a pumpkin boss.", "category": "games", "category_label": "Games", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Make a quick browser game for my kids.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Describe the game in one sentence.\n2. Let Grok Bot build it and play it in the browser.\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: Frank — https://x.com/Frank_AI_Lab/status/2108787379276222702 (summarised from source; the source has no explicit step list)", "steps": [ "Describe the game in one sentence.", "Let Grok Bot build it and play it in the browser." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-10", "trend_score": 24.7, "sources": [ { "author": "Frank", "handle": "@Frank_AI_Lab", "url": "https://x.com/Frank_AI_Lab/status/2108787379276222702", "platform": "x", "date": "2026-10-10", "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-in-chrome-woocommerce-redesign", "url": "https://agentsetups.dev/use-case/claude-in-chrome-woocommerce-redesign/", "title": "Redesign a WooCommerce store via Claude in Chrome", "summary": "Claude Code drove Claude in Chrome on a live store: audit, new logo and images, page redesigns, CRO fixes, 1-click checkout.", "category": "marketing-growth", "category_label": "Marketing & growth", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [ "WordPress", "WooCommerce" ], "prompt": "Goal: Redesign and fix an old WordPress + WooCommerce store.\nSetup: agents used in source: Claude; tools/MCPs stated: WordPress, WooCommerce.\nSteps:\n1. Run Claude Code in the terminal and let it call the Claude in Chrome extension on your site (the author worked on live, with no staging; use staging if you can).\n2. Audit: broken images and links, missing SEO tags, slow pages, broken design.\n3. Create and apply a new logo; redesign pages; recreate and replace store images.\n4. CRO: sorting order, bundled products, filters, 1-click checkout instead of 3.\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: HeyNikhila — https://x.com/HeyNikhila/status/2110375208414855526", "steps": [ "Run Claude Code in the terminal and let it call the Claude in Chrome extension on your site (the author worked on live, with no staging; use staging if you can).", "Audit: broken images and links, missing SEO tags, slow pages, broken design.", "Create and apply a new logo; redesign pages; recreate and replace store images.", "CRO: sorting order, bundled products, filters, 1-click checkout instead of 3." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-14", "trend_score": 24.5, "sources": [ { "author": "HeyNikhila", "handle": "@HeyNikhila", "url": "https://x.com/HeyNikhila/status/2110375208414855526", "platform": "x", "date": "2026-10-14", "primary": true } ] }, { "slug": "homelab-kvm-dashboard", "url": "https://agentsetups.dev/use-case/homelab-kvm-dashboard/", "title": "Build one dashboard for all your homelab KVMs", "summary": "Claude Code built a simple dashboard giving quick access to every GL.iNet Comet KVM connected to the lab systems.", "category": "devops", "category_label": "DevOps", "agents": [ "Claude" ], "models": [], "tools": [ "GL.iNet Comet KVM" ], "prompt": "Goal: Manage remote homelab machines from one place.\nSetup: agents used in source: Claude; tools/MCPs stated: GL.iNet Comet KVM.\nSteps:\n1. List the KVM devices and their addresses.\n2. Ask Claude Code to build a simple dashboard linking to each.\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: Dale Hassinger — https://x.com/dalehassinger/status/2109758509969711123 (summarised from source; the source has no explicit step list)", "steps": [ "List the KVM devices and their addresses.", "Ask Claude Code to build a simple dashboard linking to each." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 24.1, "sources": [ { "author": "Dale Hassinger", "handle": "@dalehassinger", "url": "https://x.com/dalehassinger/status/2109758509969711123", "platform": "x", "date": "2026-10-12", "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": "amp-legacy-stack-weekend-features", "url": "https://agentsetups.dev/use-case/amp-legacy-stack-weekend-features/", "title": "Ship features across legacy and mobile stacks with Amp", "summary": "Local runners on a legacy WebForms site, Orbs on a .NET API and React Native app with staging deploys and Expo previews: 12+ features.", "category": "coding", "category_label": "Coding", "agents": [ "Amp" ], "models": [], "tools": [ "WebForms", ".NET", "React Native", "Expo" ], "prompt": "Goal: Ship a backlog across three codebases in one weekend.\nSetup: agents used in source: Amp; tools/MCPs stated: WebForms, .NET, React Native, Expo.\nSteps:\n1. Use Amp locally for the legacy WebForms site.\n2. Use Orbs for the .NET API and React Native app features.\n3. Have the Orbs deploy to staging and send Expo previews to your phone.\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: Alex Heffernan — https://x.com/AlexH2035/status/2106867233825898634", "steps": [ "Use Amp locally for the legacy WebForms site.", "Use Orbs for the .NET API and React Native app features.", "Have the Orbs deploy to staging and send Expo previews to your phone." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 23.8, "sources": [ { "author": "Alex Heffernan", "handle": "@AlexH2035", "url": "https://x.com/AlexH2035/status/2106867233825898634", "platform": "x", "date": "2026-10-04", "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-support-ads-refunds-team", "url": "https://agentsetups.dev/use-case/grokbot-support-ads-refunds-team/", "title": "Have a Grok Bot team handle support and refunds", "summary": "@johnmccoyx’s bots handle support tickets, account fixes, the morning ads report, refund/dispute paperwork and content drafts.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Hand day-to-day operations to bots and keep decisions for myself.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Bots: customer support tickets, account fixes and access issues, an ads report every morning, refund and dispute paperwork, content ideas and drafts.\n2. You: decisions and building.\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 McCoy — https://x.com/johnmccoyx/status/2108012315602034988", "steps": [ "Bots: customer support tickets, account fixes and access issues, an ads report every morning, refund and dispute paperwork, content ideas and drafts.", "You: decisions and building." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 23.7, "sources": [ { "author": "John McCoy", "handle": "@johnmccoyx", "url": "https://x.com/johnmccoyx/status/2108012315602034988", "platform": "x", "date": "2026-10-08", "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": "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": "perplexity-computer-stock-terminal", "url": "https://agentsetups.dev/use-case/perplexity-computer-stock-terminal/", "title": "Build a stock analysis terminal with Perplexity Computer", "summary": "One instruction: a terminal for analysing $NVDA with real-time data from Perplexity Finance; no code written by hand.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Perplexity Computer" ], "models": [], "tools": [ "Perplexity Finance" ], "prompt": "Goal: Get a custom analysis dashboard for one stock.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: Perplexity Finance.\nSteps:\n1. Give Computer one instruction: build a terminal to analyse a ticker using real-time Perplexity Finance data.\n2. Review what it builds.\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: Quant Science — https://x.com/quantscience_/status/2110038128400404559 (summarised from source; the source has no explicit step list)", "steps": [ "Give Computer one instruction: build a terminal to analyse a ticker using real-time Perplexity Finance data.", "Review what it builds." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 23.4, "sources": [ { "author": "Quant Science", "handle": "@quantscience_", "url": "https://x.com/quantscience_/status/2110038128400404559", "platform": "x", "date": "2026-10-13", "primary": true } ] }, { "slug": "content-waterfall-from-one-video", "url": "https://agentsetups.dev/use-case/content-waterfall-from-one-video/", "title": "Turn one weekly video into 20+ posts", "summary": "Claude Code turns one recorded video into LinkedIn/X posts, a newsletter, an X Article and graphics: 300k+ impressions, 109 signups.", "category": "marketing-growth", "category_label": "Marketing & growth", "agents": [ "Claude" ], "models": [], "tools": [ "LinkedIn", "X" ], "prompt": "Goal: Keep up B2B distribution without spending the week on content.\nSetup: agents used in source: Claude; tools/MCPs stated: LinkedIn, X.\nSteps:\n1. Record one video a week.\n2. Have Claude Code turn it into several LinkedIn and X posts, one newsletter, an X Article, and graphics and 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: Tim Scheuer — https://x.com/timscheuer/status/2108543008505319500", "steps": [ "Record one video a week.", "Have Claude Code turn it into several LinkedIn and X posts, one newsletter, an X Article, and graphics and carousels." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 23.4, "sources": [ { "author": "Tim Scheuer", "handle": "@timscheuer", "url": "https://x.com/timscheuer/status/2108543008505319500", "platform": "x", "date": "2026-10-09", "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": "perplexity-computer-weekly-changes", "url": "https://agentsetups.dev/use-case/perplexity-computer-weekly-changes/", "title": "Get a weekly what-changed report with Perplexity Computer", "summary": "@JulianGoldieSEO sets Computer Automations to track a topic weekly and report only what changed, and charts raw numbers.", "category": "research-science", "category_label": "Research & science", "agents": [ "Perplexity Computer" ], "models": [], "tools": [ "Perplexity Computer Automations" ], "prompt": "Goal: Track a topic every week and only see what’s new.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: Perplexity Computer Automations.\nSteps:\n1. Choose something worth tracking (creator topics, community questions).\n2. Set the weekly schedule.\n3. Define the sources it should check.\n4. For metrics, give Computer the spreadsheet, have it chart visits and signups and what changed, then ask for five things to test next.\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: Julian Goldie SEO — https://x.com/JulianGoldieSEO/status/2106773183970095379 (summarised from source; the source has no explicit step list)", "steps": [ "Choose something worth tracking (creator topics, community questions).", "Set the weekly schedule.", "Define the sources it should check.", "For metrics, give Computer the spreadsheet, have it chart visits and signups and what changed, then ask for five things to test next." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 22.2, "sources": [ { "author": "Julian Goldie SEO", "handle": "@JulianGoldieSEO", "url": "https://x.com/JulianGoldieSEO/status/2106773183970095379", "platform": "x", "date": "2026-10-04", "primary": true }, { "author": "Julian Goldie SEO", "handle": "@JulianGoldieSEO", "url": "https://x.com/JulianGoldieSEO/status/2107705558241558775", "platform": "x", "date": "2026-10-07", "primary": false } ] }, { "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": "lovable-frontend-claude-code-backend", "url": "https://agentsetups.dev/use-case/lovable-frontend-claude-code-backend/", "title": "Pair Lovable for v1 UI with Claude Code for the backend", "summary": "A kids’ book app: frontend on Lovable in ~2 weeks, backend almost entirely with Claude Code, so he owns the code afterwards.", "category": "coding", "category_label": "Coding", "agents": [ "Claude" ], "models": [], "tools": [ "Lovable" ], "prompt": "Goal: Ship an app fast without losing ownership of the code.\nSetup: agents used in source: Claude; tools/MCPs stated: Lovable.\nSteps:\n1. Use Lovable to get v1 of the frontend on screen fast.\n2. Build the backend with Claude Code.\n3. Own and maintain the code yourself 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: Shirochenko Dmitriy — https://x.com/dmshirochenko/status/2107024678560616854", "steps": [ "Use Lovable to get v1 of the frontend on screen fast.", "Build the backend with Claude Code.", "Own and maintain the code yourself afterwards." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-05", "trend_score": 21.5, "sources": [ { "author": "Shirochenko Dmitriy", "handle": "@dmshirochenko", "url": "https://x.com/dmshirochenko/status/2107024678560616854", "platform": "x", "date": "2026-10-05", "primary": true } ] }, { "slug": "phone-app-for-all-agent-sessions", "url": "https://agentsetups.dev/use-case/phone-app-for-all-agent-sessions/", "title": "Build your own phone remote for agent sessions", "summary": "Opus 5.5 one-shot an iPhone app connecting to every Claude Code and Codex session on a Mac Studio, across 3 subscriptions.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Claude", "Codex" ], "models": [ "Opus 5.5" ], "tools": [ "iPhone" ], "prompt": "Goal: Control all my desktop agent sessions from my phone.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: iPhone.\nSteps:\n1. Ask the agent to build an iPhone app that connects to every Claude Code and Codex CLI session on your desktop.\n2. Make sessions started from the phone appear back on the desktop.\n3. Organise chats by project (client work, YouTube, newsletter).\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: Pat Simmons — https://x.com/per_simmons_/status/2107570106549071876", "steps": [ "Ask the agent to build an iPhone app that connects to every Claude Code and Codex CLI session on your desktop.", "Make sessions started from the phone appear back on the desktop.", "Organise chats by project (client work, YouTube, newsletter)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-06", "trend_score": 21.1, "sources": [ { "author": "Pat Simmons", "handle": "@per_simmons_", "url": "https://x.com/per_simmons_/status/2107570106549071876", "platform": "x", "date": "2026-10-06", "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 ’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 ’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": "dots-cheaper-utility-plan", "url": "https://agentsetups.dev/use-case/dots-cheaper-utility-plan/", "title": "Have your Dot find a cheaper electricity plan", "summary": "When a renewal email arrived, a Dot suggested other plans based on actual usage, saving $20–40 a month.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [], "prompt": "Goal: Stop auto-renewing utility plans without checking alternatives.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Let the Dot watch your inbox for renewal emails.\n2. When one arrives, have it compare other plans against your actual usage history.\n3. Review and switch if it saves money.\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: Chill Waterson — https://x.com/ChillWaterson/status/2109322448214667530 (summarised from source; the source has no explicit step list)", "steps": [ "Let the Dot watch your inbox for renewal emails.", "When one arrives, have it compare other plans against your actual usage history.", "Review and switch if it saves money." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 20.1, "sources": [ { "author": "Chill Waterson", "handle": "@ChillWaterson", "url": "https://x.com/ChillWaterson/status/2109322448214667530", "platform": "x", "date": "2026-10-11", "primary": true } ] }, { "slug": "cowork-personal-tidy-ups", "url": "https://agentsetups.dev/use-case/cowork-personal-tidy-ups/", "title": "Hand Claude Cowork your small personal tidy-ups", "summary": "@JustinTimeJLew uses Cowork to organise bookmarks and files, make mind maps for his blogs and build grocery lists.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Get time back from small organising chores.\nSetup: agents used in source: Claude.\nSteps:\n1. Ask Cowork to organise your bookmarks.\n2. Have it create a mind map for a blog.\n3. Ask for a grocery list.\n4. Have it organise your files.\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: J Lew the Don 🚀 — https://x.com/JustinTimeJLew/status/2109319425069326723", "steps": [ "Ask Cowork to organise your bookmarks.", "Have it create a mind map for a blog.", "Ask for a grocery list.", "Have it organise your files." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 20.1, "sources": [ { "author": "J Lew the Don 🚀", "handle": "@JustinTimeJLew", "url": "https://x.com/JustinTimeJLew/status/2109319425069326723", "platform": "x", "date": "2026-10-11", "primary": true } ] }, { "slug": "grokbot-cad-part-subscriptions-quotes", "url": "https://agentsetups.dev/use-case/grokbot-cad-part-subscriptions-quotes/", "title": "Let Grok Bot order a part, cut subs and shop insurance", "summary": "In 24h a Grok Bot used Claude Code to design and order a truck bracket, cut $180 of subscriptions and requested 10 quotes.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Claude", "Grok Bot" ], "models": [], "tools": [ "STEP files" ], "prompt": "Goal: Offload a mix of making, money and admin tasks to my bot.\nSetup: agents used in source: Claude, Grok Bot; tools/MCPs stated: STEP files.\nSteps:\n1. Give it a sketch; have it drive Claude Code on your Mac to design the part, build the STEP file, then quote and order it through Xometry.\n2. Have it find and cancel unused subscriptions, and review charges periodically.\n3. Have it request home and auto insurance renewal quotes from ~10 agents by email, every year.\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: Jubbs — https://x.com/JUBBAMAYNE/status/2108036870257144089", "steps": [ "Give it a sketch; have it drive Claude Code on your Mac to design the part, build the STEP file, then quote and order it through Xometry.", "Have it find and cancel unused subscriptions, and review charges periodically.", "Have it request home and auto insurance renewal quotes from ~10 agents by email, every year." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 19.5, "sources": [ { "author": "Jubbs", "handle": "@JUBBAMAYNE", "url": "https://x.com/JUBBAMAYNE/status/2108036870257144089", "platform": "x", "date": "2026-10-08", "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": "grokbot-cold-email-two-bots", "url": "https://agentsetups.dev/use-case/grokbot-cold-email-two-bots/", "title": "Set up cold email with two Grok Bots and Instantly", "summary": "Bot 1 set up domain, Workspace and email auth; bot 2 researched Toronto businesses with weak sites; 23 leads ready.", "category": "sales-outreach", "category_label": "Sales & outreach", "agents": [ "Grok Bot" ], "models": [], "tools": [ "Google Workspace", "Instantly" ], "prompt": "Goal: Land one new client a month with researched, personalised cold email.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Google Workspace, Instantly.\nSteps:\n1. Bot 1: buy a separate outreach domain, set up Google Workspace, configure email authentication and connect Instantly.\n2. Bot 2: research local small businesses with outdated sites, weak stores or no site; find contact emails and improvement opportunities; log it all in a spreadsheet.\n3. Bot 1 drafts personalised emails from that research.\n4. You review and approve; Instantly sends and follows up. Warm the inbox before sending 20–30 a day.\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: Dre Voudouris — https://x.com/drevoudouriss/status/2110418743272603919", "steps": [ "Bot 1: buy a separate outreach domain, set up Google Workspace, configure email authentication and connect Instantly.", "Bot 2: research local small businesses with outdated sites, weak stores or no site; find contact emails and improvement opportunities; log it all in a spreadsheet.", "Bot 1 drafts personalised emails from that research.", "You review and approve; Instantly sends and follows up. Warm the inbox before sending 20–30 a day." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-14", "trend_score": 19.1, "sources": [ { "author": "Dre Voudouris", "handle": "@drevoudouriss", "url": "https://x.com/drevoudouriss/status/2110418743272603919", "platform": "x", "date": "2026-10-14", "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": "instinct-weekly-small-business-help", "url": "https://agentsetups.dev/use-case/instinct-weekly-small-business-help/", "title": "Text Instinct your weekly small-business chores", "summary": "One user’s Instinct scheduled X posts overnight, audited her website, drafted Reddit posts and found homeschool field trips.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Instinct" ], "models": [], "tools": [], "prompt": "Goal: Hand off a week of small chores by text.\nSetup: agents used in source: Instinct.\nSteps:\n1. Text the agent the chores.\n2. Examples: schedule social posts overnight, audit your website, draft Reddit posts, find homeschool field trips.\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: Home Sweet Alabama — https://x.com/ourhomeswtbama/status/2105823076172849520", "steps": [ "Text the agent the chores.", "Examples: schedule social posts overnight, audit your website, draft Reddit posts, find homeschool field trips." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 18.2, "sources": [ { "author": "Home Sweet Alabama", "handle": "@ourhomeswtbama", "url": "https://x.com/ourhomeswtbama/status/2105823076172849520", "platform": "x", "date": "2026-10-02", "primary": true } ] }, { "slug": "grokbot-physics-game-for-kids", "url": "https://agentsetups.dev/use-case/grokbot-physics-game-for-kids/", "title": "Explain a science question with a Grok Bot game", "summary": "Asked why a straw looks bent in water, Grok Bot built a 3D archerfish game in one HTML file that learns Snell’s law.", "category": "education", "category_label": "Education", "agents": [ "Grok Bot" ], "models": [], "tools": [ "HTML" ], "prompt": "Goal: Help my kids understand refraction.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: HTML.\nSteps:\n1. Ask Grok Bot the kids’ question.\n2. Ask for a playable explanation; it built a single-file 3D game where an archerfish misses, learns that water bends light (n = 1.33), aims 7.2° lower and hits.\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: Frank — https://x.com/Frank_AI_Lab/status/2105898453893009485", "steps": [ "Ask Grok Bot the kids’ question.", "Ask for a playable explanation; it built a single-file 3D game where an archerfish misses, learns that water bends light (n = 1.33), aims 7.2° lower and hits." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 18.2, "sources": [ { "author": "Frank", "handle": "@Frank_AI_Lab", "url": "https://x.com/Frank_AI_Lab/status/2105898453893009485", "platform": "x", "date": "2026-10-02", "primary": true } ] }, { "slug": "grokbot-deconflict-meetings", "url": "https://agentsetups.dev/use-case/grokbot-deconflict-meetings/", "title": "Let Grok Bot spot and fix double-booked meetings", "summary": "@abbyfinan’s Grok Bot flagged two conflicting customer meetings with a rundown of each, then rescheduled one.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Catch calendar conflicts before they bite.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Connect your calendar.\n2. When it flags a conflict, read its rundown (what each meeting is, who it’s with).\n3. Ask it to deconflict; it reschedules one.\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: abby finan — https://x.com/abbyfinan/status/2105772495823577359", "steps": [ "Connect your calendar.", "When it flags a conflict, read its rundown (what each meeting is, who it’s with).", "Ask it to deconflict; it reschedules one." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 18.0, "sources": [ { "author": "abby finan", "handle": "@abbyfinan", "url": "https://x.com/abbyfinan/status/2105772495823577359", "platform": "x", "date": "2026-10-01", "primary": true } ] }, { "slug": "dots-overnight-surprise-me", "url": "https://agentsetups.dev/use-case/dots-overnight-surprise-me/", "title": "Give your Dot an overnight brief with spending rules", "summary": "“Surprise me by morning,” no spending, don’t touch existing projects: 3 GitHub projects, an audited draft PR, 193 tests passed.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [ "GitHub", "Blender" ], "prompt": "Goal: See what my Dot can do unsupervised overnight.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: GitHub, Blender.\nSteps:\n1. Set the rules: spend nothing, leave existing projects alone, work all night.\n2. Say “Surprise me by morning.”\n3. Handle sign-in and permission approvals when it asks.\n4. In the morning, review the work (here 3 new GitHub projects, an independently audited draft PR, 193 targeted tests passed, 3 DevRel applications).\n5. Optional: have it visualise the night’s work (he got a Blender city).\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 Jha — https://x.com/jhahimanshu653/status/2105521799178137706", "steps": [ "Set the rules: spend nothing, leave existing projects alone, work all night.", "Say “Surprise me by morning.”", "Handle sign-in and permission approvals when it asks.", "In the morning, review the work (here 3 new GitHub projects, an independently audited draft PR, 193 targeted tests passed, 3 DevRel applications).", "Optional: have it visualise the night’s work (he got a Blender city)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 18.0, "sources": [ { "author": "Himanshu Jha", "handle": "@jhahimanshu653", "url": "https://x.com/jhahimanshu653/status/2105521799178137706", "platform": "x", "date": "2026-10-01", "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": "perplexity-computer-light-effort-builds", "url": "https://agentsetups.dev/use-case/perplexity-computer-light-effort-builds/", "title": "Build the rough version on Light effort to save credits", "summary": "Perplexity Computer built a playable flight simulator for 97 credits on Light; scale effort up only once the idea works.", "category": "coding", "category_label": "Coding", "agents": [ "Perplexity Computer" ], "models": [], "tools": [], "prompt": "Goal: Prototype with Perplexity Computer without burning credits.\nSetup: agents used in source: Perplexity Computer.\nSteps:\n1. Use the effort slider: start on Light (smaller models, much cheaper).\n2. Build the rough version first; turn effort up only once the idea works.\n3. Use Mac app tabs to research in one tab while another builds.\n4. Ask for single-file HTML outputs (e.g. an SEO calculator, a landing page) and open them in the browser.\n5. Read your prompt twice; credits don’t come 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: Julian Goldie SEO — https://x.com/JulianGoldieSEO/status/2108176289886773738", "steps": [ "Use the effort slider: start on Light (smaller models, much cheaper).", "Build the rough version first; turn effort up only once the idea works.", "Use Mac app tabs to research in one tab while another builds.", "Ask for single-file HTML outputs (e.g. an SEO calculator, a landing page) and open them in the browser.", "Read your prompt twice; credits don’t come back." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 17.8, "sources": [ { "author": "Julian Goldie SEO", "handle": "@JulianGoldieSEO", "url": "https://x.com/JulianGoldieSEO/status/2108176289886773738", "platform": "x", "date": "2026-10-08", "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": "dots-mcp-events-notify", "url": "https://agentsetups.dev/use-case/dots-mcp-events-notify/", "title": "Notify your Dot when your app’s data changes", "summary": "@itsJaimeMedina added MCP Events to his app’s MCP server; the Dot watched a contact and pinged him when it changed.", "category": "automation-integrations", "category_label": "Automation & integrations", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [ "MCP", "Docker" ], "prompt": "Goal: Let my Dot react to events in my own app instead of polling.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: MCP, Docker.\nSteps:\n1. Add events to your app’s MCP server.\n2. Run a sender (here in Docker) that delivers events to ChatGPT.\n3. Ask your Dot to watch something (e.g. a contact’s company name), change it in the app and confirm you get a notification.\n4. Extend it: a failed job triggers a log review, a finished build triggers a check and 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: Jaime Medina — https://x.com/itsJaimeMedina/status/2110073711684632616", "steps": [ "Add events to your app’s MCP server.", "Run a sender (here in Docker) that delivers events to ChatGPT.", "Ask your Dot to watch something (e.g. a contact’s company name), change it in the app and confirm you get a notification.", "Extend it: a failed job triggers a log review, a finished build triggers a check and summary." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 16.9, "sources": [ { "author": "Jaime Medina", "handle": "@itsJaimeMedina", "url": "https://x.com/itsJaimeMedina/status/2110073711684632616", "platform": "x", "date": "2026-10-13", "primary": true } ] }, { "slug": "dots-hourly-email-weekly-billing", "url": "https://agentsetups.dev/use-case/dots-hourly-email-weekly-billing/", "title": "Schedule your Dot to check email and billing claims", "summary": "A setup video: the Dot checks email every hour and reviews billing claims every Friday, reporting back in one chat.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [], "prompt": "Goal: Put my Dot on a recurring schedule for inbox and billing checks.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Set an hourly schedule for the Dot to check email.\n2. Set a weekly (Friday) task to review billing claims.\n3. Have both report back in a single chat.\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: Dylan Normandin — https://x.com/DNormandin1234/status/2109373745081077971 (summarised from source; the source has no explicit step list)", "steps": [ "Set an hourly schedule for the Dot to check email.", "Set a weekly (Friday) task to review billing claims.", "Have both report back in a single chat." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 16.5, "sources": [ { "author": "Dylan Normandin", "handle": "@DNormandin1234", "url": "https://x.com/DNormandin1234/status/2109373745081077971", "platform": "x", "date": "2026-10-11", "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": "grokbot-stealable-routines", "url": "https://agentsetups.dev/use-case/grokbot-stealable-routines/", "title": "Run four Grok Bot routines, including a bot that checks bots", "summary": "Midnight: one bot checks the others and suggests fixes; 8am weekdays inbox triage (advice only); daily LinkedIn post; Monday review.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Grok Bot" ], "models": [], "tools": [ "LinkedIn" ], "prompt": "Goal: Set up a small routine system with Grok Bot.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: LinkedIn.\nSteps:\n1. Midnight: one bot checks your other bots and suggests fixes.\n2. 08:00 weekdays: inbox triage, advice only.\n3. Every morning: your LinkedIn post goes out.\n4. Mondays: weekly review of last week’s posts.\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: Eyad Kelleh — https://x.com/KellehEyad/status/2108505265880371670", "steps": [ "Midnight: one bot checks your other bots and suggests fixes.", "08:00 weekdays: inbox triage, advice only.", "Every morning: your LinkedIn post goes out.", "Mondays: weekly review of last week’s posts." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 16.1, "sources": [ { "author": "Eyad Kelleh", "handle": "@KellehEyad", "url": "https://x.com/KellehEyad/status/2108505265880371670", "platform": "x", "date": "2026-10-09", "primary": true } ] }, { "slug": "grokbot-runs-fantasy-football", "url": "https://agentsetups.dev/use-case/grokbot-runs-fantasy-football/", "title": "Hand your fantasy football team to Grok Bot", "summary": "It drafted live, sets the lineup each morning, files waivers, swaps injured players before kickoff and only messages on changes.", "category": "personal-life", "category_label": "Personal life", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Manage my fantasy team without opening the app.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Have Grok Bot draft live for you.\n2. Each morning it sets the lineup and files waivers.\n3. Before kickoff it swaps out injured players.\n4. It only messages you when something 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: Dean Young — https://x.com/Dean_Y0ung/status/2108036174417965538", "steps": [ "Have Grok Bot draft live for you.", "Each morning it sets the lineup and files waivers.", "Before kickoff it swaps out injured players.", "It only messages you when something changes." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 15.9, "sources": [ { "author": "Dean Young", "handle": "@Dean_Y0ung", "url": "https://x.com/Dean_Y0ung/status/2108036174417965538", "platform": "x", "date": "2026-10-08", "primary": true } ] }, { "slug": "grokbot-landlord-lease-signing", "url": "https://agentsetups.dev/use-case/grokbot-landlord-lease-signing/", "title": "Have Grok Bot draft and send a lease for signing", "summary": "Grok Bot logged into a rental-management site, drafted a lease with the requested terms, and both tenants signed it overnight.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Grok Bot" ], "models": [], "tools": [ "rental management website", "email" ], "prompt": "Goal: Handle a rental lease without a property manager.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: rental management website, email.\nSteps:\n1. Give Grok Bot the lease terms in a prompt.\n2. Let it log into your rental-management website and generate the agreement with signature boxes.\n3. Have it email it to the tenants with a friendly message (it can schedule the send).\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: Joseph R. Nosef — https://x.com/jrnosef/status/2110567718734709023", "steps": [ "Give Grok Bot the lease terms in a prompt.", "Let it log into your rental-management website and generate the agreement with signature boxes.", "Have it email it to the tenants with a friendly message (it can schedule the send)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 14.9, "sources": [ { "author": "Joseph R. Nosef", "handle": "@jrnosef", "url": "https://x.com/jrnosef/status/2110567718734709023", "platform": "x", "date": "2026-10-15", "primary": true } ] }, { "slug": "grokbot-review-seller-disclosures", "url": "https://agentsetups.dev/use-case/grokbot-review-seller-disclosures/", "title": "Give Grok Bot the seller disclosures first", "summary": "A Bay Area house hunter gives Grok Bot each seller-disclosure packet first; he says it finds more than his agent and lawyer.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Catch issues in a home’s disclosure documents early.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Upload the seller disclosures to your bot before anything else.\n2. Ask it to flag issues, then take its findings to your agent or lawyer.\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 — https://x.com/thecsguy/status/2110586525427876259 (summarised from source; the source has no explicit step list)", "steps": [ "Upload the seller disclosures to your bot before anything else.", "Ask it to flag issues, then take its findings to your agent or lawyer." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 14.9, "sources": [ { "author": "nick", "handle": "@thecsguy", "url": "https://x.com/thecsguy/status/2110586525427876259", "platform": "x", "date": "2026-10-15", "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": "cowork-research-with-folder-and-chrome", "url": "https://agentsetups.dev/use-case/cowork-research-with-folder-and-chrome/", "title": "Do research with Claude Cowork driving data portals", "summary": "Link a real folder, let Cowork drive Chrome to pull MAST and ExoFOP data, and give it computer access to run the analysis.", "category": "research-science", "category_label": "Research & science", "agents": [ "Claude" ], "models": [], "tools": [ "Chrome", "MAST", "ExoFOP" ], "prompt": "Goal: Run an astronomy research project with Claude Cowork.\nSetup: agents used in source: Claude; tools/MCPs stated: Chrome, MAST, ExoFOP.\nSteps:\n1. Link a real project folder on your PC to Cowork.\n2. Let it drive Chrome to fetch data from archives (MAST, ExoFOP).\n3. Give it computer access to run the analysis code.\n4. Talk to it like a coworker, or hand it a /goal.\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: samsonfraser — https://x.com/samsonfraser_/status/2108580741873561993 (summarised from source; the source has no explicit step list)", "steps": [ "Link a real project folder on your PC to Cowork.", "Let it drive Chrome to fetch data from archives (MAST, ExoFOP).", "Give it computer access to run the analysis code.", "Talk to it like a coworker, or hand it a /goal." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 13.8, "sources": [ { "author": "samsonfraser", "handle": "@samsonfraser_", "url": "https://x.com/samsonfraser_/status/2108580741873561993", "platform": "x", "date": "2026-10-09", "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": "opencode-reviews-dictated-daily-note", "url": "https://agentsetups.dev/use-case/opencode-reviews-dictated-daily-note/", "title": "Ramble into a daily note, let OpenCode make sense of it", "summary": "Dictate unfiltered thoughts into an Obsidian daily note all day; each evening OpenCode extracts tasks, summarises and sets goals.", "category": "knowledge-memory", "category_label": "Knowledge & memory", "agents": [ "OpenCode" ], "models": [], "tools": [ "Obsidian" ], "prompt": "Goal: Get the benefit of time tracking without the tracking.\nSetup: agents used in source: OpenCode; tools/MCPs stated: Obsidian.\nSteps:\n1. Through the day, dictate whatever you are doing or thinking into your Obsidian daily note.\n2. At the end of each day, have OpenCode read the daily note from the vault.\n3. Have it extract tasks, summarise your thoughts and set goals for tomorrow.\n4. Over weeks, use the notes to build a personal charter or a tag-based heatmap of your time.\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/Billy-Fong-2007 — https://www.reddit.com/r/ObsidianMD/comments/1x5k75t/rambling_into_obsidian_daily_note_is_the_best/", "steps": [ "Through the day, dictate whatever you are doing or thinking into your Obsidian daily note.", "At the end of each day, have OpenCode read the daily note from the vault.", "Have it extract tasks, summarise your thoughts and set goals for tomorrow.", "Over weeks, use the notes to build a personal charter or a tag-based heatmap of your time." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-14", "trend_score": 13.6, "sources": [ { "author": "/u/Billy-Fong-2007", "handle": "/u/Billy-Fong-2007", "url": "https://www.reddit.com/r/ObsidianMD/comments/1x5k75t/rambling_into_obsidian_daily_note_is_the_best/", "platform": "reddit", "date": "2026-10-14", "primary": true } ] }, { "slug": "claude-patches-1991-dos-game", "url": "https://agentsetups.dev/use-case/claude-patches-1991-dos-game/", "title": "Have Claude patch an old game that won’t run", "summary": "Given the 1991 game’s binaries and the symptoms, Claude disassembled it, found a sound-card handshake that hangs, and wrote a 3-byte patch.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [], "tools": [ "FreeDOS" ], "prompt": "Goal: Get a retro game running on real old hardware.\nSetup: agents used in source: Claude; tools/MCPs stated: FreeDOS.\nSteps:\n1. Give Claude the original binaries and a description of the problem.\n2. Let it disassemble the executable, trace execution and identify the likely root cause.\n3. Have it apply the patch to a new copy (keep the original) and test on the real 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: /u/jrowberg — https://www.reddit.com/r/ClaudeAI/comments/1x06hmp/claude_fixed_a_bug_in_a_dos_game_from_1991_and/", "steps": [ "Give Claude the original binaries and a description of the problem.", "Let it disassemble the executable, trace execution and identify the likely root cause.", "Have it apply the patch to a new copy (keep the original) and test on the real machine." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 13.5, "sources": [ { "author": "/u/jrowberg", "handle": "/u/jrowberg", "url": "https://www.reddit.com/r/ClaudeAI/comments/1x06hmp/claude_fixed_a_bug_in_a_dos_game_from_1991_and/", "platform": "reddit", "date": "2026-10-07", "primary": true } ] }, { "slug": "pixel-dungeon-agent-monitor", "url": "https://agentsetups.dev/use-case/pixel-dungeon-agent-monitor/", "title": "Watch all your coding agents in one pixel-art dungeon", "summary": "Each Claude Code, Codex, Kiro or Gemini CLI session is a hero in its project’s room; click to see the console and answer prompts.", "category": "coding", "category_label": "Coding", "agents": [ "Claude", "Codex", "Kiro", "Gemini CLI" ], "models": [], "tools": [ "Herdr" ], "prompt": "Goal: See at a glance which of my agents is waiting for me.\nSetup: agents used in source: Claude, Codex, Kiro, Gemini CLI; tools/MCPs stated: Herdr.\nSteps:\n1. Run your agents through Herdr so the app can listen to their events (or use the read-only fallback).\n2. Give each project a room and each harness its own hero.\n3. Click a room to see the live console, answer a prompt or permission request, or stop the agent.\n4. Open the full-screen view for changed files, diffs and the branch’s 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/NachoV125 — https://www.reddit.com/r/LLMDevs/comments/1x58qog/i_made_a_pixelart_dungeon_to_keep_an_eye_on_all/", "steps": [ "Run your agents through Herdr so the app can listen to their events (or use the read-only fallback).", "Give each project a room and each harness its own hero.", "Click a room to see the live console, answer a prompt or permission request, or stop the agent.", "Open the full-screen view for changed files, diffs and the branch’s PR." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 13.3, "sources": [ { "author": "/u/NachoV125", "handle": "/u/NachoV125", "url": "https://www.reddit.com/r/LLMDevs/comments/1x58qog/i_made_a_pixelart_dungeon_to_keep_an_eye_on_all/", "platform": "reddit", "date": "2026-10-13", "primary": true } ] }, { "slug": "grokbot-printed-morning-paper", "url": "https://agentsetups.dev/use-case/grokbot-printed-morning-paper/", "title": "Get a printed personal morning paper from Grok Bot", "summary": "Users have Grok Bot research and print a daily paper (appointments, weather, chosen headlines) or a commute audio brief.", "category": "personal-life", "category_label": "Personal life", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Start the day with a briefing without staring at a screen.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Tell Grok Bot what to include: your appointments, the weather, the headlines you care about.\n2. Have it research and write it every morning.\n3. Have it print it (or deliver audio for your commute).\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 Lee — https://x.com/tamerton/status/2107753044729352358 (summarised from source; the source has no explicit step list)", "steps": [ "Tell Grok Bot what to include: your appointments, the weather, the headlines you care about.", "Have it research and write it every morning.", "Have it print it (or deliver audio for your commute)." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 13.2, "sources": [ { "author": "Michael Lee", "handle": "@tamerton", "url": "https://x.com/tamerton/status/2107753044729352358", "platform": "x", "date": "2026-10-07", "primary": true }, { "author": "T K", "handle": "@TKozzer", "url": "https://x.com/TKozzer/status/2108565838961705202", "platform": "x", "date": "2026-10-09", "primary": false }, { "author": "Padjen", "handle": "@padjen", "url": "https://x.com/padjen/status/2107390788351172934", "platform": "x", "date": "2026-10-06", "primary": false } ] }, { "slug": "chatgpt-agent-comedy-show-alerts", "url": "https://agentsetups.dev/use-case/chatgpt-agent-comedy-show-alerts/", "title": "Get alerted to surprise comedy shows with ChatGPT agent", "summary": "After missing a surprise show, a fan built a ChatGPT agent that checks ticket sites hourly and sends push + email alerts.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT agent" ], "models": [], "tools": [], "prompt": "Goal: Never miss a surprise show by a favourite comedian again.\nSetup: agents used in source: ChatGPT agent.\nSteps:\n1. Have the agent check ticket sites and comedy clubs every hour.\n2. Send push and email alerts when a new show appears.\n3. Run it 24/7 in the cloud, not on your laptop.\n4. Add a weekly health check so you know it’s still working.\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 Moseley — https://x.com/bmose14/status/2109293515217990112", "steps": [ "Have the agent check ticket sites and comedy clubs every hour.", "Send push and email alerts when a new show appears.", "Run it 24/7 in the cloud, not on your laptop.", "Add a weekly health check so you know it’s still working." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 12.8, "sources": [ { "author": "Brian Moseley", "handle": "@bmose14", "url": "https://x.com/bmose14/status/2109293515217990112", "platform": "x", "date": "2026-10-11", "primary": true } ] }, { "slug": "minecraft-mod-claude-builds", "url": "https://agentsetups.dev/use-case/minecraft-mod-claude-builds/", "title": "Have Claude Code build in Minecraft as you play", "summary": "Press K, describe a build (“a medieval castle with a moat”) and a mod drives your own Claude Code through 20 in-game tools; one click…", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [], "tools": [ "Minecraft Java", "Fabric/Forge/NeoForge" ], "prompt": "Goal: Build big structures in Minecraft by describing them.\nSetup: agents used in source: Claude; tools/MCPs stated: Minecraft Java, Fabric/Forge/NeoForge.\nSteps:\n1. Install Claude Code (Pro or Max) plus Minecraft Java and the free mod jar.\n2. In game, press K and describe what you want built.\n3. Keep playing while it builds through the mod’s in-game tools; undo with one click if you don’t like 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.\nNote: Beta; the author’s biggest timed build was a 34k-block castle in about 15 minutes.\nBased on: /u/DutyOnly4308 — https://www.reddit.com/r/ClaudeAI/comments/1x3olix/i_made_a_free_minecraft_mod_where_claude_builds/", "steps": [ "Install Claude Code (Pro or Max) plus Minecraft Java and the free mod jar.", "In game, press K and describe what you want built.", "Keep playing while it builds through the mod’s in-game tools; undo with one click if you don’t like it." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 12.8, "sources": [ { "author": "/u/DutyOnly4308", "handle": "/u/DutyOnly4308", "url": "https://www.reddit.com/r/ClaudeAI/comments/1x3olix/i_made_a_free_minecraft_mod_where_claude_builds/", "platform": "reddit", "date": "2026-10-12", "primary": true } ] }, { "slug": "hermes-self-maintaining-config", "url": "https://agentsetups.dev/use-case/hermes-self-maintaining-config/", "title": "Keep a Hermes agent from rotting for six months", "summary": "Tiny memory file, an Obsidian reference vault, scheduled skill pruning, a nightly dream loop and LLM-free daily backups.", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "Hermes Agent" ], "models": [], "tools": [ "Obsidian", "cron", "SQLite" ], "prompt": "Goal: Run one long-lived agent without starting fresh every few weeks.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: Obsidian, cron, SQLite.\nSteps:\n1. Keep the memory file at the default tiny size; first line: “Memory = only facts relevant to all conversations. Everything else → vault/skills.”\n2. Keep an indexed reference/ folder in an Obsidian vault (one doc per system) as the shared source of truth; offload to it when memory hits ~75%.\n3. Schedule skill pruning; deletions must declare what absorbed the content, pinned skills can be patched but not deleted.\n4. Run a nightly dream job with a restricted toolset: review the day’s sessions, self-critique, write a dream log and insights file, audit skills, triage memory.\n5. Back up daily/weekly/monthly with a no-agent cron script: WAL checkpoint before copying SQLite, verify integrity, include restore instructions.\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/ct06033 — https://www.reddit.com/r/hermesagent/comments/1x24qfp/my_hermes_configuration_that_works_for_me/", "steps": [ "Keep the memory file at the default tiny size; first line: “Memory = only facts relevant to all conversations. Everything else → vault/skills.”", "Keep an indexed reference/ folder in an Obsidian vault (one doc per system) as the shared source of truth; offload to it when memory hits ~75%.", "Schedule skill pruning; deletions must declare what absorbed the content, pinned skills can be patched but not deleted.", "Run a nightly dream job with a restricted toolset: review the day’s sessions, self-critique, write a dream log and insights file, audit skills, triage memory.", "Back up daily/weekly/monthly with a no-agent cron script: WAL checkpoint before copying SQLite, verify integrity, include restore instructions." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-10", "trend_score": 12.7, "sources": [ { "author": "/u/ct06033", "handle": "/u/ct06033", "url": "https://www.reddit.com/r/hermesagent/comments/1x24qfp/my_hermes_configuration_that_works_for_me/", "platform": "reddit", "date": "2026-10-10", "primary": true } ] }, { "slug": "claude-code-24-7-pixel-news-network", "url": "https://agentsetups.dev/use-case/claude-code-24-7-pixel-news-network/", "title": "Build a 24/7 AI news channel with fact checks", "summary": "Claude Code built a pixel-art news network: scripted segments from ~70 feeds, numbers checked against source data, and a token budget.", "category": "content-video", "category_label": "Content & video", "agents": [ "Claude" ], "models": [ "Opus 5.5", "Haiku", "Sonnet" ], "tools": [ "Suno" ], "prompt": "Goal: Run an always-on AI broadcast that doesn’t make things up about real people.\nSetup: agents used in source: Claude; tools/MCPs stated: Suno.\nSteps:\n1. Have the model write every segment as a structured script; voice, time and place each line in one shared broadcast timeline.\n2. Check every price, number or statistic against the data the model was given; rewrite or kill lines that don’t match.\n3. Keep a sourced research library and have another agent fact-check facts before they are added.\n4. Put a budget around it: nothing gets written if nobody is watching; use a cheap model for routine dialogue.\n5. Run automated checks before every 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: /u/Icy_Upstairs_7328 — https://www.reddit.com/r/ClaudeCode/comments/1wvkje5/hey_opus_55_can_you_build_me_a_news_network_that/", "steps": [ "Have the model write every segment as a structured script; voice, time and place each line in one shared broadcast timeline.", "Check every price, number or statistic against the data the model was given; rewrite or kill lines that don’t match.", "Keep a sourced research library and have another agent fact-check facts before they are added.", "Put a budget around it: nothing gets written if nobody is watching; use a cheap model for routine dialogue.", "Run automated checks before every push." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 12.2, "sources": [ { "author": "/u/Icy_Upstairs_7328", "handle": "/u/Icy_Upstairs_7328", "url": "https://www.reddit.com/r/ClaudeCode/comments/1wvkje5/hey_opus_55_can_you_build_me_a_news_network_that/", "platform": "reddit", "date": "2026-10-02", "primary": true } ] }, { "slug": "n8n-invoice-inbox-to-sheet", "url": "https://agentsetups.dev/use-case/n8n-invoice-inbox-to-sheet/", "title": "Auto-log every emailed invoice into a sheet", "summary": "Watches a billing@ inbox, classifies and extracts invoice fields in one call, dedupes on invoice number, logs to Sheets and pings Telegram.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "n8n" ], "models": [], "tools": [ "Gmail", "Google Sheets", "Telegram" ], "prompt": "Goal: Never type an invoice into a spreadsheet again at tax time.\nSetup: agents used in source: n8n; tools/MCPs stated: Gmail, Google Sheets, Telegram.\nSteps:\n1. Point the workflow at one billing@ address and forward invoices from other addresses there.\n2. Watch Gmail for unread emails with attachments and filter out junk files.\n3. Classify “is this an invoice?” and extract the fields in the same call.\n4. Look the invoice number up in the sheet before appending, so re-sends never create duplicates.\n5. Append new invoices to Google Sheets and send a Telegram alert for each.\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/easybits_ai — https://www.reddit.com/r/n8n/comments/1wuxey9/tax_season_is_coming_the_n8n_workflow_i_built_to/", "steps": [ "Point the workflow at one billing@ address and forward invoices from other addresses there.", "Watch Gmail for unread emails with attachments and filter out junk files.", "Classify “is this an invoice?” and extract the fields in the same call.", "Look the invoice number up in the sheet before appending, so re-sends never create duplicates.", "Append new invoices to Google Sheets and send a Telegram alert for each." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 12.1, "sources": [ { "author": "/u/easybits_ai", "handle": "/u/easybits_ai", "url": "https://www.reddit.com/r/n8n/comments/1wuxey9/tax_season_is_coming_the_n8n_workflow_i_built_to/", "platform": "reddit", "date": "2026-10-01", "primary": true } ] }, { "slug": "claude-bubblegum-pop-music-video", "url": "https://agentsetups.dev/use-case/claude-bubblegum-pop-music-video/", "title": "Make a music video with Claude, Suno and Remotion", "summary": "Claude polished the lyrics and style, Suno made the song, and Opus built the video in Remotion plus an app to fix word timings by hand.", "category": "content-video", "category_label": "Content & video", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [ "Suno", "Remotion" ], "prompt": "Goal: Make a finished music video in a couple of days.\nSetup: agents used in source: Claude; tools/MCPs stated: Suno, Remotion.\nSteps:\n1. Write rough lyrics and the vibe; have Claude turn them into real lyrics and pick a style.\n2. Generate the song in Suno (here about 20 generations).\n3. Have Opus build the video in JS with Remotion.\n4. When timings are off, have it build a small app so you can adjust word and beat timings by hand.\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/pizzaisprettyneato — https://www.reddit.com/r/vibecoding/comments/1x4agp8/i_had_claude_make_a_bubblegum_pop_music_video/", "steps": [ "Write rough lyrics and the vibe; have Claude turn them into real lyrics and pick a style.", "Generate the song in Suno (here about 20 generations).", "Have Opus build the video in JS with Remotion.", "When timings are off, have it build a small app so you can adjust word and beat timings by hand." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 11.9, "sources": [ { "author": "/u/pizzaisprettyneato", "handle": "/u/pizzaisprettyneato", "url": "https://www.reddit.com/r/vibecoding/comments/1x4agp8/i_had_claude_make_a_bubblegum_pop_music_video/", "platform": "reddit", "date": "2026-10-12", "primary": true } ] }, { "slug": "n8n-czech-investment-tax-bot", "url": "https://agentsetups.dev/use-case/n8n-czech-investment-tax-bot/", "title": "Calculate your investment taxes from broker CSVs", "summary": "Send a broker CSV to a Telegram bot; n8n matches lots FIFO, applies the Czech 3-year rule with ČNB rates and answers /sell, /report.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "n8n" ], "models": [], "tools": [ "Telegram", "n8n Data Tables" ], "prompt": "Goal: Know the tax impact of a sale before I make it.\nSetup: agents used in source: n8n; tools/MCPs stated: Telegram, n8n Data Tables.\nSteps:\n1. Send the broker CSV (Trading 212 or IBKR) to a Telegram bot backed by self-hosted n8n.\n2. On import, check for duplicate files and overlapping statement periods, then parse the broker format.\n3. Match every sell to buy lots FIFO, run the 3-year test per lot, convert at the ČNB rate of the day (cached).\n4. Write results only at the very end so a failed run writes nothing.\n5. Use commands: /sell for a planned sale, /report for the year, /dap for tax-return grouping, /export for evidence.\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: Not tax advice; the author’s own tool.\nBased on: /u/MiveClor — https://www.reddit.com/r/n8n/comments/1x52mx6/i_built_a_telegram_bot_in_n8n_that_calculates_my/", "steps": [ "Send the broker CSV (Trading 212 or IBKR) to a Telegram bot backed by self-hosted n8n.", "On import, check for duplicate files and overlapping statement periods, then parse the broker format.", "Match every sell to buy lots FIFO, run the 3-year test per lot, convert at the ČNB rate of the day (cached).", "Write results only at the very end so a failed run writes nothing.", "Use commands: /sell for a planned sale, /report for the year, /dap for tax-return grouping, /export for evidence." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 11.8, "sources": [ { "author": "/u/MiveClor", "handle": "/u/MiveClor", "url": "https://www.reddit.com/r/n8n/comments/1x52mx6/i_built_a_telegram_bot_in_n8n_that_calculates_my/", "platform": "reddit", "date": "2026-10-13", "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": "claude-code-skill-biology-figures", "url": "https://agentsetups.dev/use-case/claude-code-skill-biology-figures/", "title": "Generate interactive, sourced biology figures", "summary": "A Claude Code skill researches the mechanism, builds SVG geometry, adds interaction and verifies it, with citations for numeric claims.", "category": "research-science", "category_label": "Research & science", "agents": [ "Claude" ], "models": [], "tools": [ "Anima skill", "SVG", "WebGL" ], "prompt": "Goal: Explain a biological mechanism with an interactive figure instead of a static image.\nSetup: agents used in source: Claude; tools/MCPs stated: Anima skill, SVG, WebGL.\nSteps:\n1. Install the Anima skill in Claude Code.\n2. Ask in plain language, e.g. compare how cocaine and amphetamine affect dopamine transport.\n3. Let the agent research the mechanism, identify structures, build isometric SVG geometry, add interaction and verify the result.\n4. Check the citations it adds for numerical claims and its notes on uncertainty; it is not a guarantee of correctness.\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/zealshama — https://www.reddit.com/r/LLMDevs/comments/1x578yw/i_built_an_opensource_claude_code_skill_that/", "steps": [ "Install the Anima skill in Claude Code.", "Ask in plain language, e.g. compare how cocaine and amphetamine affect dopamine transport.", "Let the agent research the mechanism, identify structures, build isometric SVG geometry, add interaction and verify the result.", "Check the citations it adds for numerical claims and its notes on uncertainty; it is not a guarantee of correctness." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 11.1, "sources": [ { "author": "/u/zealshama", "handle": "/u/zealshama", "url": "https://www.reddit.com/r/LLMDevs/comments/1x578yw/i_built_an_opensource_claude_code_skill_that/", "platform": "reddit", "date": "2026-10-13", "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": "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-form-ugc-ad-builder", "url": "https://agentsetups.dev/use-case/n8n-form-ugc-ad-builder/", "title": "Build a click-through UGC video ad maker in n8n", "summary": "One n8n workflow driven by Form pages: pick a presenter, voice, product shots and best takes; it upscales and joins them into a 1080p ad.", "category": "content-video", "category_label": "Content & video", "agents": [ "n8n" ], "models": [], "tools": [ "n8n Forms" ], "prompt": "Goal: Let a non-technical person make a UGC-style video ad by clicking through forms.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n Forms.\nSteps:\n1. Build one n8n workflow driven entirely by Form pages, so the user only opens one form URL.\n2. Ask for counts first (products, intro yes/no) so the next page shows exactly that many fields.\n3. Generate options at each step (4 presenters, 4 voice previews, product views, scenes) and show a \"use / re-roll with a note\" page before anything is paid for.\n4. Film one clip per product with several takes; let the user pick the best take per clip.\n5. Upscale the picked takes and join them into a 1080p MP4.\n6. Carry state in one $json.state object through every node so a re-roll keeps earlier choices.\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/useapi_net — https://www.reddit.com/r/n8n/comments/1wx2q9k/i_built_a_multipage_n8n_form_app_that_makes_ugc/", "steps": [ "Build one n8n workflow driven entirely by Form pages, so the user only opens one form URL.", "Ask for counts first (products, intro yes/no) so the next page shows exactly that many fields.", "Generate options at each step (4 presenters, 4 voice previews, product views, scenes) and show a \"use / re-roll with a note\" page before anything is paid for.", "Film one clip per product with several takes; let the user pick the best take per clip.", "Upscale the picked takes and join them into a 1080p MP4.", "Carry state in one $json.state object through every node so a re-roll keeps earlier choices." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 10.8, "sources": [ { "author": "/u/useapi_net", "handle": "/u/useapi_net", "url": "https://www.reddit.com/r/n8n/comments/1wx2q9k/i_built_a_multipage_n8n_form_app_that_makes_ugc/", "platform": "reddit", "date": "2026-10-04", "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": "cowork-fix-printer-scan-button", "url": "https://agentsetups.dev/use-case/cowork-fix-printer-scan-button/", "title": "Have Claude Cowork fix a years-old printer issue", "summary": "Cowork got a 10-year-old printer’s “scan to computer” button working again after years of failed manual attempts.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Claude" ], "models": [], "tools": [], "prompt": "Goal: Fix a device feature that stopped working years ago.\nSetup: agents used in source: Claude.\nSteps:\n1. Describe the symptom to Cowork (e.g. the printer’s scan-to-computer button does nothing).\n2. Let it investigate settings and drivers on the Mac and apply the fix.\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: Arpit Agarwal — https://x.com/arpitagarwal1/status/2108065673566122051 (summarised from source; the source has no explicit step list)", "steps": [ "Describe the symptom to Cowork (e.g. the printer’s scan-to-computer button does nothing).", "Let it investigate settings and drivers on the Mac and apply the fix." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 10.7, "sources": [ { "author": "Arpit Agarwal", "handle": "@arpitagarwal1", "url": "https://x.com/arpitagarwal1/status/2108065673566122051", "platform": "x", "date": "2026-10-08", "primary": true } ] }, { "slug": "grokbot-watch-baseball-for-you", "url": "https://agentsetups.dev/use-case/grokbot-watch-baseball-for-you/", "title": "Have Grok Bot watch the game and ping key moments", "summary": "It pings when a playoff game reaches the 4th inning, on every score and at the final, and sends the day’s schedule each morning.", "category": "personal-life", "category_label": "Personal life", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Follow games without watching the whole thing.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Tell Grok Bot your teams and which moments matter.\n2. Have it ping you at the 4th inning, on every score and at the final.\n3. Have it send the day’s schedule every morning.\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: I’m Still …. Southern Living — https://x.com/SouthernLvg/status/2108045118620021176", "steps": [ "Tell Grok Bot your teams and which moments matter.", "Have it ping you at the 4th inning, on every score and at the final.", "Have it send the day’s schedule every morning." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 10.7, "sources": [ { "author": "I’m Still …. Southern Living", "handle": "@SouthernLvg", "url": "https://x.com/SouthernLvg/status/2108045118620021176", "platform": "x", "date": "2026-10-08", "primary": true } ] }, { "slug": "openclaw-translate-family-whatsapp", "url": "https://agentsetups.dev/use-case/openclaw-translate-family-whatsapp/", "title": "Translate the WhatsApp groups your family relies on", "summary": "An OpenClaw plugin translates chosen Hebrew groups (voice notes, photos of notices) into Russian digests on Telegram. It never writes back.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "OpenClaw" ], "models": [], "tools": [ "WhatsApp", "Telegram" ], "prompt": "Goal: Never miss a kindergarten or building announcement in a language I can’t read.\nSetup: agents used in source: OpenClaw; tools/MCPs stated: WhatsApp, Telegram.\nSteps:\n1. Run your own OpenClaw gateway with WhatsApp linked as a device and a Telegram bot as the destination.\n2. Pick the groups to watch; give each its own destination chat and glossary of names.\n3. Transcribe and translate voice notes; lift text off photos of notices while keeping tables as tables.\n4. Batch messages into digests instead of one notification per line.\n5. Never write into WhatsApp and don’t let the assistant act on those chats, so planted instructions can’t run anything.\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/SleepEnvironmental62 — https://www.reddit.com/r/openclaw/comments/1wwtudl/i_dont_read_hebrew_so_i_built_a_plugin_that/", "steps": [ "Run your own OpenClaw gateway with WhatsApp linked as a device and a Telegram bot as the destination.", "Pick the groups to watch; give each its own destination chat and glossary of names.", "Transcribe and translate voice notes; lift text off photos of notices while keeping tables as tables.", "Batch messages into digests instead of one notification per line.", "Never write into WhatsApp and don’t let the assistant act on those chats, so planted instructions can’t run anything." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 10.6, "sources": [ { "author": "/u/SleepEnvironmental62", "handle": "/u/SleepEnvironmental62", "url": "https://www.reddit.com/r/openclaw/comments/1wwtudl/i_dont_read_hebrew_so_i_built_a_plugin_that/", "platform": "reddit", "date": "2026-10-03", "primary": true } ] }, { "slug": "muse-dashboard-replaces-codex-apps", "url": "https://agentsetups.dev/use-case/muse-dashboard-replaces-codex-apps/", "title": "Replace hand-built dashboards with a Meta Muse one", "summary": "A user retired his Codex-built custom apps for a Meta Muse dashboard with screens, alerts, news events and charts.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Meta Muse" ], "models": [], "tools": [], "prompt": "Goal: Stop maintaining my own custom tracking apps.\nSetup: agents used in source: Meta Muse.\nSteps:\n1. Ask the Meta Muse app for a dashboard with your screens, alerts, news events and charts.\n2. Retire the custom apps it replaces.\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: Will Kriski — https://x.com/willkriski/status/2107192560989110429 (summarised from source; the source has no explicit step list)", "steps": [ "Ask the Meta Muse app for a dashboard with your screens, alerts, news events and charts.", "Retire the custom apps it replaces." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-05", "trend_score": 10.2, "sources": [ { "author": "Will Kriski", "handle": "@willkriski", "url": "https://x.com/willkriski/status/2107192560989110429", "platform": "x", "date": "2026-10-05", "primary": true } ] }, { "slug": "dots-ux-review-web-app", "url": "https://agentsetups.dev/use-case/dots-ux-review-web-app/", "title": "Have your Dot review your app’s UX and apply fixes", "summary": "Unprompted, a Dot offered a first-time-user review of a web app, then made the changes with before/after views for approval.", "category": "design-frontend", "category_label": "Design & frontend", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [], "prompt": "Goal: Improve my web app’s UX with my personal agent.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Ask your Dot to review the app from a first-time user’s perspective and rank the highest-impact UX fixes.\n2. Ask it to make the changes and show before/after comparisons.\n3. Review everything before publishing.\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: Isabella — https://x.com/isabellasyan/status/2106450829477884349", "steps": [ "Ask your Dot to review the app from a first-time user’s perspective and rank the highest-impact UX fixes.", "Ask it to make the changes and show before/after comparisons.", "Review everything before publishing." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-03", "trend_score": 9.9, "sources": [ { "author": "Isabella", "handle": "@isabellasyan", "url": "https://x.com/isabellasyan/status/2106450829477884349", "platform": "x", "date": "2026-10-03", "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": "claude-code-native-tv-plex-client", "url": "https://agentsetups.dev/use-case/claude-code-native-tv-plex-client/", "title": "Reverse-engineer a TV to build a faster native app", "summary": "With Ghidra and Claude Code, an iOS dev built a native Plex client for a 2019 LG TV: profile picker in ~3 s instead of ~30 s.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Claude" ], "models": [ "Opus" ], "tools": [ "Ghidra", "Rust", "OpenGL" ], "prompt": "Goal: Replace a slow official TV app with a native one.\nSetup: agents used in source: Claude; tools/MCPs stated: Ghidra, Rust, OpenGL.\nSteps:\n1. On a development TV, pull the native libraries and open them in Ghidra.\n2. Ask the model to work out how things are implemented, navigating addresses, xrefs and strings; trust the binary and real hardware over its claims.\n3. Prove the hard part first (a real video frame on the hardware video plane) before building the app.\n4. Watch for code that compiles but breaks elsewhere when agents refactor (memory and ownership).\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/Purple_Imagination_1 — https://www.reddit.com/r/ClaudeCode/comments/1x043yp/i_used_claude_code_to_reverseengineer_an_lg_tv/ (summarised from source; the source has no explicit step list)", "steps": [ "On a development TV, pull the native libraries and open them in Ghidra.", "Ask the model to work out how things are implemented, navigating addresses, xrefs and strings; trust the binary and real hardware over its claims.", "Prove the hard part first (a real video frame on the hardware video plane) before building the app.", "Watch for code that compiles but breaks elsewhere when agents refactor (memory and ownership)." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 9.8, "sources": [ { "author": "/u/Purple_Imagination_1", "handle": "/u/Purple_Imagination_1", "url": "https://www.reddit.com/r/ClaudeCode/comments/1x043yp/i_used_claude_code_to_reverseengineer_an_lg_tv/", "platform": "reddit", "date": "2026-10-07", "primary": true } ] }, { "slug": "openclaw-face-and-voice-iphone", "url": "https://agentsetups.dev/use-case/openclaw-face-and-voice-iphone/", "title": "Give your OpenClaw agent a face and voice on iPhone", "summary": "An iPhone app is only the face and voice of your own OpenClaw gateway on a Mac, over Tailscale, with lip-sync and hands-free talk.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "OpenClaw" ], "models": [], "tools": [ "Tailscale", "iPhone" ], "prompt": "Goal: Talk to my own agent hands-free, like a person.\nSetup: agents used in source: OpenClaw; tools/MCPs stated: Tailscale, iPhone.\nSteps:\n1. Keep the OpenClaw gateway on your own Mac.\n2. Connect the phone app over your Tailscale network and approve its device key once.\n3. Use the gateway’s text-to-speech for the voice; the app lip-syncs from the text.\n4. Talk, pause, and it sends; it listens again after each reply.\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/Sweaty_Ad_6152 — https://www.reddit.com/r/openclaw/comments/1x3wyq9/i_gave_my_openclaw_agent_a_face_and_a_voice_on/ (summarised from source; the source has no explicit step list)", "steps": [ "Keep the OpenClaw gateway on your own Mac.", "Connect the phone app over your Tailscale network and approve its device key once.", "Use the gateway’s text-to-speech for the voice; the app lip-syncs from the text.", "Talk, pause, and it sends; it listens again after each reply." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 9.5, "sources": [ { "author": "/u/Sweaty_Ad_6152", "handle": "/u/Sweaty_Ad_6152", "url": "https://www.reddit.com/r/openclaw/comments/1x3wyq9/i_gave_my_openclaw_agent_a_face_and_a_voice_on/", "platform": "reddit", "date": "2026-10-12", "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": "student-proves-geometry-conjecture", "url": "https://agentsetups.dev/use-case/student-proves-geometry-conjecture/", "title": "Work with Claude to prove a geometry conjecture", "summary": "A 9th grader and Claude proved the rhombicosidodecahedron can’t pass through a copy of itself, with a 38-CPU-hour interval-arithmetic check.", "category": "research-science", "category_label": "Research & science", "agents": [ "Claude" ], "models": [], "tools": [ "interval arithmetic" ], "prompt": "Goal: Tackle an open maths problem with an AI collaborator while staying in charge.\nSetup: agents used in source: Claude; tools/MCPs stated: interval arithmetic.\nSteps:\n1. Choose the problem and decide the direction at each step yourself.\n2. Let Claude help with arguments, code and writing the paper.\n3. Use a computer check that rounding can’t fool (here interval arithmetic over ~12.3 million boxes).\n4. Ask it to re-check the whole proof from scratch and fix the real mistakes it finds; check everything 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/Gihyo0921 — https://www.reddit.com/r/ClaudeAI/comments/1x2eybb/im_a_9th_grader_and_i_used_claude_to_prove_a/", "steps": [ "Choose the problem and decide the direction at each step yourself.", "Let Claude help with arguments, code and writing the paper.", "Use a computer check that rounding can’t fool (here interval arithmetic over ~12.3 million boxes).", "Ask it to re-check the whole proof from scratch and fix the real mistakes it finds; check everything yourself." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-10", "trend_score": 8.7, "sources": [ { "author": "/u/Gihyo0921", "handle": "/u/Gihyo0921", "url": "https://www.reddit.com/r/ClaudeAI/comments/1x2eybb/im_a_9th_grader_and_i_used_claude_to_prove_a/", "platform": "reddit", "date": "2026-10-10", "primary": true } ] }, { "slug": "claude-code-subagents-video-call", "url": "https://agentsetups.dev/use-case/claude-code-subagents-video-call/", "title": "See your Claude Code subagents as a live video call", "summary": "A VS Code extension reads Claude Code’s session files and shows each subagent as a character in a call, with real commands and diffs.", "category": "coding", "category_label": "Coding", "agents": [ "Claude" ], "models": [], "tools": [ "VS Code", "Node" ], "prompt": "Goal: Follow what each subagent is doing without reading a wall of logs.\nSetup: agents used in source: Claude; tools/MCPs stated: VS Code, Node.\nSteps:\n1. Read the session files Claude Code already writes in ~/.claude/projects and follow the current session live.\n2. Show each subagent joining when it gets a task and leaving when it reports back.\n3. Show a shared “screen” with the agent’s real commands, output, diffs and files read.\n4. Add a tree of who asked whom, a recap of changed files and replay of past 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: /u/stickygoose — https://www.reddit.com/r/ClaudeAI/comments/1x2f59x/i_made_my_claude_code_subagents_a_video_call/", "steps": [ "Read the session files Claude Code already writes in ~/.claude/projects and follow the current session live.", "Show each subagent joining when it gets a task and leaving when it reports back.", "Show a shared “screen” with the agent’s real commands, output, diffs and files read.", "Add a tree of who asked whom, a recap of changed files and replay of past sessions." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-10", "trend_score": 8.5, "sources": [ { "author": "/u/stickygoose", "handle": "/u/stickygoose", "url": "https://www.reddit.com/r/ClaudeAI/comments/1x2f59x/i_made_my_claude_code_subagents_a_video_call/", "platform": "reddit", "date": "2026-10-10", "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": "grokbot-daily-lead-research-pack", "url": "https://agentsetups.dev/use-case/grokbot-daily-lead-research-pack/", "title": "Get a daily lead research pack with proof links", "summary": "Every morning: 5 brands with AI-visibility gaps, 5 mortgage brokers, 5 X threads to reply to — each with a proof link, date and “why now”.", "category": "sales-outreach", "category_label": "Sales & outreach", "agents": [ "Grok Bot" ], "models": [], "tools": [ "X" ], "prompt": "Goal: Get fresh, verified leads every morning.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: X.\nSteps:\n1. Define the lists you want (here 5 US brands with AI-visibility gaps, 5 Canadian mortgage brokers, 5 X threads worth a reply).\n2. Require a proof link, a date and a “why now” for every row.\n3. Have it dedupe against previous days (it caught 5 of 10 leads were repeats).\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: Hami Tahm — https://x.com/HamiTahm/status/2108558264158056660", "steps": [ "Define the lists you want (here 5 US brands with AI-visibility gaps, 5 Canadian mortgage brokers, 5 X threads worth a reply).", "Require a proof link, a date and a “why now” for every row.", "Have it dedupe against previous days (it caught 5 of 10 leads were repeats)." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 6.7, "sources": [ { "author": "Hami Tahm", "handle": "@HamiTahm", "url": "https://x.com/HamiTahm/status/2108558264158056660", "platform": "x", "date": "2026-10-09", "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": "codex-computer-use-backtest-pine", "url": "https://agentsetups.dev/use-case/codex-computer-use-backtest-pine/", "title": "Let Codex run hours of strategy backtests on screen", "summary": "Codex operated the computer for 12 hours of iterative backtesting of an old Pine Script algo on LuxAlgo.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Codex" ], "models": [], "tools": [ "Pine Script", "LuxAlgo" ], "prompt": "Goal: Re-test an old trading algorithm without clicking through it myself.\nSetup: agents used in source: Codex; tools/MCPs stated: Pine Script, LuxAlgo.\nSteps:\n1. Open the backtesting tool (here LuxAlgo, free).\n2. Have Codex operate the computer to run iterative backtests on the Pine Script algo.\n3. Let it run for hours and review 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: TargetAcquired — https://x.com/BitcoinCyborg/status/2107657695490875406", "steps": [ "Open the backtesting tool (here LuxAlgo, free).", "Have Codex operate the computer to run iterative backtests on the Pine Script algo.", "Let it run for hours and review the results." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-07", "trend_score": 6.5, "sources": [ { "author": "TargetAcquired", "handle": "@BitcoinCyborg", "url": "https://x.com/BitcoinCyborg/status/2107657695490875406", "platform": "x", "date": "2026-10-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": "pplx-computer-email-drafts-not-posting", "url": "https://agentsetups.dev/use-case/pplx-computer-email-drafts-not-posting/", "title": "Use Perplexity Computer email for drafts, not posting", "summary": "Asked to draft and post about an OSS repo, it wrote a clean draft but posted nowhere: HN refused, 5 sites gave 0 accounts.", "category": "marketing-growth", "category_label": "Marketing & growth", "agents": [ "Perplexity Computer" ], "models": [], "tools": [ "email" ], "prompt": "Goal: Test whether Perplexity Computer’s email agent can market a repo for me.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: email.\nSteps:\n1. Email Perplexity Computer asking it to draft and post once about the repo (use a throwaway account).\n2. Expect a good draft, then ToS refusals: in this test HN refused and 5 more sites produced 0 accounts and 0 posts.\n3. Post the draft 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: Yava — https://x.com/YavaCode/status/2105958358121328890", "steps": [ "Email Perplexity Computer asking it to draft and post once about the repo (use a throwaway account).", "Expect a good draft, then ToS refusals: in this test HN refused and 5 more sites produced 0 accounts and 0 posts.", "Post the draft yourself." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 6.0, "sources": [ { "author": "Yava", "handle": "@YavaCode", "url": "https://x.com/YavaCode/status/2105958358121328890", "platform": "x", "date": "2026-10-02", "primary": true } ] }, { "slug": "dots-pixel-art-aseprite", "url": "https://agentsetups.dev/use-case/dots-pixel-art-aseprite/", "title": "Make pixel art by installing Aseprite on your Dot", "summary": "Install Aseprite on the Dot’s computer instance and let it do the heavy work; results beat image gen for pixel art.", "category": "content-video", "category_label": "Content & video", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [ "Aseprite" ], "prompt": "Goal: Get better pixel art than image generation gives me.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Aseprite.\nSteps:\n1. Install Aseprite on your Dot’s computer instance.\n2. Set up a good workflow and have the Dot do the pixel-art work in Aseprite.\n3. Mind the security implications of installing arbitrary software 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: Michael Gwilt — https://x.com/mgwilt/status/2105745498019901614", "steps": [ "Install Aseprite on your Dot’s computer instance.", "Set up a good workflow and have the Dot do the pixel-art work in Aseprite.", "Mind the security implications of installing arbitrary software there." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-01", "trend_score": 5.9, "sources": [ { "author": "Michael Gwilt", "handle": "@mgwilt", "url": "https://x.com/mgwilt/status/2105745498019901614", "platform": "x", "date": "2026-10-01", "primary": true } ] }, { "slug": "claude-code-3d-survivors-game", "url": "https://agentsetups.dev/use-case/claude-code-3d-survivors-game/", "title": "Direct Claude Code to build a 3D survivors game", "summary": "A non-coder had a lead Claude Code session spec, review and deploy while subagents built stages; bots that play the game test balance.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [ "Opus", "Sonnet" ], "tools": [ "Three.js", "Vite", "Vitest", "Higgsfield", "Meshy", "ElevenLabs", "Obsidian" ], "prompt": "Goal: Ship a small, fun browser game without writing the code myself.\nSetup: agents used in source: Claude; tools/MCPs stated: Three.js, Vite, Vitest, Higgsfield, Meshy, ElevenLabs, Obsidian.\nSteps:\n1. Build the feel first with plain shapes (movement, a few spells, a boss) and playtest with blunt notes before any art.\n2. Only then make art: concept images, image-to-3D models, rigging and walk clips.\n3. Dump every idea into a brief; have Claude turn it into a versioned design doc you approve, then build in stages.\n4. Run one main Claude Code session as lead (specs, reviews, tests, deploys) and give each build stage to a subagent working from the spec.\n5. Gate every deploy: type check, all tests, build, then deploy.\n6. Test balance with bots that play the game, e.g. a “stand still” bot that must lose.\n7. Keep design docs, decisions and session logs in an Obsidian vault so the next session picks up where the last stopped.\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/Bonelessgummybear — https://www.reddit.com/r/vibecoding/comments/1x55yeh/3d_vampire_survivors_style_arcane_game_with/", "steps": [ "Build the feel first with plain shapes (movement, a few spells, a boss) and playtest with blunt notes before any art.", "Only then make art: concept images, image-to-3D models, rigging and walk clips.", "Dump every idea into a brief; have Claude turn it into a versioned design doc you approve, then build in stages.", "Run one main Claude Code session as lead (specs, reviews, tests, deploys) and give each build stage to a subagent working from the spec.", "Gate every deploy: type check, all tests, build, then deploy.", "Test balance with bots that play the game, e.g. a “stand still” bot that must lose.", "Keep design docs, decisions and session logs in an Obsidian vault so the next session picks up where the last stopped." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 5.9, "sources": [ { "author": "/u/Bonelessgummybear", "handle": "/u/Bonelessgummybear", "url": "https://www.reddit.com/r/vibecoding/comments/1x55yeh/3d_vampire_survivors_style_arcane_game_with/", "platform": "reddit", "date": "2026-10-13", "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": "mikeholp-route-claude-codex", "url": "https://agentsetups.dev/use-case/mikeholp-route-claude-codex/", "title": "Route by task type and make each agent review the other", "summary": "Route by task type and make each agent review the other", "category": "coding", "category_label": "Coding", "agents": [ "Claude", "Codex", "Cursor" ], "models": [ "Claude Opus 5.5 (medium/high effort)", "Claude Sonnet 5.5 (English content)", "GPT-6.1 Sol (bug fixes, features, scripts)", "GPT-6 Luna (small edits, data work)" ], "tools": [], "prompt": "Goal: Use Claude Code and Codex together, routing each task by type\nSetup: agents used in source: Claude, Codex, Cursor.\nBefore you start: A terminal and an account for each tool; Claude Pro plan; ChatGPT login or OpenAI API key for Codex.\nSteps:\n1. Install and sign in to both tools: The author's video covers install and sign-in (01:05–02:27).\n2. Classify each task by type, first match wins: Review, locale text, audits, research, English prose, broken, mechanical edit, feature, script, data.\n3. Map types to tool and model: Audits/research/content → Claude Code; bugs/features/scripts/data → Codex; lighter models for lighter jobs.\n4. Work in a separate project folder: Away from any script that sends email or writes to an outside service.\n5. Lock down permissions: Claude Code in manual mode with an allowlist, push/commit/merge/deploy/delete disallowed; Codex workspace-write or read-only.\n6. Fall back to the other tool on usage limits: At most four attempts; never moves to paid credits without approval.\n7. Have the other tool review substantial work: The reviewer reports findings and does not edit.\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 Holp — https://www.ai-automation-station.com/guides/claude-code-vs-codex.html (summarised from source; the source has no explicit step list)", "steps": [ "Install and sign in to both tools: The author's video covers install and sign-in (01:05–02:27).", "Classify each task by type, first match wins: Review, locale text, audits, research, English prose, broken, mechanical edit, feature, script, data.", "Map types to tool and model: Audits/research/content → Claude Code; bugs/features/scripts/data → Codex; lighter models for lighter jobs.", "Work in a separate project folder: Away from any script that sends email or writes to an outside service.", "Lock down permissions: Claude Code in manual mode with an allowlist, push/commit/merge/deploy/delete disallowed; Codex workspace-write or read-only.", "Fall back to the other tool on usage limits: At most four attempts; never moves to paid credits without approval.", "Have the other tool review substantial work: The reviewer reports findings and does not edit." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-11", "trend_score": 4.9, "sources": [ { "author": "Mike Holp", "handle": "Mike Holp", "url": "https://www.ai-automation-station.com/guides/claude-code-vs-codex.html", "platform": "blog", "date": "2026-10-11", "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": "joekarlsson-opencode-litellm", "url": "https://agentsetups.dev/use-case/joekarlsson-opencode-litellm/", "title": "Move your default coding agent to OpenCode via OpenRouter", "summary": "DeepSeek V4.1 Flash passed every run of his two-task test at about two cents a task (self-reported, \"a field report and not a ranking\").", "category": "agent-setup", "category_label": "Agent setup & config", "agents": [ "OpenCode", "Claude" ], "models": [ "DeepSeek V4.1 Flash", "Claude (escalation for the hardest problems)" ], "tools": [], "prompt": "Goal: Move your default coding agent to OpenCode with open-weight models\nSetup: agents used in source: OpenCode, Claude.\nBefore you start: An OpenRouter account (a LiteLLM gateway is optional).\nSteps:\n1. Point OpenCode at OpenRouter (gateway optional): The author routes everything through LiteLLM with names like cloud-coder, fallbacks and per-app budgets.\n2. Run your own two-task bake-off: One easy and one hard task with hidden tests; two runs per model; grade pass/fail, time and cost.\n3. Pick the cheapest model that passes: For him: DeepSeek V4.1 Flash as default.\n4. Make OpenCode send reasoning back: Set `interleaved: {field: \"reasoning_content\"}` and a reasoningEffort per model in opencode.json.\n5. Add a \"Done means verified\" rule to global AGENTS.md: Run the change, paste 1–5 proof lines, end PASS or FAIL.\n6. Add a verify gate if the model still skips it: A ~100-line OpenCode plugin sends the agent back once if it edited code and ran nothing.\n7. Keep Claude as the escalation path: Harder coding to DeepSeek V4 Pro; the hardest problems to Claude.\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: Joe Karlsson — https://www.joekarlsson.com/blog/breaking-up-with-claude-code/ (summarised from source; the source has no explicit step list)", "steps": [ "Point OpenCode at OpenRouter (gateway optional): The author routes everything through LiteLLM with names like cloud-coder, fallbacks and per-app budgets.", "Run your own two-task bake-off: One easy and one hard task with hidden tests; two runs per model; grade pass/fail, time and cost.", "Pick the cheapest model that passes: For him: DeepSeek V4.1 Flash as default.", "Make OpenCode send reasoning back: Set `interleaved: {field: \"reasoning_content\"}` and a reasoningEffort per model in opencode.json.", "Add a \"Done means verified\" rule to global AGENTS.md: Run the change, paste 1–5 proof lines, end PASS or FAIL.", "Add a verify gate if the model still skips it: A ~100-line OpenCode plugin sends the agent back once if it edited code and ran nothing.", "Keep Claude as the escalation path: Harder coding to DeepSeek V4 Pro; the hardest problems to Claude." ], "steps_basis": "summarised", "time": null, "cost": "About two cents a task on DeepSeek V4.1 Flash; OpenCode capped at $20 a month at his gateway", "date": "2026-10", "trend_score": 3.9, "sources": [ { "author": "Joe Karlsson", "handle": "Joe Karlsson", "url": "https://www.joekarlsson.com/blog/breaking-up-with-claude-code/", "platform": "blog", "date": "2026-10", "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": "claude-code-desk-usage-display", "url": "https://agentsetups.dev/use-case/claude-code-desk-usage-display/", "title": "Put your Claude Code usage on a desk display", "summary": "Claude wrote a Claude Code mod, ESP32 firmware and UI, then drove FreeCAD from the display’s drawing to make a printable enclosure.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [ "ESP32", "FreeCAD" ], "prompt": "Goal: See subscription usage and context window at a glance on a small screen.\nSetup: agents used in source: Claude; tools/MCPs stated: ESP32, FreeCAD.\nSteps:\n1. Use a Claude Code mod to pull subscription usage and context-window data out to a display over USB.\n2. Have Claude write the mod, the ESP32 firmware and the UI.\n3. Give Claude the manufacturer’s dimensioned drawing and have it drive FreeCAD to design the enclosure and stand.\n4. 3D print and assemble.\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/fcampanini74 — https://www.reddit.com/r/ClaudeCode/comments/1wye4ix/i_just_wanted_to_try_the_new_claude_code_mods_i/ (summarised from source; the source has no explicit step list)", "steps": [ "Use a Claude Code mod to pull subscription usage and context-window data out to a display over USB.", "Have Claude write the mod, the ESP32 firmware and the UI.", "Give Claude the manufacturer’s dimensioned drawing and have it drive FreeCAD to design the enclosure and stand.", "3D print and assemble." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-05", "trend_score": 3.7, "sources": [ { "author": "/u/fcampanini74", "handle": "/u/fcampanini74", "url": "https://www.reddit.com/r/ClaudeCode/comments/1wye4ix/i_just_wanted_to_try_the_new_claude_code_mods_i/", "platform": "reddit", "date": "2026-10-05", "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": "claude-muse-meal-plan-grocery-order", "url": "https://agentsetups.dev/use-case/claude-muse-meal-plan-grocery-order/", "title": "Plan meals with Claude, let Muse order the groceries", "summary": "Claude writes a two-week meal plan for approval and the shopping list; Muse places the order in its browser while he confirms payment.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Claude", "Meta Muse" ], "models": [], "tools": [ "Google Docs", "Walmart", "tablet kiosk" ], "prompt": "Goal: Hand off meal planning and grocery ordering but keep the final say.\nSetup: agents used in source: Claude, Meta Muse; tools/MCPs stated: Google Docs, Walmart, tablet kiosk.\nSteps:\n1. Have Claude draft a two-week meal plan from household preferences and last cycle’s feedback, and submit it for review.\n2. After approval, have it build the grocery list, add low pantry staples, and save it as a Google Doc in a dedicated folder.\n3. Have Muse read the doc and place the order in its own browser; confirm the final payment yourself from your phone.\n4. Show the plan, tonight’s recipe, thaw reminders and the list on a kitchen tablet in kiosk 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: /u/WeezerHunter — https://www.reddit.com/r/ClaudeAI/comments/1wxlm01/ai_is_a_hellofresh_killer_automated_meal_prep_and/", "steps": [ "Have Claude draft a two-week meal plan from household preferences and last cycle’s feedback, and submit it for review.", "After approval, have it build the grocery list, add low pantry staples, and save it as a Google Doc in a dedicated folder.", "Have Muse read the doc and place the order in its own browser; confirm the final payment yourself from your phone.", "Show the plan, tonight’s recipe, thaw reminders and the list on a kitchen tablet in kiosk mode." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-04", "trend_score": 1.3, "sources": [ { "author": "/u/WeezerHunter", "handle": "/u/WeezerHunter", "url": "https://www.reddit.com/r/ClaudeAI/comments/1wxlm01/ai_is_a_hellofresh_killer_automated_meal_prep_and/", "platform": "reddit", "date": "2026-10-04", "primary": true } ] }, { "slug": "claude-splat-engine-then-game", "url": "https://agentsetups.dev/use-case/claude-splat-engine-then-game/", "title": "Build a splat engine, then let Claude design the game", "summary": "Opus built a Gaussian-splat 3D engine in ~5 hours; told only the genre, it then made every design decision for a survivors game.", "category": "games", "category_label": "Games", "agents": [ "Claude" ], "models": [ "Opus 5.5" ], "tools": [ "Gaussian splats" ], "prompt": "Goal: See what the model designs when I hand it every decision.\nSetup: agents used in source: Claude; tools/MCPs stated: Gaussian splats.\nSteps:\n1. Build the engine first (here about 5 hours and ~20 prompts to tune it).\n2. Tell Claude only the genre and to use the engine you just made.\n3. Tell it to make all the design decisions and only come back when the whole game is finished.\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/buak — https://www.reddit.com/r/vibecoding/comments/1wvu4u0/made_a_3dengine_that_uses_gaussian_splats_instead/", "steps": [ "Build the engine first (here about 5 hours and ~20 prompts to tune it).", "Tell Claude only the genre and to use the engine you just made.", "Tell it to make all the design decisions and only come back when the whole game is finished." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 0.9, "sources": [ { "author": "/u/buak", "handle": "/u/buak", "url": "https://www.reddit.com/r/vibecoding/comments/1wvu4u0/made_a_3dengine_that_uses_gaussian_splats_instead/", "platform": "reddit", "date": "2026-10-02", "primary": true } ] }, { "slug": "dots-household-admin-week", "url": "https://agentsetups.dev/use-case/dots-household-admin-week/", "title": "What a Dot did in a week of household admin", "summary": "Zapier’s Harry Guinness: bounced card payments, a scam check, grant paperwork, delivery clashes, new restaurant tables.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "ChatGPT Dots" ], "models": [], "tools": [ "Google account" ], "prompt": "Goal: Let a Dot connected to my real Google account handle household admin.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Google account.\nSteps:\n1. Connect your Dot to your actual Google account (the author notes the privacy trade-off).\n2. Let it flag issues proactively: bounced card payments, clashing deliveries, documents that miss requirements (a lead-pipe grant).\n3. Ask it to check suspicious emails (it correctly said a forwarded email was legitimate).\n4. Give it errands: find alternative tables when a booking is cancelled, troubleshoot a broadband login with support.\n5. Don’t let it run your inbox unsupervised: it can miss urgent, high-judgment items.\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: Harry Guinness — https://zapier.com/blog/chatgpt-dots/", "steps": [ "Connect your Dot to your actual Google account (the author notes the privacy trade-off).", "Let it flag issues proactively: bounced card payments, clashing deliveries, documents that miss requirements (a lead-pipe grant).", "Ask it to check suspicious emails (it correctly said a forwarded email was legitimate).", "Give it errands: find alternative tables when a booking is cancelled, troubleshoot a broadband login with support.", "Don’t let it run your inbox unsupervised: it can miss urgent, high-judgment items." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-13", "trend_score": 0.0, "sources": [ { "author": "Harry Guinness", "handle": "Zapier blog", "url": "https://zapier.com/blog/chatgpt-dots/", "platform": "blog", "date": "2026-10-13", "primary": true } ] }, { "slug": "cowork-replace-portfolio-tool", "url": "https://agentsetups.dev/use-case/cowork-replace-portfolio-tool/", "title": "Automate portfolio workflows in Cowork instead of buying", "summary": "Vendor portfolio tools cost a lot for features they didn’t need; Cowork + MS365 + add-ins + skills automated the workflows.", "category": "productivity-ops", "category_label": "Productivity & ops", "agents": [ "Claude" ], "models": [], "tools": [ "Microsoft 365" ], "prompt": "Goal: Avoid an expensive portfolio management tool.\nSetup: agents used in source: Claude; tools/MCPs stated: Microsoft 365.\nSteps:\n1. List the workflows you actually need from the vendor tool.\n2. Connect Claude Cowork to Microsoft 365 and its add-ins.\n3. Write skills for each workflow and automate 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: Purnendu Shekhar — https://x.com/shekhar311224/status/2108214631986868410 (summarised from source; the source has no explicit step list)", "steps": [ "List the workflows you actually need from the vendor tool.", "Connect Claude Cowork to Microsoft 365 and its add-ins.", "Write skills for each workflow and automate them." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 0.0, "sources": [ { "author": "Purnendu Shekhar", "handle": "@shekhar311224", "url": "https://x.com/shekhar311224/status/2108214631986868410", "platform": "x", "date": "2026-10-08", "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": "goose-web-ui-sandboxed-microvm", "url": "https://agentsetups.dev/use-case/goose-web-ui-sandboxed-microvm/", "title": "Put a web UI on a Goose agent in a microVM", "summary": "React SSR + Express + SSE front end talking ACP over WebSockets to a sandboxed Goose agent, with SQLite and WhatsApp.", "category": "coding", "category_label": "Coding", "agents": [ "Goose" ], "models": [], "tools": [ "React", "Express", "SSE", "ACP", "WebSockets", "SQLite", "WhatsApp" ], "prompt": "Goal: Use a Goose agent safely from a browser and WhatsApp.\nSetup: agents used in source: Goose; tools/MCPs stated: React, Express, SSE, ACP, WebSockets, SQLite, WhatsApp.\nSteps:\n1. Run Goose inside a sandboxed microVM.\n2. Connect to it with ACP over WebSockets from an Express server.\n3. Stream responses to a React (SSR) UI via SSE.\n4. Persist sessions in SQLite and add a WhatsApp integration.\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: Ismael — https://x.com/IsmaelFcoM/status/2107984515465675147", "steps": [ "Run Goose inside a sandboxed microVM.", "Connect to it with ACP over WebSockets from an Express server.", "Stream responses to a React (SSR) UI via SSE.", "Persist sessions in SQLite and add a WhatsApp integration." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-08", "trend_score": 0.0, "sources": [ { "author": "Ismael", "handle": "@IsmaelFcoM", "url": "https://x.com/IsmaelFcoM/status/2107984515465675147", "platform": "x", "date": "2026-10-08", "primary": true } ] }, { "slug": "grokbot-onchain-wallet-tracker", "url": "https://agentsetups.dev/use-case/grokbot-onchain-wallet-tracker/", "title": "Track your crypto wallet activity with Grok Bot", "summary": "A daily Sui user turned Grok Bot into a personal assistant that tracks his wallet and monitors onchain activity.", "category": "finance-trading", "category_label": "Finance & trading", "agents": [ "Grok Bot" ], "models": [], "tools": [ "Sui" ], "prompt": "Goal: Keep an eye on my onchain activity without checking manually.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Sui.\nSteps:\n1. Give Grok Bot your wallet address.\n2. Have it track wallet activity and collect the data for you.\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: Palaki — https://x.com/iampalaki/status/2110584074339598609 (summarised from source; the source has no explicit step list)", "steps": [ "Give Grok Bot your wallet address.", "Have it track wallet activity and collect the data for you." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 0.0, "sources": [ { "author": "Palaki", "handle": "@iampalaki", "url": "https://x.com/iampalaki/status/2110584074339598609", "platform": "x", "date": "2026-10-15", "primary": true } ] }, { "slug": "grokbot-builds-updates-website", "url": "https://agentsetups.dev/use-case/grokbot-builds-updates-website/", "title": "Have Grok Bot build and update a website daily", "summary": "Without writing code, a user talked Grok Bot into building a site (Bot Lodge), and it keeps it updated every day.", "category": "design-frontend", "category_label": "Design & frontend", "agents": [ "Grok Bot" ], "models": [], "tools": [], "prompt": "Goal: Run a website without coding.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Describe the site to Grok Bot in conversation.\n2. Have it build the site.\n3. Schedule it to update the site every day.\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: Nathan Petty — https://x.com/nathanpetty/status/2110574324394656008 (summarised from source; the source has no explicit step list)", "steps": [ "Describe the site to Grok Bot in conversation.", "Have it build the site.", "Schedule it to update the site every day." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 0.0, "sources": [ { "author": "Nathan Petty", "handle": "@nathanpetty", "url": "https://x.com/nathanpetty/status/2110574324394656008", "platform": "x", "date": "2026-10-15", "primary": true } ] }, { "slug": "grokbot-papers-to-prototype", "url": "https://agentsetups.dev/use-case/grokbot-papers-to-prototype/", "title": "Turn a gym idea into papers and a prototype", "summary": "Mid-workout he told Grok Bot an idea; it found research papers, summarised them and built a prototype on GitHub by the time he got home.", "category": "research-science", "category_label": "Research & science", "agents": [ "Grok Bot" ], "models": [], "tools": [ "GitHub" ], "prompt": "Goal: Explore an idea while I’m away from my desk.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: GitHub.\nSteps:\n1. Tell Grok Bot the idea by voice.\n2. Have it find relevant research papers with summaries.\n3. Ask it to build a working prototype taking the best of each paper and push it to GitHub.\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: Glauber — https://x.com/glauberxyz/status/2110573717499891753 (summarised from source; the source has no explicit step list)", "steps": [ "Tell Grok Bot the idea by voice.", "Have it find relevant research papers with summaries.", "Ask it to build a working prototype taking the best of each paper and push it to GitHub." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-15", "trend_score": 0.0, "sources": [ { "author": "Glauber", "handle": "@glauberxyz", "url": "https://x.com/glauberxyz/status/2110573717499891753", "platform": "x", "date": "2026-10-15", "primary": true } ] }, { "slug": "claude-code-power-bi-dashboard", "url": "https://agentsetups.dev/use-case/claude-code-power-bi-dashboard/", "title": "Build a Power BI dashboard by describing it", "summary": "With Claude Code connected to a Power BI project, a dashboard took 20 minutes instead of ~2 days.", "category": "data-analysis", "category_label": "Data analysis", "agents": [ "Claude" ], "models": [], "tools": [ "Power BI" ], "prompt": "Goal: Speed up building Power BI reports.\nSetup: agents used in source: Claude; tools/MCPs stated: Power BI.\nSteps:\n1. Connect Claude Code to your Power BI project.\n2. Describe the dashboard you want in plain English.\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: CalibreAI — https://x.com/Calibre_AI/status/2108533676493672945 (summarised from source; the source has no explicit step list)", "steps": [ "Connect Claude Code to your Power BI project.", "Describe the dashboard you want in plain English." ], "steps_basis": "summarised", "time": null, "cost": null, "date": "2026-10-09", "trend_score": 0.0, "sources": [ { "author": "CalibreAI", "handle": "@Calibre_AI", "url": "https://x.com/Calibre_AI/status/2108533676493672945", "platform": "x", "date": "2026-10-09", "primary": true } ] }, { "slug": "hermes-as-coding-agent-tips", "url": "https://agentsetups.dev/use-case/hermes-as-coding-agent-tips/", "title": "Turn Hermes Agent into a coding machine", "summary": "After 2 months, Hermes builds his apps (14k and 25k lines): ast-grep skill, coding model, no approvals, Superpowers, a vision model.", "category": "coding", "category_label": "Coding", "agents": [ "Hermes Agent" ], "models": [], "tools": [ "Understand-Anything", "ast-grep", "Superpowers" ], "prompt": "Goal: Make a general-purpose agent reliable at real software work.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: Understand-Anything, ast-grep, Superpowers.\nSteps:\n1. Use Understand-Anything so you and the agent share the codebase context.\n2. Enable the optional ast-grep skill for smarter code search.\n3. Pick a model that’s strong at coding — the deciding factor.\n4. Configure the env so the agent runs uninterrupted (skip approvals).\n5. Use Superpowers for a proper development workflow.\n6. Add a vision model so it can see and verify the UI.\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: Kyz — https://x.com/minhng92/status/2109490581747708346", "steps": [ "Use Understand-Anything so you and the agent share the codebase context.", "Enable the optional ast-grep skill for smarter code search.", "Pick a model that’s strong at coding — the deciding factor.", "Configure the env so the agent runs uninterrupted (skip approvals).", "Use Superpowers for a proper development workflow.", "Add a vision model so it can see and verify the UI." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 0.0, "sources": [ { "author": "Kyz", "handle": "@minhng92", "url": "https://x.com/minhng92/status/2109490581747708346", "platform": "x", "date": "2026-10-12", "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": "amp-orb-garmin-watch-face", "url": "https://agentsetups.dev/use-case/amp-orb-garmin-watch-face/", "title": "Build a Garmin watch face in a cloud Amp Orb", "summary": "An Amp Orb set up with the Garmin Connect IQ SDK and simulator built a recreation of a favourite old Garmin watch face.", "category": "hardware-iot", "category_label": "Hardware & IoT", "agents": [ "Amp" ], "models": [], "tools": [ "Garmin Connect IQ SDK", "Garmin simulator" ], "prompt": "Goal: Recreate a watch face I loved from older Garmin models.\nSetup: agents used in source: Amp; tools/MCPs stated: Garmin Connect IQ SDK, Garmin simulator.\nSteps:\n1. Set up an Amp Orb with the Garmin CIQ SDK and Simulator.\n2. Have it build the watch face in the cloud and test it in the simulator.\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: Robert — https://x.com/robertholak/status/2109734909270958171", "steps": [ "Set up an Amp Orb with the Garmin CIQ SDK and Simulator.", "Have it build the watch face in the cloud and test it in the simulator." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-12", "trend_score": 0.0, "sources": [ { "author": "Robert", "handle": "@robertholak", "url": "https://x.com/robertholak/status/2109734909270958171", "platform": "x", "date": "2026-10-12", "primary": true } ] }, { "slug": "dots-resume-crashed-codex-threads", "url": "https://agentsetups.dev/use-case/dots-resume-crashed-codex-threads/", "title": "Have your Dot resume crashed Codex threads", "summary": "Ubuntu killed the Codex app mid-run; after a restart, his Dot found and resumed every interrupted parallel thread.", "category": "personal-assistant", "category_label": "Personal assistants", "agents": [ "Codex", "ChatGPT Dots" ], "models": [], "tools": [ "Ubuntu" ], "prompt": "Goal: Recover several parallel Codex threads after a crash.\nSetup: agents used in source: Codex, ChatGPT Dots; tools/MCPs stated: Ubuntu.\nSteps:\n1. After restarting, ask your Dot to find all interrupted Codex threads.\n2. Have it resume each one; expect it to take a while.\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: Deependra Solanky — https://x.com/solanky/status/2105871916800389433", "steps": [ "After restarting, ask your Dot to find all interrupted Codex threads.", "Have it resume each one; expect it to take a while." ], "steps_basis": "source", "time": null, "cost": null, "date": "2026-10-02", "trend_score": 0.0, "sources": [ { "author": "Deependra Solanky", "handle": "@solanky", "url": "https://x.com/solanky/status/2105871916800389433", "platform": "x", "date": "2026-10-02", "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": "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 } ] }, { "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 } ] } ] }