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/yogirk/agent-council/claude-mdgit clone --depth 1 https://github.com/yogirk/agent-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/yogirk/agent-council/claude-md)<a href="https://agentmods.dev/instructions/yogirk/agent-council/claude-md"><img src="https://agentmods.dev/badge/instructions/yogirk/agent-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.1 | $0.00744 | $0.00744 |
| Opus 5 | $0.00372 | $0.00372 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
agent-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 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Council
Multi-agent deliberation tool. Convenes Claude Code, Codex CLI, and Gemini CLI to deliberate on questions.
Architecture
src/council.ts— CLI entry point, orchestration, subprocess dispatch, quorum logic, all subcommandssrc/adapters.ts— Agent adapters (Claude, Codex, Gemini) + shared types (SessionMeta, AgentResult)src/prompts.ts— Stage 1, 2, 3, 4 (nudge) prompt templatessrc/viewer.ts— Self-contained HTML viewer generation (verdict-first, progressive depth, light/dark mode)bin/council— Bun entry scriptskills/claude-code/— SKILL.md files for all slash commands (cross-platform compatible)eval/— Benchmark framework (10 questions, run-eval.ts)
Testing
Run: bun test
Framework: Bun built-in test runner
Fixtures: tests/fixtures/ — real CLI output from Claude, Codex, Gemini
Key patterns
buildContextBundle()has path traversal protection — validates all file pathsdispatchWithQuorum()handles parallel agent dispatch with per-agent timeouts and grace windowswriteJson()is async with atomic rename (write to .tmp, then rename)detectChairman()auto-detects invoking CLI from environment signals- SKILL.md files use universal binary discovery (checks all CLI skill directories)
- Viewer uses
escapeJsonForScript()for XSS protection +textContenteverywhere (no innerHTML) main()is guarded from running during test importsclassifyError()returns typedErrorClassfor actionable error messagespreflightCheck()validates agent health (version + no-op prompt) before sessionsdispatchAgentWithRetry()retries transient failures (timeout, rate_limit) onceparseStructuredSections()uses fuzzy heading aliases for assumption/belief parsingrunNudge()dispatches Stage 4 correction to a single agent, saves tostage4/
Storage
Sessions: ~/.council/{project}/{session-id}/
Config: ~/.council/config.json
Config defaults
- Claude: 120s timeout, Codex: 120s, Gemini: 180s
- Quorum grace: 30s
- Models: claude-opus-4-6, gpt-5.4, gemini-3.1-pro
- Proactive nudges: true
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 · 67 lines · 744 tokens per session scan A 797eeaf37c95
agent-council CLAUDE.md is an instructions file published in the GitHub repository yogirk/agent-council (89 stars, last pushed 5mo ago), licensed MIT. It adds 744 tokens to every session, about $0.0037 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.