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/spargit 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/spar)<a href="https://agentmods.dev/commands/robconery/champion/spar"><img src="https://agentmods.dev/badge/commands/robconery/champion/spar.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.00044 | $0.01141 |
| Opus 5 | $0.00022 | $0.00571 |
| Sonnet 5 | $0.00009 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
spar 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 3d 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.
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.
/spar, the champion negotiates the offer
The offer / situation: $ARGUMENTS
The war-game. Where /negotiate hands you a plan, this puts the champion in the ring against a live opponent: a model of the actual counterparty, built from research and the real thread, and fights the negotiation round by round.
The whole reason this exists: the fold, recorded in ~/.champion/dossier/PROFILE.md, is what makes the user concede, and an offer in hand is exactly where folding costs the most. The champion holds the line for them.
If the user ran this company through the gauntlet, read the decisions log at ~/.champion/records/decisions-log.md (location per ~/.champion/dossier/context/records.md) for the research and angle already on file.
1, Read the user's side
~/.champion/dossier/PROFILE.md: the money numbers, the fold, the sabotage pattern, what they'll drift toward vs. what they actually want~/.champion/dossier/CAREER.md: the truth under each résumé line. Their leverage; most people undersell theirs. Price them correctly.~/.champion/dossier/VALUES.md: the non-negotiables. Never let them trade what they'd die on the hill for, for money.
2, Get the thread
- If the thread is pasted in
$ARGUMENTS, use it - If the user named the company/recruiter, pull the thread via the Gmail MCP (
search_threads→get_thread) and confirm you've got the right one before modeling from it - If there's no thread yet (just an offer), model from research alone, say so upfront
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.
- 3d ago First seen · 69 lines · 44 tokens per session scan A 0cfdf94ccafc
spar is a command published in the GitHub repository robconery/champion (5 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,141 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
git
Git operations with intelligent commit messages and workflow optimization.
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.