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 skills add Guild-Agents/guild --skill councilgit clone --depth 1 https://github.com/Guild-Agents/guildWrote 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/guild-agents/guild/council)<a href="https://agentmods.dev/skills/guild-agents/guild/council"><img src="https://agentmods.dev/badge/skills/guild-agents/guild/council/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/guild-agents/guild/council"><img src="https://agentmods.dev/badge/skills/guild-agents/guild/council.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.00013 | $0.02261 |
| Opus 5.5 | $0.00005 | $0.00904 |
| Sonnet 5.5 | $0.00003 | $0.00452 |
| Haiku 4.5 | $0.00001 | $0.00226 |
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 1mo 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council
Convenes a council of specialized agents to debate an important decision. Each agent contributes their independent perspective and the result is a synthesis of the debate.
Agents are invoked IN PARALLEL using the Task tool to obtain independent perspectives without bias.
When to use
- Before making an important architectural decision
- To evaluate the scope of a feature with multiple perspectives
- To decide whether to address technical debt and how to prioritize it
- When you need multiple viewpoints on a complex problem
Usage
/council [question or decision to debate]
Optionally you can specify the type: /council architecture [question]
Council Types
1. Council Architecture
Participants: Tech Lead + Advisor + Developer When it applies: Decisions about architecture, patterns, large refactors, new technologies
Invokes all 3 agents IN PARALLEL using Task tool:
- Task 1: Reads
.claude/agents/tech-lead.md— architecture and technical coherence perspective - Task 2: Reads
.claude/agents/advisor.md— feasibility and business risk perspective - Task 3: Reads
.claude/agents/developer.md— implementability and pragmatism perspective
2. Council Feature-Scope
Participants: Advisor + Developer + Tech Lead When it applies: Defining feature scope, prioritizing functionality, evaluating product proposals
Invokes all 3 agents IN PARALLEL using Task tool:
- Task 1: Reads
.claude/agents/advisor.md— domain and strategic vision perspective - Task 2: Reads
.claude/agents/developer.md— implementability and pragmatism perspective - Task 3: Reads
.claude/agents/tech-lead.md— technical feasibility and effort perspective
3. Council Tech-Debt
Participants: Tech Lead + Developer + Code Reviewer When it applies: Deciding whether to address technical debt, planning refactors, evaluating codebase quality
Invokes all 3 agents IN PARALLEL using Task tool:
- Task 1: Reads
.claude/agents/tech-lead.md— architectural impact perspective - Task 2: Reads
.claude/agents/developer.md— implementation cost perspective - Task 3: Reads
.claude/agents/code-reviewer.md— quality and risk perspective
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.
- 1mo ago First seen · 234 lines · 13 tokens per session scan A 90d8f25a4234
council is a skill published in the GitHub repository Guild-Agents/guild (4 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 2,261 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
ccs
Search local Claude Code, Codex, and Cursor user-prompt history (read-only). Use when you need a past prompt, want to grep coding-agent session text, or pipe prompt history as JSON.
nodejs
Use when building or operating a plain Node.js / Express 5 backend service: project layout, async correctness, central error middleware, fail-fast config, graceful shutdown on SIGTERM. NOT DI modules/providers/guards (that is nestjs), NOT the type system or tsconfig (that is typescript), NOT REST contract design (that…
save-learning
Saves user instructions as persistent learnings for future sessions. Use when the user says 'remember this', 'always do X', 'from now on', 'never do Y', or gives any instruction they want persisted across sessions. Proactively suggest when the user states a preference, convention, or rule they clearly want followed in…
configure-pi-sync
Explain @narumitw/pi-sync settings and guide safe setup through its existing manager. Use when the user asks how to configure pi-sync.json, choose Git, WebDAV, R2, or S3 storage, select synced content, understand automatic controls, or recover unsupported settings. This skill provides guidance only, not settings edits…
web-access
A method for handling difficult web tasks across search, page fetching, and a real browser. It covers sites that need login sessions, dynamic pages, anti-bot handling, or exploration before their structure is understood.
skill-creator
A skill for creating or improving reusable instructions for an agent. It covers capturing the intended workflow, writing a draft, testing it, and refining its trigger description.