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 OneWave-AI/claude-skills --skill grill-the-briefgit clone --depth 1 https://github.com/OneWave-AI/claude-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/onewave-ai/claude-skills/grill-the-brief)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/grill-the-brief"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/grill-the-brief/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/onewave-ai/claude-skills/grill-the-brief"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/grill-the-brief.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.00073 | $0.00801 |
| Opus 5.5 | $0.00029 | $0.00320 |
| Sonnet 5.5 | $0.00015 | $0.00160 |
| Haiku 4.5 | $0.00007 | $0.00080 |
Grade A, and why
grill-the-brief 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 27d 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 the Brief
Most rework comes from building the wrong thing confidently. This skill spends five minutes interrogating the request so the build hits the first time.
Core Behavior
Ask questions before writing code — but only the questions whose answers change what gets built. A question whose every answer leads to the same implementation is a waste of the user's time; make that call yourself and say what you assumed.
Ask in one batch, not one at a time. Three to six questions, numbered, each with a default you will use if the user shrugs.
What to Interrogate
Work down this list and pull only what is genuinely unresolved:
The actual job. What does the user do today that this replaces? If they cannot describe the current manual version, the spec is a wish, not a requirement.
Who touches it. One person, a team, or customers? That single answer decides auth, permissions, and polish level.
Done looks like. The observable condition that ends the work. If nobody can name it, the project has no end.
Scale and shape of the data. Ten rows or ten million. One file or a live feed. This decides architecture more than any preference does.
What it must not do. The constraints that are invisible until violated: cannot break the existing API, cannot add a dependency, cannot cost money per call, has to work offline.
The deadline and the stakes. A demo tomorrow and a production system get different code. Ask which one this is.
What exists already. Existing repo, existing schema, existing design system. Building beside something is different from building fresh.
Questioning Rules
- Never ask what you can read. Check the repo, the files, the git history first — asking the user something the code answers is a tell that you did not look.
- Attach a default to every question: "Which auth? (default: Google SSO, since the repo already has it)". The user can answer with silence and still get moving.
- Push back once, concretely, when the brief has a real problem — then build what they asked if they confirm. One flag, not a debate.
- Stop at six questions. Beyond that you are stalling.
- No question that only serves your comfort. "What framework do you prefer?" is a decision you can make.
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.
- 27d ago First seen · 69 lines · 73 tokens per session scan A 0a1c32b16e0a
grill-the-brief is a skill published in the GitHub repository OneWave-AI/claude-skills (349 stars, last pushed 15d ago), licensed MIT. It adds 73 tokens to every session and 801 once invoked, about $0.0003 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-09-20.
Other skills, from other repositories
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.
agb-rechtswahl-schweizer-recht-rom-i
Für AGB Rechtswahl Schweizer Recht Rom I: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-rechtswahl-schweizer-recht-rom-i.