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/local-council-execution)<a href="https://agentmods.dev/skills/hex/claude-council/local-council-execution"><img src="https://agentmods.dev/badge/skills/hex/claude-council/local-council-execution/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hex/claude-council/local-council-execution"><img src="https://agentmods.dev/badge/skills/hex/claude-council/local-council-execution.svg" alt="Reviewed on agentmods" width="80" 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.00098 | $0.01523 |
| Opus 5 | $0.00049 | $0.00762 |
| Sonnet 5 | $0.00020 | $0.00305 |
| Haiku 4.5 | $0.00010 | $0.00152 |
Grade A, and why
local-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 9d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Council Execution
When no external providers are configured, convene a council of independent Claude subagents instead. Each member answers from one role, blind to the others; you then synthesize the spread of perspectives.
Read this first — the honest framing is not optional. Every member is Claude. They share priors and training, so agreement between them is weak signal, not validation. The value here is independent angles and blind-spot coverage, not consensus. The output you produce MUST make this explicit and MUST NOT present member agreement as if it were cross-vendor corroboration.
Step 0: Confirm this is a local-council context (guard)
A local council is the fallback for when no real providers exist — it is not a default way to "use the council". Only proceed if one of these holds:
- The user explicitly passed
--local, or - There are no configured providers and the user accepted the local-council offer.
If you reached this skill any other way, verify providers are actually absent before spawning anything:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/query-council.sh --list-default 2>&1 | head -1
If that lists one or more providers and the user did not ask for --local,
STOP — do not spawn local members. Run the standard cross-vendor flow
(council-execution) so the real providers answer, since same-model role-play is
strictly weaker than the cross-vendor council the user can actually get.
Step 1: Resolve the roles
Source the libs once:
source ${CLAUDE_PLUGIN_ROOT}/scripts/lib/prompts.sh
source ${CLAUDE_PLUGIN_ROOT}/scripts/lib/roles.sh
If the user passed --roles, it already says both which lenses and how many
members — use it directly and skip the size question:
local_council_roles "<--roles value>"
Otherwise, ask the user how many members to convene, then resolve that many:
AskUserQuestion:
Question: "How many independent perspectives should the local council convene? More members means broader angle coverage, but a longer run and synthesis."
Header: "Members"
multiSelect: false
Options:
- "4 (Recommended) - balanced breadth"
- "3 - quick, three sharpest lenses"
- "5 - thorough"
- "6 - exhaustive"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 164 lines · 98 tokens per session scan A df27aec2f7c8
local-council-execution is a skill published in the GitHub repository hex/claude-council (705 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 1,523 once invoked, about $0.0005 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.
security-analyst
Threat-model and find vulnerabilities, with practical remediation.
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.