Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/naimkatiman/continuous-improvement/roast)<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/roast"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/roast/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/roast"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/roast.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00069 | $0.00513 |
| Opus 5.5 | $0.00028 | $0.00205 |
| Sonnet 5.5 | $0.00014 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
roast scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
/roast
Pressure-test an idea before you build it. Convene a council of five independent persona agents who attack the idea from every angle, then act as the Judge and return one decisive verdict — so Law 1 (Research Before Executing) is satisfied on the idea itself, not just the plan.
Trigger phrases
/roast/roast <the idea>- "roast this idea"
- "convene the council"
- "pressure-test this" / "stress-test this idea"
- "validate this business idea"
- "give me a brutal second opinion before I build this"
What happens
- Brief. Read the idea from the argument (if given) and ask up to 3-4 clarifying questions in one batch — the idea, the buyer + money model, your edge, your constraints. Skip the questions if the user says "just run it."
- Council (parallel). Spin up all five personas in parallel, each pasted the same brief: Contrarian (assume it fails), Expansionist (the 10x case), Logician (first-principles, no web), Researcher (web evidence + competitors), Buyer (role-play the target customer). Each returns a stance, 3-5 sharp points, the one thing you must hear, and a 1-10 score.
- Verdict. Act as the Judge: resolve the council's tension, fold in the economics lens, and return one
GO / RESHAPE / KILLcall with the biggest risk, biggest upside, money read, and — most importantly — the cheapest 48-hour test to validate the riskiest assumption before building anything.
Skill file
Full behavior is defined in skills/roast.md.
Pairs with
/grill-me— roast validates the idea; grill-me then hardens the plan./proceed-with-the-recommendation— walk the verdict's next steps under the 7 Laws.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 35 lines · 69 tokens per session scan A 5f55692d026c
roast is a command published in the GitHub repository naimkatiman/continuous-improvement (9 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 513 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
ap-swarm
Run a MultiAgentRuntime swarm in file mode — local journal at .runtime/conversation.md, no network.
reflect-promote
Promote learnings from skills to global CLAUDE.md.
reflect-meta
Show meta-learning statistics and pattern performance.
reflect-stats
Show cross-skill learning statistics.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.