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 d-gangz/dgang-skills --skill grillinggit clone --depth 1 https://github.com/d-gangz/dgang-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/d-gangz/dgang-skills/grilling)<a href="https://agentmods.dev/skills/d-gangz/dgang-skills/grilling"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/grilling/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/d-gangz/dgang-skills/grilling"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/grilling.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.00036 | $0.00837 |
| Opus 5 | $0.00018 | $0.00418 |
| Sonnet 5 | $0.00007 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
grilling 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 11d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview the user relentlessly about the thing they want to work on, walking the decision tree one branch at a time. The steps below are the mechanics; the goal is shared understanding — you and the user aligned on what to do and why. Keep the interview sharp and adaptive: pull moves as the conversation needs them, don't march the list.
How to grill
- Ground first. Spawn sub-agents in parallel to read the relevant codebase and anything the user attached or referenced — files, URLs, tickets, docs. Skip only if the subject is genuinely context-free.
- Start at the root. Open with the decision that gates the most others. Ask if the subject itself is unclear.
- One question at a time, always with a recommended answer. End on a single ask — don't bolt a second question on with "and" or a dash; that's the next turn's, not a tail on this one. An either/or that rephrases the same question is fine. Lay it out per Question shape.
- Facts you find; decisions are theirs. A fact — anything in the code, config, git history, or the attached resources — you look up/explore rather than ask. A decision is the user's: put it to them. Only ask for decisions, and for facts you genuinely can't derive.
- Follow dependencies. Resolve decisions in dependency order — each answer constrains the next, so settle the gating one before the choices that hang off it. Don't wander to siblings until the current branch is resolved.
- Don't stop early. Keep going until every decision has an answer, the user ends it, or what's left is pure implementation detail. Then summarize the decisions made — and stop. Don't act on the plan until the user confirms the summary reflects shared understanding.
Question shape
Make it answerable at a glance: lead with the question, then the options — each option's detail rides in the option, not a preamble before the list. Choice-shaped decisions get numbered options; open or reframing ones get just the recommendation and why.
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.
- 11d ago First seen · 42 lines · 36 tokens per session scan A aa9546adb81d
grilling is a skill published in the GitHub repository d-gangz/dgang-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 837 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.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…