Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add hex/claude-council/plugin install 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/skills/hex/claude-council/council-execution)<a href="https://agentmods.dev/skills/hex/claude-council/council-execution"><img src="https://agentmods.dev/badge/skills/hex/claude-council/council-execution.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.00066 | $0.00588 |
| Opus 5 | $0.00033 | $0.00294 |
| Sonnet 5 | $0.00013 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
council-execution 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council Query Execution
Step 1: Run Query and Save to File
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --providers=gemini,openai -- "Your question"
This outputs the path to the saved file (e.g., .claude/council-cache/council-1734567890.md).
Flag syntax: Use = with no spaces: --providers=gemini,openai
CRITICAL: Always place -- before the prompt to prevent prompt text containing dashes from being parsed as flags.
Run this Bash call with timeout: 600000 (ten minutes). The Bash tool's
two-minute default is shorter than a slow council round, and inside tmux a
provider failure makes the streaming pane offer the user a retry for
COUNCIL_RETRY_WAIT seconds (default 45) and then runs another provider round
if accepted. A call cut off mid-run loses the whole transcript, the answers
that did arrive included.
Step 2: Read and Display the Output VERBATIM
Use the Read tool to read the output file path returned by Step 1.
CRITICAL: Display the file content EXACTLY as written. Do NOT:
- Reformat or reinterpret any text
- Add your own headers or structure
- Summarize or abbreviate responses
- Skip any lines including separator lines (
---)
Simply copy-paste the entire file content into your response.
Step 3: Complete the Synthesis Section
The file ends with a ## Synthesis header. Read
${CLAUDE_PLUGIN_ROOT}/prompts/synthesis.md and write your synthesis UNDER
that header following its structure (Consensus / Divergence / Recommendation)
and calibration rules.
Step 4: Notify User of Saved Output
After displaying the synthesis, tell the user:
(use this emoji 💾) Full output saved to
.claude/council-cache/council-TIMESTAMP.md(use the actual filename)
This lets them review the complete responses later.
Output Format: Provider Names
The output file uses emoji prefixes to visually distinguish providers. Preserve this format when displaying results:
| Provider | Prefix |
|---|---|
| Gemini | 🟦 Gemini |
| OpenAI | 🔳 OpenAI |
| Grok | 🟥 Grok |
| Perplexity | 🟩 Perplexity |
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.
- 8d ago First seen · 66 lines · 66 tokens per session scan A 4df86067c861
council-execution is a skill published in the GitHub repository hex/claude-council (699 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 588 once invoked, about $0.0003 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
architect
System design, tradeoffs, and complex technical decisions.
scope-analyst
Catch ambiguities and hidden requirements before planning.
code-reviewer
Find bugs, security holes, and maintainability issues in a diff or file.
plan-reviewer
Validate that a work plan is executable before work starts.
researcher
Research external libraries, APIs, and best practices, with evidence.
security-analyst
Threat-model and find vulnerabilities, with practical remediation.