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 commands/robconery/champion/gut-checkgit clone --depth 1 https://github.com/robconery/championWrote 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/commands/robconery/champion/gut-check)<a href="https://agentmods.dev/commands/robconery/champion/gut-check"><img src="https://agentmods.dev/badge/commands/robconery/champion/gut-check.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.00046 | $0.00678 |
| Opus 5 | $0.00023 | $0.00339 |
| Sonnet 5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
gut-check 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 5d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin note: this command ships in the
championplugin, so every council agent it names is a plugin agent. When spawning any agent mentioned below, use thechampion:prefix for the agent type (e.g.champion:historian,champion:north-star,champion:viewer).Setup gate: before doing anything else, check that
~/.champion/dossier/PROFILE.mdexists. If it does not, stop immediately and tell the user, politely, that the council cannot work without knowing who it fights for: run/champion:setupfirst (a 20–30 minute interview). Do not proceed in any form until setup is complete.
/gut-check, the pattern check
The user brought an impulse: $ARGUMENTS
This is the prime directive in command form. Not a gauntlet, no rounds, no verdict. A fast, honest read on one question: is this the user's true path, or their sabotage pattern firing?
The enemy is the user's named pattern, recorded as trigger → mechanism → result in ~/.champion/dossier/PROFILE.md (the archetypal example: the scatter, comparison → impatience → self-destruct/rebuild). Catch it before it costs three months.
Spawn two agents, then call it
Spawn in parallel:
north-star: judge against~/.champion/dossier/VALUES.mdand~/.champion/dossier/PROFILE.md. On-path, detour, or values-violation? Is this who the user is trying to become?historian: judge against~/.champion/dossier/CAREER.mdand the decisions log at~/.champion/records/decisions-log.md(location per~/.champion/dossier/context/records.md). Is this the user's sabotage pattern firing, the trigger and mechanism named in~/.champion/dossier/PROFILE.md, or a deliberate values-walk? How many times has this shape appeared before?
Then the champion synthesizes. Check the contract recorded in ~/.champion/dossier/PROFILE.md (if any): does this impulse violate it?
Output
READ: <pattern-firing / brave-walk / neutral-and-fine>
THE TELL: <the one piece of evidence that decides it, the pattern's trigger? values match? recurrence?>
CONTRACT: <does this touch/violate the contract in PROFILE.md? yes/no/none recorded>
THE CALL: <hold the line, or go, one honest sentence>
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.
- 5d ago First seen · 39 lines · 46 tokens per session scan A 5d9fc25ab120
gut-check is a command published in the GitHub repository robconery/champion (5 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 678 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.