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/dorukanc/harness-council/spawngit clone --depth 1 https://github.com/dorukanc/harness-councilWrote 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/dorukanc/harness-council/spawn)<a href="https://agentmods.dev/commands/dorukanc/harness-council/spawn"><img src="https://agentmods.dev/badge/commands/dorukanc/harness-council/spawn.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.00017 | $0.00116 |
| Opus 5 | $0.00009 | $0.00058 |
| Sonnet 5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
spawn 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.
What it actually says
Spawn a council worker for: $ARGUMENTS
Use the council CLI or MCP:
council spawn --role code $ARGUMENTS
If the user intent is exploration/research, use --role explore.
If implementation/coding, use --role code.
If review-only, use --role review.
Report the job id, status, and how to council result / council attach.
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 · 18 lines · 17 tokens per session scan A feba6caff7d4
spawn is a command published in the GitHub repository dorukanc/harness-council (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 116 once invoked, about $0.0001 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
setup
Configure deliberation with Codex (GPT), Gemini, Grok, and OpenRouter MCP servers.
analyze
Analyze recent runs (latency, tokens, verdict agreement) and suggest model/reasoning/fanout tuning.
ask-gpt
Ask GPT (Codex) for a single-shot second opinion.
ask-grok
Ask Grok (xAI) for a single-shot second opinion.
doctor
Check deliberation's health - config, provider CLIs, sessions/debug, and path drift - and suggest fixes. Read-only; never changes anything.
search
Search X (Twitter) and the web in real time with Grok, then summarize with sources.