Agent use case packs: real jobs, step by step, page 3
A use case pack walks one specific job from blank page to result with an AI agent: the plan, the prompts for each stage, what usually goes wrong and how to check the output.
Route a coding agent's questions by the kind of decision, and log every answer
A team building a business system with coding agents has the agent stop and ask, with options, when a task runs past its spec. Questions about product direction, rule exceptions or loosening a check go to a person; routine design calls are answered from written rules and earlier rulings. In one week, 762 questions, 59 answered by the owner.
Check the whole MCP session, not just each tool call, for the untrusted input plus private data plus outbound mix
A post on r/mcp argues that per-call guardrails miss leaks made of two allowed calls, citing the case where a support ticket told an agent with a service role key to read a tokens table and post it back to the ticket. The fix is to break the combination of untrusted input, private data and an outbound channel per session.
Stop a browser agent clicking the wrong thing after the page changes under it
A team building a shared human and agent browser tags every agent action with who is driving the tab and the page revision the plan was based on. If either changed, the action fails as stale and the agent re-reads instead of clicking whatever is now at that spot.
Test a token-saving prompt against hidden tests before you adopt it
One builder ran a popular 'save tokens' prompt for Claude Code over 32 runs with hidden tests. Total cost fell about 9 percent on Opus and 6 percent on Sonnet, up to 20 percent on review tasks and close to zero on bug fixes, with the same quality. Most of the cost was reading code, which the prompt barely touched.
Check your machine for the backdoored Claude Code editor extension and clean up properly
For about eleven hours on Oct 29, Cursor's extension marketplace served a tampered build of the Claude Code extension (2.1.313) to up to 5,000 users. It added an SSH key and startup persistence that survive uninstalling the extension, so the fix is a check, an update and a credential rotation, not just a reinstall.
Give your Grok Bots office hours so questions wait for a briefing instead of interrupting you
A builder shared a prompt for a Chief of Staff bot that sorts every bot notification into urgent, decision and FYI, batches decisions into two daily review windows, rolls FYI into one end-of-day summary, and flags approvals that would expire before the next window.
Wake your bots on real work instead of a timer, and give each one its own read budget
A builder wiring seven Grok Bots into one launch workflow found hourly timers would mean over a thousand mostly empty runs a week. His fix: one scheduled check, every other bot woken by a trigger, a shared ledger for handoffs, a per-bot X read budget, a real dry-run mode and one spending bot behind a hard approval limit.
Build 3D scenes in Blender by letting the agent arrange library assets, not model them
A walkthrough for Claude with the official Blender MCP server: connect, confirm the agent can search the BlenderKit asset library, give it a reference image and plain instructions, and have it place assets, light, rig and animate. The rule that saves the project is never letting the model build furniture from scratch.
Move your Claude Code, Codex, Cursor or OpenClaw setup into Hermes with a dry run first
Nous Research's agent-importers plugin gives Hermes one command that reads an existing agent setup (instructions, memories, MCP servers, skills and command allow and deny lists) and shows a per-item plan before writing anything. Credentials stay behind unless you opt in for OpenClaw.
Run a multi-agent team on a ledger that only marks work done when the receiver confirms
YC Labs ran 50 agents in a Minecraft survival world and 10 against 10 Claude and GPT teams in Bed Wars. The colony's food ledger learned the hard way that a tool's 'delivered' report is not proof: a tossed ration was picked up by the wrong agent, so the rule became named chests and 'served only after the recipient confirms'.
Write down your own call before your agent argues for one
Anthropic gave 50 professional analysts Claude Code with a hidden, coin-flip lean on four analysis choices. They went with the agent's lean 86% of the time, 77% later reused its arguments, and only 15% credited it. A cheap guard: record your choice and reason before you ask the agent, then compare.
Have Claude write an Aseprite extension that paints isometric worlds from brushes
A game artist tired of hand-drawing hundreds of grass tiles spent a couple of weeks directing Claude to write the Lua for an Aseprite extension: SimCity-style brushes for hills, paths, ponds and trees that redraw only the area touched, with trees grown in 3D first and drawn back to pixels with the same camera.
Make a small browser horror game in a weekend with one style line per area for consistent 3D models
A non-coder made a six-minute first-person browser horror game in 52 hours: 150 models from Tripo for about $27 including retries, sound from ElevenLabs and code from Claude. The trick that kept a hundred separate generations looking like one house was one written style line per floor appended to every prompt.
Turn an official public source into a versioned git history, one agent session per source
A builder used separate Claude Code sessions, one per country, to download every version of each law from official publishers and write it out as git history with one commit per change on its in-force date. Each session checked robots.txt and the terms first, and two independent builds had to match hash for hash.
Sandbox your MCP servers too, because the agent's sandbox may not cover them
A write-up on r/mcp points out that Claude Code's and Codex's own docs say local MCP servers run as ordinary processes outside the agent's sandbox. It walks through a recent paper on narrow tools being steered into reading files outside their job, and gives concrete container and environment settings.
Design MCP tools and errors so the model's next call is the right one
Two MCP server builders shared numbers and rules from real use. A Photoshop server with 83 tools kept model-caused bad calls to about 1 in 290 by making every tool distinct, folding variants into parameters, returning errors that list allowed values, and giving the model a short capability map. A design editor server added batch writes with one undo step and idempotency keys that report stale after an undo.