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 skills add spencerpauly/skills-repo --skill grill-megit clone --depth 1 https://github.com/spencerpauly/skills-repoWrote 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/spencerpauly/skills-repo/grill-me)<a href="https://agentmods.dev/skills/spencerpauly/skills-repo/grill-me"><img src="https://agentmods.dev/badge/skills/spencerpauly/skills-repo/grill-me/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/spencerpauly/skills-repo/grill-me"><img src="https://agentmods.dev/badge/skills/spencerpauly/skills-repo/grill-me.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.00599 |
| Opus 5 | $0.00026 | $0.00300 |
| Sonnet 5 | $0.00010 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
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 12d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill Me
Walk the user down their own decision tree until there's nothing left unresolved. The point is not to agree with the plan — it's to surface the assumptions they're making without realizing it.
When to use
- The user shares a plan, RFC, design, or proposal and asks you to challenge it.
- The user says "grill me", "ask me hard questions", "what am I missing".
- Before a big commit / deploy / launch and the user wants a sanity check.
Steps
-
Read the plan once, without interrupting. Hold it in your head before asking anything.
-
Ask one question at a time. Wait for the answer before asking the next. Multiple questions at once = the user picks the easy one and skips the hard one.
-
Walk the decision tree depth-first.
- Pick the most load-bearing assumption.
- Resolve every branch under it before moving to the next assumption.
- Don't context-switch between unrelated decisions.
-
For each question, also state your recommended answer. Don't just interrogate — give the user something to push back on. A question without a hypothesis is a survey, not a grilling.
-
If a question can be answered by reading the codebase, read the codebase. Don't make the user look up something you can grep yourself.
-
Track open threads. If the user defers a decision, add it to a running "Open" list and circle back at the end.
Question patterns that work
- "What happens if <the assumption you're depending on> is wrong?"
- "Who is the first person to notice this is broken? How long after it breaks?"
- "What's the dumbest version of this we could ship in a day? Why isn't that good enough?"
- "When you say — do you mean A, B, or C?"
- "Walk me through the worst-case rollback. How bad is it?"
Output format
## Question 1
<the question>
**My guess:** <your recommended answer + 1-sentence rationale>
---
(after the user answers)
## Question 2
...
---
## Open at end of session
- ...
- ...
Don't
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.
- 12d ago First seen · 69 lines · 52 tokens per session scan A 698050787c66
grill-me is a skill published in the GitHub repository spencerpauly/skills-repo (25 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 599 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…