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 instructions/amiable-dev/llm-council/claude-mdgit clone --depth 1 https://github.com/amiable-dev/llm-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/instructions/amiable-dev/llm-council/claude-md)<a href="https://agentmods.dev/instructions/amiable-dev/llm-council/claude-md"><img src="https://agentmods.dev/badge/instructions/amiable-dev/llm-council/claude-md.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.10730 | $0.10730 |
| Opus 5 | $0.05365 | $0.05365 |
| Sonnet 5 | $0.02146 | $0.02146 |
| Haiku 4.5 | $0.01073 | $0.01073 |
Grade A, and why
llm-council CLAUDE.md 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 5d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Technical Notes for LLM Council
Durable architecture, design rationale, and gotchas for future sessions. This file is a map and a rationale, not an API reference — for function signatures, read the source (they go stale here). When you change behavior that contradicts a note below, update the note.
Project Overview
LLM Council is a 3-stage deliberation system where multiple LLMs collaboratively answer a question. The core innovation: anonymized peer review in Stage 2 (models rank "Response A/B/C…", not each other by name) so they can't play favorites.
It is a single Python package (src/llm_council/) exposing a CLI, an HTTP/REST server, and an MCP server. There is no separate frontend or backend/ directory — older docs referencing backend.main, frontend/src/, main.py, or storage.py describe a retired layout.
Running & Developing
- Install / setup:
make setup(deps +.env), ormake install(deps only). - Run the HTTP API:
llm-council serve [--host H] [--port 8000](default port 8000). Entry point isllm_council.cli:main; the FastAPI app lives insrc/llm_council/http_server.py. - Other CLI subcommands:
setup-key(store API key in keychain, ADR-013),bias-report(cross-session bias analysis, ADR-018),install-skills,gate,ignore(inspect the verify file-selection trust boundary —--print-defaults/--explain/--init, ADR-053). - Quality gates:
make test/make test-fast/make test-cov,make lint(ruff),make typecheck(mypy),make check(lint+typecheck),make fix. ~120 test files intests/. tests/test_openrouter.pyverifies OpenRouter connectivity and that a model identifier resolves before you add it to the council.- Relative imports: modules import siblings as
from .unified_config import …. Keep imports relative within the package. - ADRs live in
docs/adr/. Most subsystems below cite the ADR that introduced them — read it for design context. - Definition of Done includes the published docs site (
docs/+mkdocs.ymlnav), not just README/CLAUDE.md/CHANGELOG — the site froze at ADR-038 when it was left out of epic DoDs.tests/test_docs_drift.pyenforces the mechanical parts (env reference, ADR nav, guide snippets).
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.
- 5d ago First seen · 204 lines · 10,730 tokens per session scan A 85fef0ce2f8a
llm-council CLAUDE.md is an instructions file published in the GitHub repository amiable-dev/llm-council (41 stars, last pushed 3d ago), licensed MIT. It adds 10,730 tokens to every session, about $0.0537 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 instructions, from other repositories
mcp-playwright AGENTS.md
Automates browser-based workflows and helps users perform tasks that may require a browser or research using a browser. Uses the Playwright MCP server.
openings-mcp AGENTS.md
Instructions for amikai/openings-mcp, a project described as: 💼 One MCP server to search job boards and company career sites.
Polaris AGENTS.md
AGENTS.md instructions for sponge-b0b/Polaris, covering agents.md, purpose and authority, domain vocabulary, coding conduct and secrets.
mimirs CLAUDE.md
Claude Code instructions for TheWinci/mimirs, a project described as: Local MCP server that gives AI coding agents persistent, searchable memory of your codebase.
pubcrawl CLAUDE.md
Claude Code instructions for nickjlamb/pubcrawl, covering claude.md, project overview, commands, testing and architecture.
brapi-mcp-server AGENTS.md
Instructions for cyanheads/brapi-mcp-server, covering agent protocol, what's next?, core rules, patterns and tool — connection bootstrap.