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/drvoss/everything-copilot-cli/councilnpx skills add drvoss/everything-copilot-cli --skill councilgit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/council)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/council"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/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 | $0.00045 | $0.01136 |
| Opus 5 | $0.00023 | $0.00568 |
| Sonnet 5 | $0.00009 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00114 |
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 today.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council
Convene four advisors for decisions under ambiguity:
- Architect — correctness, maintainability, long-term implications
- Skeptic — premise challenge, simplification, assumption breaking
- Pragmatist — shipping speed, user impact, operational reality
- Critic — edge cases, downside risk, failure modes
This is for decision-making under ambiguity, not code review, architecture design, or implementation planning.
When to Use
- A decision has multiple credible paths and no obvious winner
- You need explicit tradeoff surfacing before committing
- Conversational anchoring is a risk (you've been going in one direction too long)
- A go/no-go call would benefit from adversarial challenge
Examples: monorepo vs polyrepo · ship now vs hold for polish · feature flag vs full rollout · simplify scope vs keep strategic breadth
When NOT to Use
| Instead of council | Use |
|---|---|
| Verifying whether output is correct | evaluate-repository or direct review |
| Breaking a feature into implementation steps | planner / Plan Mode |
| Reviewing code for bugs | code-review skill |
| Straight factual questions | answer directly |
| Obvious execution tasks | do the task |
Workflow
1. Extract the real question
Reduce to one explicit prompt:
- What exactly are we deciding?
- What constraints matter?
- What counts as success?
If the question is vague, ask one clarifying question before convening.
2. Form the Architect position first
Before reading other voices, write down:
- Your initial position
- The three strongest reasons for it
- The main risk in your preferred path
This anchors the synthesis so it doesn't simply mirror external voices.
3. Launch three subagents in parallel
Each subagent gets: the decision question + compact context + strict role. No full conversation history.
# Copilot CLI tool call — launch 3 background task agents
task:
agent_type: "general-purpose"
name: "skeptic"
mode: "background"
prompt: |
You are the Skeptic on a four-voice decision council.
Question: [DECISION QUESTION]
Context: [COMPACT CONTEXT]
Challenge the framing. Question assumptions. Propose the simplest credible alternative.
Respond with:
1. Position — 1-2 sentences
2. Reasoning — 3 concise bullets
3. Risk — biggest risk in the status quo
4. Surprise — one thing the other voices may miss
Under 300 words. No hedging.
task:
agent_type: "general-purpose"
name: "pragmatist"
mode: "background"
prompt: |
You are the Pragmatist on a four-voice decision council.
[same structure — optimize for speed, simplicity, real-world execution]
task:
agent_type: "general-purpose"
name: "critic"
mode: "background"
prompt: |
You are the Critic on a four-voice decision council.
[same structure — surface downside risk, edge cases, failure modes]
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.
- today First seen · 149 lines · 45 tokens per session scan A 59681275258b
council is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 1,136 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
winui-design
Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…
winui-dev-workflow
Build and run workflow for WinUI 3 apps with WinApp CLI 0.6+ — project creation with winapp new, project-mode winapp run, BuildAndRun.ps1 analyzer integration, crash diagnosis, and prerequisites. Use when creating, building, running, or fixing build errors in a WinUI 3 project.
winui-packaging
MSIX packaging, code signing, and distribution for WinUI 3 apps — build for release, certificate generation (winapp cert generate), certificate trust, code signing (winapp sign), self-contained deployment, CI/CD with GitHub Actions, and Microsoft Store submission. Use when preparing for release, creating MSIX…
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
journey-template
Create new agentic journeys from app ideas. Generates README.md (learner walkthrough), PLAN.md (AI-readable spec), and app-specific skills for OSS deployments. Supports any stack (Node.js, Python, .NET, Java, Swift, Kotlin) and Azure service (Container Apps, AKS, Functions, App Service). USE FOR: new journey, scaffold…