Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-tools/main/.claude/skills/council-router/SKILL.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-toolsWrote 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/namastexlabs/automagik-tools/council-router)<a href="https://agentmods.dev/skills/namastexlabs/automagik-tools/council-router"><img src="https://agentmods.dev/badge/skills/namastexlabs/automagik-tools/council-router/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/namastexlabs/automagik-tools/council-router"><img src="https://agentmods.dev/badge/skills/namastexlabs/automagik-tools/council-router.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.00031 | $0.00381 |
| Opus 5 | $0.00015 | $0.00191 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
council-router 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 12d 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.
This is a copy
100% identical to council-router — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Council Router
Routes reviews to specialized council members based on code context.
When to Invoke Council
- PR reviews with significant changes
- Architecture decisions or design proposals
- New dependency additions
- Security-sensitive code modifications
- Performance-critical path changes
- API surface changes
Routing Rules
| Context | Route To | Why |
|---|---|---|
| Security-sensitive code (auth, crypto, input validation) | @sentinel | Troy Hunt mindset - security-first |
| Performance-critical paths (hot loops, data processing) | @benchmarker | Matteo Collina - measure everything |
| New dependencies or abstractions | @questioner | Ryan Dahl - challenge assumptions |
| API changes (public interfaces, CLI) | @ergonomist | Sindre Sorhus - DX obsession |
| Deployment configs (Docker, K8s, CI/CD) | @operator, @deployer | Kelsey + Guillermo - ops reality |
| Observability code (logging, metrics, tracing) | @measurer, @tracer | Bryan + Charity - production debugging |
| Architecture decisions (module boundaries, patterns) | @architect | Linus - systems thinking |
| Complex abstractions (over-engineering risk) | @simplifier | TJ - elegant minimalism |
Usage
When a review context matches multiple categories, invoke multiple council members. Each member votes: APPROVE, REJECT, or MODIFY with rationale.
Agent Aliases
All council members are available as Claude agents:
- @questioner, @benchmarker, @simplifier
- @sentinel, @ergonomist, @architect
- @operator, @deployer, @measurer, @tracer
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.
- 12d ago First seen · 43 lines · 31 tokens per session scan A dfae59e92070
council-router is a skill published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 381 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to council-router, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
ai-slop-cleaner
Post-implementation cleanup that removes AI-generated bloat while preserving functionality. Runs pass-by-pass with test verification after each pass. Activate after kraken/spark complete a feature, or when a codebase needs hygiene work.
coding-standards
Universal coding standards - naming, formatting, error handling, immutability, SOLID principles.