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/testzugang/pi-plugins/grill-with-docsnpx skills add testzugang/pi-plugins --skill grill-with-docsgit clone --depth 1 https://github.com/testzugang/pi-pluginsWrote 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/testzugang/pi-plugins/grill-with-docs)<a href="https://agentmods.dev/skills/testzugang/pi-plugins/grill-with-docs"><img src="https://agentmods.dev/badge/skills/testzugang/pi-plugins/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.00046 | $0.00475 |
| Opus 5 | $0.00023 | $0.00237 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
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 3d 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 with Docs
Specialized grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallize.
Reference: Based on the grill-with-docs skill from mattpocock/skills.
Process
- Domain Awareness: Before grilling, use
scoutorreadto find existing documentation.- Look for
CONTEXT.md(glossary) anddocs/adr/(Architectural Decision Records). - If
CONTEXT-MAP.mdexists, the repo has multiple contexts; locate the relevant one.
- Look for
- Interview Relentlessly: Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
- Challenge against the Glossary: If a term conflicts with
CONTEXT.md, call it out immediately. - Sharpen Fuzzy Language: Propose precise canonical terms (e.g., "Customer" vs "User").
- Cross-reference with Code: Verify if the code agrees with the stated plan.
- Update Inline: Update
CONTEXT.mdand create ADRs (sparingly) as decisions are made.
Documentation Formats
ADR Criteria
Only offer to create an ADR when all three are true:
- Hard to reverse — high cost of changing later.
- Surprising without context — future readers will wonder "why?".
- Real trade-off — there were genuine alternatives.
Red Flags
- "We can fix the terminology later" -> No, sharpen it now.
- "I'll update CONTEXT.md at the end" -> No, update it inline.
- Creating ADRs for obvious or easily reversible decisions.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 41 lines · 46 tokens per session scan A 9ce4e7b3c3b6
grill-with-docs is a skill published in the GitHub repository testzugang/pi-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 475 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…