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-megit 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-me)<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/grill-me"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/grill-me.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.1 | $0.00031 | $0.00502 |
| Opus 5 | $0.00015 | $0.00251 |
| Sonnet 5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
grill-me 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 6d 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
/grill-me
Stress-test the current plan or design by interviewing the user one question at a time, walking every branch of the decision tree, and recommending an answer for each.
Trigger phrases
/grill-me- "grill me"
- "stress-test this plan"
- "interview me about this"
- "what am I missing?"
What happens
- Identify the current plan or design from the conversation — the high-level goal, the assumptions in play, the decisions already made.
- Walk the decision tree top-down. For each unresolved branch, ask exactly one question with a recommended answer.
- Before asking, check whether the codebase already answers the question (
grep,ls, file reads). If it does, use that and skip the question. - Resolve dependencies in order — do not ask about deployment before the data model is pinned.
- Stop when the plan is shippable cold to a fresh agent. Do not interview past the point of usefulness.
Five interview rules
- One question at a time. Never multi-question; force depth on every branch.
- Always recommend. Every question carries "my answer would be X because Y".
- Explore before asking. Code answers beat user-attention answers.
- Walk the tree, do not jump. Order matters.
- Stop when shippable. End state is a plan a fresh agent could execute, not an infinite interview.
Skill file
Full behavior is defined in skills/grill-me.md. The verbatim upstream cold-storage copy lives at third-party/mattpocock-skills/skills/productivity/grill-me/SKILL.md; SHA pin in third-party/MANIFEST.md.
Attribution
Ported from mattpocock/skills productivity/grill-me (MIT, © 2026 Matt Pocock).
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.
- 6d ago First seen · 41 lines · 31 tokens per session scan A f7b22a3cd09d
grill-me is a command published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 11d ago), licensed MIT. It adds 31 tokens to every session and 502 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.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
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.