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/hex/claude-council/resultgit clone --depth 1 https://github.com/hex/claude-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/hex/claude-council/result)<a href="https://agentmods.dev/commands/hex/claude-council/result"><img src="https://agentmods.dev/badge/commands/hex/claude-council/result.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.00013 | $0.00396 |
| Opus 5 | $0.00006 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
result 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.
What it actually says
Manage background council jobs.
Argument Handling
$ARGUMENTSis empty orlist: list jobs$ARGUMENTSiscancel <job-id>: cancel that job- Otherwise: treat
$ARGUMENTSas a job id and fetch its result
List Jobs
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --jobs
Present the output as a table (job id, status, created). If empty, tell the
user there are no background council jobs and that /claude-council:ask
with --async starts one.
Cancel a Job
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --cancel=<job-id>
Relay the confirmation verbatim.
Fetch a Result
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --result=<job-id>
- Exit 0: stdout is the output file path. Read the file and display its
content VERBATIM (same rules as the council-execution skill: no
reformatting, no summarizing). Then complete the synthesis under the
## Synthesisheader following${CLAUDE_PLUGIN_ROOT}/prompts/synthesis.md. - Exit 2: the job is still running. Tell the user and suggest re-running
/claude-council:result <job-id>in a little while. - Exit 1: unknown, failed, or cancelled job. Show the script's stderr, which includes the tail of the job log for failures.
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 · 47 lines · 13 tokens per session scan A 7aa2bfe5374a
result is a command published in the GitHub repository hex/claude-council (673 stars, last pushed 8d ago), licensed MIT. It adds 13 tokens to every session and 396 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-30.
Other commands, from other repositories
grok-files
List, prune, or gc Grok (xAI) uploaded files. Cleanup for bridge-owned uploads only.
help
Show how to use deliberation here - what each command does, when to reach for it, and real prompts you can paste right now. Read-only.
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-all
Ask GPT, Gemini, Grok, and OpenRouter in parallel for independent second opinions.
ask-gemini
Ask Gemini for a single-shot second opinion.