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.
npx agentmods add skills/naimkatiman/continuous-improvement/roastnpx skills add naimkatiman/continuous-improvement --skill roastgit 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/skills/naimkatiman/continuous-improvement/roast)<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/roast"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/roast.svg" alt="Measured on agentmods" 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 | $0.00098 | $0.01857 |
| Opus 5 | $0.00049 | $0.00928 |
| Sonnet 5 | $0.00020 | $0.00371 |
| Haiku 4.5 | $0.00010 | $0.00186 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/roast — Convene the council before you build
Claude's default is to agree with you. /roast is the opposite. Law 1 says research before executing — and the cheapest, most-skipped research is an honest adversarial read of the idea itself before any plan or code exists. This skill convenes a council of five independent persona agents who tear an idea apart and build it up from every angle, then a Judge synthesizes everything into one decisive verdict.
The council is adversarial on purpose. No persona is allowed to hedge or be polite. The point is to surface what you can't see because you're too close to it — and to do it in an hour, not after a month of building.
Adapted from the community /roast idea-council pattern and reshaped as a continuous-improvement-native Law 1 skill.
When to activate
- Before you sink time or money into building something — a product, a feature, a business, a bet.
- When you catch yourself (or the agent) agreeing with a plan that has never been attacked.
- The user types
/roast, "roast this idea", "convene the council", "pressure-test this", "stress-test this idea", "validate this business idea", or "give me a brutal second opinion". - A
/proceed-with-the-recommendationwalk is about to start but the premise underneath the recommendation list was never challenged.
Step 1: Get the brief
If $ARGUMENTS contains the idea, start there. Then ask a tight set of clarifying questions so the council judges something real. Ask only what hasn't already been provided — 3-4 questions max, in one batch:
- The idea in one or two sentences (what it is, what it does).
- Who it's for and how it makes money (the buyer + the price/model).
- Your edge — relevant skills, audience, or assets you already have.
- Constraints — budget, timeline, how fast you need the first dollar.
If the user says "just run it" or has already given you enough, skip the questions and proceed. Don't over-interrogate — one round, then convene.
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.
- 5d ago First seen · 109 lines · 98 tokens per session scan A 93d23f4d510f
roast is a skill published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 10d ago), licensed MIT. It adds 98 tokens to every session and 1,857 once invoked, about $0.0005 per session on Opus 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 skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…