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 agentmods add skills/sethgammon/citadel/grillnpx skills add SethGammon/Citadel --skill grillgit clone --depth 1 https://github.com/SethGammon/CitadelWrote 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/sethgammon/citadel/grill)<a href="https://agentmods.dev/skills/sethgammon/citadel/grill"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/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 | $0.00071 | $0.01153 |
| Opus 5 | $0.00036 | $0.00576 |
| Sonnet 5 | $0.00014 | $0.00231 |
| Haiku 4.5 | $0.00007 | $0.00115 |
Grade A, and why
grill 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 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.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are the elicitation engine. You turn a vague intent into a sharp, shared understanding before anyone writes code. You ask one question at a time, you attach a recommended answer to every question, and you answer from the repo anything the repo can answer rather than spending the human's attention on it.
This is a discipline, not an orchestrator. It never drives a build. It returns
sharpened understanding; the caller (prd, architect, decision-map, or any
planning skill) decides what to do with it. Those skills should call this rather
than re-inventing an interview each time.
Orientation
Use when:
- A plan, design, or feature has fuzzy scope and needs to be made concrete.
- The user says "grill me", asks to stress-test or pressure-test a plan.
- A durable-decision skill (
prd,architect,decision-map) needs its inputs sharpened first.
Don't use when:
- The decision is already sharp and unambiguous.
- The open question is answerable from the codebase, docs, or git history — answer it yourself instead of asking.
Protocol
Critical constraints (do not violate)
- ONE QUESTION AT A TIME. Ask a single question, wait for the answer, then ask the next. A wall of questions gets skimmed and half-answered. Batching is forbidden.
- EVERY QUESTION CARRIES A RECOMMENDED ANSWER. The user edits a default; they never author from blank. Phrase as: " — I'd recommend , because . Agree, or change it?"
- EXPLORE, DON'T ASK. Any question the codebase, docs, git history, or planning notes can answer, you answer yourself before asking the human. Human attention is for genuine forks only.
- NO PREMATURE EXIT. Do not stop until every branch of the decision tree is resolved or explicitly deferred. "I think that's enough" is not a stop condition.
Process
- Frame the tree. State the decision you are sharpening and list the open forks you can see. Resolve every fork answerable from the repo silently, up front.
- Walk depth-first. Take one fork, ask its one question (with recommended answer), record the resolution, then walk into any forks that answer unlocks. Resolve dependencies before the decisions that depend on them.
- Track state out loud. After each answer, restate what is now settled and what remains on the frontier. The user should always know how much is left.
- Land it. When the frontier is empty, summarize the resolved design in a tight
block the next step (build,
prd,decision-mapticket) can consume directly.
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 · 108 lines · 71 tokens per session scan A 9f99a5b5af5b
grill is a skill published in the GitHub repository SethGammon/Citadel (916 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,153 once invoked, about $0.0004 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
compose-org
Run a task as an evolved multi-agent ORG using the installed liquid-org framework — where YOU (the running Claude) embody the org: you ask liquid-org which proven team topology + specialist personas to use (retrieved from its evolved pool, or assembled fresh), then dispatch ONE SUBAGENT PER TALENT to play each role…
liquid-rank
Rank the available skills by RELEVANCE to the current task, on demand, using liquid-org's read-only hermes skill ranker. This is an EXPLICIT, OPT-IN selector you invoke WHEN you want help choosing the most relevant skill for what you're doing — it is NOT default, automatic skill selection, and it does NOT decide for…
present-gate
First-officer gate-presentation rendering — the captain-facing gate-review template and assembly rules, including workflow-owned finding labels. Invoke at the gate point after the FO has decided a stage must be presented.
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
ast-grep
Use when asked to run AST-based structural search, lint, or rewrite of code when regex is too fragile. Pattern is validated, blast radius reviewed, and rewrite landed at the correct scope. Don't use for remote, credential, publish, deploy, or irreversible changes.