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 skills/guild-agents/guild/councilnpx skills add Guild-Agents/guild --skill councilgit clone --depth 1 https://github.com/Guild-Agents/guildWhat 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.00013 | $0.02261 |
| Opus 5 | $0.00006 | $0.01130 |
| Sonnet 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 2d 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.
- 2d 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 1mo ago), licensed MIT. It adds 13 tokens to every session and 2,261 once invoked, about $0.0001 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-31.
Other skills, from other repositories
using-pi-subagents
Operate pi-subagents jobs safely, including direct-work decisions, least-privilege tool selection, thinking-level selection, delegation, bidirectional messaging, parallel starts, timeout selection, waiting, cancellation, result handling, verification, and writer isolation.
mcp-development
Use this skill for Laravel MCP development only. Trigger when creating or editing MCP tools, resources, prompts, or servers in Laravel projects. Covers: artisan make:mcp- generators, mcp:inspector, routes/ai.php, Tool/Resource/Prompt classes, schema validation, shouldRegister(), OAuth setup, URI templates, read-only…
codebase-memory
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions…
add-channel-setup-guide
Add a new chat channel's layer-1 setup guide — the in-dashboard SetupGuide that walks a developer through connecting the channel itself (create app/bot → save credentials → install/verify → send first message) with live connection detection — in apps/dashboard, following the existing Slack, MS Teams, and Telegram…
add-channel-whats-next-onboarding
Add a new chat channel's layer-2 dashboard onboarding — the connected-state "What's next" / "FOR YOUR USERS" developer-rollout guide plus its connected details page — in apps/dashboard, following the existing Slack, MS Teams, and Telegram pattern. Use when a connected agent integration needs a per-provider "what's…
update-allowed-tools
Use when creating or editing a skill that uses Bash commands, file writes, or external tools and the allowed-tools frontmatter may be incomplete or carry entries that grant nothing.