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 julianobarbosa/claude-code-skills --skill grill-megit clone --depth 1 https://github.com/julianobarbosa/claude-code-skillsWrote 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/julianobarbosa/claude-code-skills/grill-me)<a href="https://agentmods.dev/skills/julianobarbosa/claude-code-skills/grill-me"><img src="https://agentmods.dev/badge/skills/julianobarbosa/claude-code-skills/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/julianobarbosa/claude-code-skills/grill-me"><img src="https://agentmods.dev/badge/skills/julianobarbosa/claude-code-skills/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.00037 | $0.00501 |
| Opus 5.5 | $0.00015 | $0.00200 |
| Sonnet 5.5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00004 | $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 1mo 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill Me
Interview the user relentlessly about every aspect of their plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
How It Works
When this skill is invoked, switch into interviewer mode:
- Read the plan — understand what the user has described so far.
- Identify the decision tree — map out every branch: architecture, data model, UX, edge cases, deployment, dependencies.
- Grill one branch at a time — ask focused questions, starting from the highest-impact unknowns. Don't move on until the branch is resolved.
- Surface dependencies — when one decision blocks or constrains another, name it explicitly before continuing.
- Summarize as you go — after each resolved branch, restate the decision so the user can confirm or correct.
- Stop when aligned — once all branches are resolved, present the complete shared understanding as a structured summary.
Rules
- Never assume. If something is ambiguous, ask.
- One topic at a time. Don't bundle unrelated questions.
- Push back. If a decision seems risky or contradictory, say so.
- No implementation. This skill is for planning only. Don't write code.
- Be direct. Skip pleasantries. Get to the point.
- Track progress. Keep a mental map of resolved vs. open branches so the user knows how much is left.
Gotchas
- The interview process is one-direction — saying "stop" and resuming later loses context. Save state explicitly before pausing.
- Tree-of-questions can fork deeply on minor branches — set a depth limit explicitly or get lost in irrelevant detail.
- Skipping a question defers all dependent branches — the skill may not flag the deferral; check for holes in the final summary.
- Time-budget vs depth-budget: "30 min interview" vs "5 levels deep" are different; pick the constraint that matches the user's intent.
- Recap accuracy depends on consistent terminology — switching terms mid-interview produces a recap that conflates concepts.
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.
- 1mo ago First seen · 40 lines · 37 tokens per session scan A 9cd352e5b96f
grill-me is a skill published in the GitHub repository julianobarbosa/claude-code-skills (14 stars, last pushed 11d ago), licensed MIT. It adds 37 tokens to every session and 501 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.