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 commands/naimkatiman/continuous-improvement/grill-with-docsgit 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/grill-with-docs)<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/grill-with-docs"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/grill-with-docs.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.00049 | $0.00612 |
| Opus 5 | $0.00024 | $0.00306 |
| Sonnet 5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
grill-with-docs 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grill-with-docs
Stress-test the current plan or design by interviewing the user one question at a time AND updating the project's domain-language doc (CONTEXT.md) and architecture decision records (docs/adr/) inline as decisions land.
Trigger phrases
/grill-with-docs- "grill me and update the docs"
- "stress-test this against our domain model"
- "let's nail down the language and ADR this"
What happens
- Read
CONTEXT.md(orCONTEXT-MAP.md+ per-contextCONTEXT.md) anddocs/adr/if they exist. Use them as the source of truth for project language and prior decisions. - Walk the decision tree top-down. One question at a time with a recommended answer.
- Challenge fuzzy terms against the glossary. Sharpen vague language. Stress-test relationships with concrete scenarios. Cross-reference user statements against the code.
- When a term is resolved, update
CONTEXT.mdimmediately (lazy-create if missing). Use the format in the skill's Appendix A. - Offer an ADR only when all three are true: hard to reverse, surprising without context, result of a real trade-off. Use the format in Appendix B.
When to fire this instead of /grill-me
| Skill | Use when |
|---|---|
/grill-me |
Conversation-only grilling; no project to update yet, or no docs convention. |
/grill-with-docs |
Project has CONTEXT.md or is ready to start one; decisions should persist past the session. |
Skill file
Full behavior, format specs, and 7 Laws fit are defined in skills/grill-with-docs.md. The verbatim upstream cold-storage copies live at third-party/mattpocock-skills/skills/engineering/grill-with-docs/ (SKILL.md, CONTEXT-FORMAT.md, ADR-FORMAT.md); SHA pin in third-party/MANIFEST.md.
Attribution
Ported from mattpocock/skills engineering/grill-with-docs (MIT, © 2026 Matt Pocock). Mattpocock calls this his most powerful skill: "It's hard to explain how powerful this is. It might be the single coolest technique in this repo."
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.
- 4d ago First seen · 39 lines · 49 tokens per session scan A 009c4889d969
grill-with-docs is a command published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 612 once invoked, about $0.0002 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 commands, from other repositories
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
release
Generate changelog, bump version, and create git tag.
analyze-and-create-issue
Analyze codebase and create GitHub/GitLab/Forgejo issues per finding.
generate-report
Generate a professional HTML report from assessment results in the conversation.
data-flow-analysis
Trace how data flows through the system from input to output.
market-context
Build the "why now" market narrative — macro forces, buying triggers, category moment — then deepen brain Section 5.