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 Data-Wise/craft --skill grillgit clone --depth 1 https://github.com/Data-Wise/craftWrote 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/data-wise/craft/grill)<a href="https://agentmods.dev/skills/data-wise/craft/grill"><img src="https://agentmods.dev/badge/skills/data-wise/craft/grill.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.1 | $0.00115 | $0.01834 |
| Opus 5 | $0.00057 | $0.00917 |
| Sonnet 5 | $0.00023 | $0.00367 |
| Haiku 4.5 | $0.00012 | $0.00183 |
Grade B, and why
grill scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`docs/specs/*`, `commands/`, `~/.claude/settings.json` when relevant) — and PRE-ANSWER every How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill — Interrogate Before Building
Convergent counterpart to brainstorm. Brainstorm is divergent — it GENERATES options and
expands the space. Grill is convergent — it INTERROGATES a position to find gaps,
contradictions, and unresolved dependencies before you implement.
Use grill to stress-test a spec/plan (or a bare topic) until every load-bearing branch of the
design tree is resolved, then capture the locked decisions as a durable ledger that feeds
/craft:plan → /do.
Boundary With Adjacent Skills
| Skill | Role |
|---|---|
| grill (this) | Convergent — interrogates a position, captures a GRILL-*.md decision ledger |
brainstorm |
Divergent — generates options, captures a BRAINSTORM/SPEC |
prompt-refiner |
Sharpens a bare/quoted topic before grilling (default-on for topics) |
plan-orchestrator / --orch |
Turns the locked ledger + spec into an ORCHESTRATE artifact |
Inputs (flags owned by the commands/grill.md shim)
- target — spec/plan path, a quoted topic, or empty (detect from context).
- --bound N — stop after N decision branches (quick gate; used by orchestrate Step 0.5).
- --no-capture — skip writing a
GRILL-*file; return decisions inline (embedded callers). - --yes / --non-interactive — auto-accept every Recommended answer, zero AskUserQuestion prompts.
- --refine / --no-refine — refine a topic via
prompt-refinerbefore grilling (default-on for topics; skipped for a path). - --no-tests / --no-docs — suppress the auto-emitted test-plan / Documentation sections.
Procedure
Step 1: Resolve the target
- Path argument → load that artifact (spec/plan/ORCHESTRATE/diff) and interrogate it.
- Quoted topic → sketch a 3–5 bullet skeleton, show it, then interrogate the skeleton.
- Empty → detect from
.STATUS, branch name, and recent commits; confirm the target before grilling.
Step 2: Codebase-first sweep (read-then-confirm)
When the argument is a quoted/bare topic, run prompt-refiner on it first (default-on;
--no-refine skips). When the argument is a path, skip refine entirely.
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.
- 4d ago First seen · 124 lines · 115 tokens per session scan B 09004d615f6d
grill is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed 4d ago), licensed MIT. It adds 115 tokens to every session and 1,834 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
architecture-review
Conducts a comprehensive multi-perspective architecture review using ALL architecture team members. Use when the user requests "Start architecture review", "Full architecture review", "Review architecture for version X.Y.Z", "Conduct comprehensive review", or when they want assessment from multiple perspectives. Do…
specialist-review
Conducts a focused review from ONE specific specialist's perspective (e.g., Security Specialist, Performance Expert). Use when the user requests "Ask [specialist role] to review [target]", "Get [specialist]'s opinion on [topic]", "Have [role] review [code/component]", or when they want deep expertise in ONE specific…
hulde-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
hulde-chat
Use when you need to ask questions about a codebase or understand code using a knowledge graph for code review.
hulde-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase for code review.
hulde-review-code
Run a deep, language-profile-driven code review — quality, security, performance, maintainability, and modernization analysis with pluggable language support.