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/refo/claude-dev-helpers/grill-megit clone --depth 1 https://github.com/refo/claude-dev-helpersWrote 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/refo/claude-dev-helpers/grill-me)<a href="https://agentmods.dev/commands/refo/claude-dev-helpers/grill-me"><img src="https://agentmods.dev/badge/commands/refo/claude-dev-helpers/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 | $0.00000 | $0.00347 |
| Opus 5 | $0.00000 | $0.00173 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
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 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.
What it actually says
Grill Me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree.
Workflow
1. Prepare
Read any existing documentation (PRDs, design docs, code comments) that define the plan or design. If nothing exists, ask the user to describe it.
2. Ask relentlessly
Your goal: identify and resolve uncertainties, ambiguities, or weak assumptions. Ask one question at a time. After the user answers, ask the next question — don't ask multiple questions in sequence.
When questions can be answered by exploring the codebase, do so. Otherwise, rely on the user.
Recommended structure for each question:
[brief context about why this matters]
[your question]
[your recommended answer, or "I don't have enough context to recommend"]
3. Refine
As the user clarifies, refine your understanding. When you identify a conflict or ambiguity in the plan:
- Call it out explicitly: "I'm hearing X from you here, but Y from you earlier — which is correct?"
- Record the resolution: add a note that this was clarified
4. Finish
When you've resolved enough of the decision tree that implementing the plan is now unambiguous, write a summary document. Ask the user: "Should I write this up as a PRD, a plan, a design doc, or something else?"
Then do it.
When to use
Use this skill when:
- User asks to be "grilled" on a plan or design
- User mentions "stress-test" or "poke holes"
- You're about to build something and want to ensure shared understanding
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 · 47 lines · 0 tokens per session scan A 9516aafd2a11
grill-me is a command published in the GitHub repository refo/claude-dev-helpers (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 347 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.