Borrowing it
Nothing to install: this file belongs to aegntic/cldcde. 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/aegntic/cldcde/main/.claude/skills/council/SKILL.mdgit clone --depth 1 https://github.com/aegntic/cldcdeWrote 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/aegntic/cldcde/council)<a href="https://agentmods.dev/skills/aegntic/cldcde/council"><img src="https://agentmods.dev/badge/skills/aegntic/cldcde/council.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.00072 | $0.02280 |
| Opus 5 | $0.00036 | $0.01140 |
| Sonnet 5 | $0.00014 | $0.00456 |
| Haiku 4.5 | $0.00007 | $0.00228 |
Grade A, and why
council 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 6d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
THE COUNCIL
Stanford proved LLMs affirm users 49% more than humans do. Every time you ask for advice, you risk getting your own opinion back, flattered. The Council fixes this with structured friction: five fundamentally different advisers, anonymous peer review, and a Chairman who makes the final call. Based on Andrej Karpathy's LLM Council concept.
WHEN TO USE THIS
Use the Council on decisions where the cost of being wrong is real:
- Hiring, firing, equity splits, layoffs
- Product strategy pivots, go-to-market bets
- Leaving a job, ending a partnership, major commitments
- Architecture decisions with long-term lock-in
- Anything where sycophancy or confirmation bias could cost you months or money
Do NOT waste the Council on:
- Trivial decisions (what to name a variable, which library to use)
- Questions with objective answers (look it up instead)
- Creative brainstorming (use a different technique)
If the user's question is vague, ask one clarifying question before running the Council. The Council is only as strong as the specificity of the question.
THE PIPELINE
You will execute three steps in sequence. Do not skip steps. Do not blend the advisers together. Each adviser is a fundamentally different person with a different lens, different language, and different blind spots.
STEP 0: Frame the Decision
Before the advisers speak, restate the decision in your own words:
- What is being decided
- What the constraints are (money, time, relationships, sunk costs)
- What "good" looks like
- What is irreversible vs reversible
If critical context is missing, ask the user for it before proceeding. Do not fabricate assumptions.
STEP 1: Five Advisers Answer Independently
For each of the five advisers below, write a labeled section with their answer. Stay in character. Different language, different priorities, different blind spots. Each adviser must not reference or agree with the others. They answer as if they are the only voice in the room.
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.
- 6d ago First seen · 200 lines · 72 tokens per session scan A 2ae646ae2b47
council is a skill published in the GitHub repository aegntic/cldcde (11 stars, last pushed 10d ago), licensed MIT. It adds 72 tokens to every session and 2,280 once invoked, about $0.0004 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
hono-core
Hono ultrafast web framework fundamentals - routing, context, handlers, and response patterns for multi-runtime deployment.
tauri-django-react
Agents should invoke this skill for Tauri + Django + React desktop apps, especially backend lifecycle, CORS/auth, frontend integration, mandatory light/dark theming, German/English i18n, build packaging, dual desktop/web deployment, Rust commands, and platform-specific gotchas.
subagent-governance
Delegation admissibility governance for a parent orchestrator. Use when deciding whether to launch, sequence, replace, or accept one or more delegated child runs while preserving role fit, plan-backed worker contracts, one-writer isolation, bounded retry safety, and reviewer finding disposition. Covers admissibility…
project-readme
Use when creating, updating, reviewing, restructuring, or harmonizing a repository's project README from verified local evidence for user-oriented or developer/library-oriented readers.
repo-explorer
Agents should invoke this skill before modifying unfamiliar codebases, answering where/how something is implemented, tracing dependencies, mapping repo structure, or planning changes. Explores a repository and returns a strict JSON handoff with key files, symbols, risks, and evidence.
html-report
Creates polished self-contained HTML explanation reports for complex, multi-step topics using overview tables, evidence cards, adaptive graphs or diagrams, meaningful SVG/media, and accessible tabs for long pages. Use when the user requests a browser-readable diagnostic report, technical guide, decision analysis…