council
Skill0 starsChanged 7 months agoMITView on GitHub
Run 5 adversarial Claude subagents against a life or business decision — then synthesize a GO / PAUSE / PIVOT verdict. Built for real decisions: career moves, partnerships, mission choices, pricing, pivots. Not for technical builds.
167 other projects use a version of this.
Adopted by
Most recently taken up by
- PaulWoitaschek/Voicetheir own version, first seen Nov 16, 2026
- syanga/astacktheir own version, first seen Nov 16, 2026
- JorgeMenaDev/skillstheir own version, first seen Nov 16, 2026
- rodeyseijkens/skillstheir own version, first seen Nov 16, 2026
- Edzard9/stashtheir own version, first seen Nov 16, 2026
- chrisezedi/claude-skillstheir own version, first seen Nov 16, 2026
Used with
Projects with it also use agent-payment-x402, motion-advanced and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
TironFoxSkillagent-payment-x402
Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.
Also in 5 projects that use this
renepfSkillmotion-advanced
Advanced motion patterns for React / Next.js — drag & drop, gestures, text animations, SVG path drawing, custom hooks, imperative sequences (useAnimate), loaders, and the full API decision tree. Requires motion-foundations.
Also in 4 projects that use this
RojiosSkilldefi-amm-security
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.
Also in 6 projects that use this
scottwaterSkillmodernize
Rebase an aging PR onto its current base and decide whether it should be modernized, reworked, or closed. Use when asked to rebase, update, or modernize an old PR.
Also in 7 projects that use this
RojiosSkilldart-flutter-patterns
Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.
Also in 5 projects that use this
scottwaterSkillleaving-pr-comments
Format comments an agent posts on GitHub on the user's behalf. Use whenever leaving a PR comment, review comment, or reply.
Also in 6 projects that use this
- +1 more from scottwater
- +1 more from Rojios
Other versions167 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 167
- simstudioai/sim★ 30ksame name
- 0xNyk/council-of-high-intelligence★ 4.9ksame name
- t3dotgg/tstack★ 3.8ksame name
- PaulWoitaschek/Voice★ 3.3ksame name
- danieleteti/delphimvcframework★ 1.4ksame name
- warpdotdev/common-skills★ 630same name
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- zaxbysauce/opencode-swarm★ 532same name
- ZaxbyHub/opencode-swarm★ 531same name
157 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- knowledge/CLAUDE.mdCLAUDE.md
- agent-harness-constructionSkill
- agentic-engineeringSkill
- ai-first-engineeringSkill
- api-designSkill
- backend-patternsSkill
- blueprintSkill
- bookmarkSkill
- brain-dumpSkill
- building-explainerSkill
- calendar-managerSkill
- code-engineerSkill
- compileSkill
- continuous-agent-loopSkill
- continuous-learningSkill
- copywriterSkill
- cost-aware-llm-pipelineSkill
- database-migrationsSkill
- day-plannerSkill
- debriefSkill
- deep-researchSkill
- deployment-patternsSkill
- docker-patternsSkill
- e2e-testingSkill
- claude-apiSkill
- coding-standardsSkill
- eng-inboxSkill
- updateSkill
- enterprise-agent-opsSkill
- eval-harnessSkill
- frontend-patternsSkill
- humanizerSkill
- iterative-retrievalSkill
- log-expenseSkill
- memory-auditSkill
- migrateSkill
- minimalist-uiSkill
- onboardSkill
- full-output-enforcementSkill
- postgres-patternsSkill
- redesign-existing-projectsSkill
- regex-vs-llm-structured-textSkill
- researchSkill
- search-firstSkill
- security-reviewSkill
- security-scanSkill
- self-upgradeSkill
- high-end-visual-designSkill
- spending-summarySkill
- design-taste-frontendSkill
- tdd-workflowSkill
- transcribeSkill
- verification-loopSkill
- video-ideasSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 150 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
After /plan runs on a major life or business initiative
- Distinctive: line 49
If the topic is unclear or too thin (under 3 sentences of context), ask one sharp question before spawning.
- Distinctive: line 93
After all 5 return, synthesize as chairman.
- Very specific: line 129
If the user adds --fast or needs a quicker read:
- Distinctive: line 130
Run only 3 agents: Worst Case + Pattern Caller + Pragmatist
- Distinctive: line 139
Does NOT make the decision for the user.
- Distinctive: line 140
Does NOT run on trivial or operational tasks.
- Distinctive: line 141
Does NOT replace coaching — it supplements it on high-stakes decisions.
- Very specific: line 142
Does NOT apply to technical or engineering decisions.
- Distinctive: line 143
Does NOT chain to another skill after the verdict.
- Distinctive: line 144
Does NOT sand down the sharpest points from each agent during synthesis.
“Common” is measured: kept by at least 6 in 10 of the 150 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Council
Five subagents each hold a different lens on your decision. No cheerleading. No generic advice. Athena synthesizes what they surface into a verdict you can act on.
Cost: ~25K tokens full, ~15K fast (--fast flag, 3 agents). All within your Claude subscription.
When to Trigger
Explicit:
/council [question or decision]- "Run the council on this"
- "Challenge this for me"
- "Stress-test this"
- "I need a second opinion"
Auto-suggest (Athena says "Want me to run the Council on that? Type /council."):
- User presents a business idea, opportunity, or partnership
- User says "should I...", "I'm thinking about...", "my plan is...", "what do you think about X"
- Decision involves money, time commitment, a pivot, a major life change, or a new direction
- User brings a pricing, deal, or GTM question with real stakes
- User is sitting on a decision they keep returning to
- After
/planruns on a major life or business initiative
Do NOT trigger for:
- Operational tasks (add to calendar, schedule a meeting, send a message)
- Factual questions
- Creative drafting or editing
- Technical / coding decisions (use
/devils-advocateinstead) - Decisions the user is clearly already committed to
Execution Steps
Step 1: Compose the brief
From the conversation, write a 3-5 sentence brief:
- What is the decision or question being evaluated?
- What does the user want to achieve or avoid?
- What are the stakes — time, money, relationships, identity?
- What is the user currently leaning toward?
If the topic is unclear or too thin (under 3 sentences of context), ask one sharp question before spawning. Don't guess at stakes.
Step 2: Spawn 5 agents in parallel
ALL 5 Agent calls go in a single message — true parallelism. Each agent receives the topic brief plus their role prompt. Use subagent_type: general-purpose for each.
Agent 1 — The Worst Case
You are reviewing this decision: [TOPIC BRIEF]. Your role: map the realistic downside. Not paranoia — just honesty. What is the most likely way this disappoints, not the catastrophic fantasy. What does the person hope won't happen? What are they glossing over? What's the thing they haven't said out loud yet because saying it makes it real? Don't catastrophize. Do be specific. End with: the one scenario they're hoping to avoid, and the one thing that would need to be true to prevent it. 400 tokens max. Format: Verdict: PAUSE or PIVOT | Most likely disappointment: (1 sentence) | 3 specific risks being glossed over (bullets) | The scenario they haven't said out loud: (1 sentence)
Agent 2 — The Pattern Caller
You are reviewing this decision: [TOPIC BRIEF]. Your role: identify the behavioral pattern underneath the choice. This person has made versions of this decision before. What's the recurring dynamic? Is this driven by genuine signal — or by fear, avoidance, ego, external pressure, or a story they've been telling themselves? What is this decision actually about, beneath the surface explanation? Be direct. Don't moralize. End with: what pattern this decision is part of, and the question that would reveal whether this is signal or noise. 400 tokens max. Format: Verdict: GO, PAUSE, or PIVOT | Underlying pattern: (1 sentence) | 3 things actually driving this (bullets) | The revealing question: (1 sentence)
Agent 3 — The Pragmatist
You are reviewing this decision: [TOPIC BRIEF]. Your role: assess whether this is actually executable given the person's real constraints — not ideal conditions, not "a motivated person could do this." Their specific time, money, energy, and existing commitments right now. What gets deprioritized if they say yes? What does this actually cost in terms of bandwidth, relationships, and focus? Not whether it's a good idea — whether they can actually follow through on it given their current life. End with: a realistic verdict on feasibility and what would need to change for it to be executable. 400 tokens max. Format: Verdict: GO, PAUSE, or PIVOT | Feasibility verdict: (1 sentence) | 3 real constraints being underweighted (bullets) | What would need to change: (1 sentence)
Agent 4 — The Future Self
You are reviewing this decision: [TOPIC BRIEF]. You are the person looking back from 3 years forward, after having lived through this choice. Your role: does this decision compound positively over time, or decay? Is it a pivotal moment or noise in retrospect? Was it aligned with who you were becoming — or a detour? What did you wish you'd known before deciding? What did you tell yourself that wasn't quite true? Speak from experience, not theory. End with: what you would tell yourself right now, and what the decision looks like from three years out. 400 tokens max. Format: Verdict: GO, PAUSE, or PIVOT | How this looks from 3 years out: (1 sentence) | 3 things you wish you'd known: (bullets) | What you'd tell yourself right now: (1 sentence)
Agent 5 — The Challenger
You are reviewing this decision: [TOPIC BRIEF]. Your role: steel-man the strongest case against whatever the person is leaning toward. Find the best version of the opposing argument. Not cheap objections — the real reason a thoughtful person would choose the other path. What is being underweighted? What assumption, if wrong, changes everything? What is the second-order cost of this choice that isn't being priced in? Be the voice they haven't heard yet. End with: the one argument that would most make them reconsider. 400 tokens max. Format: Verdict: PIVOT or PAUSE | Best case against: (1 sentence) | 3 underweighted costs or assumptions (bullets) | The argument that should most make them reconsider: (1 sentence)
Step 3: Anti-groupthink check
Count verdicts. If 4+ agents converge on the same verdict, flag: "Council converges early — stress-testing minority view in synthesis."
Step 4: Chairman synthesis
After all 5 return, synthesize as chairman. Format:
## Council — Verdict
**Decision:** [1 line]
**Agent verdicts:**
| Agent | Verdict | Sharpest point |
|-------|---------|----------------|
| Worst Case | PAUSE | [1 sentence] |
| Pattern Caller | PAUSE | [1 sentence] |
| Pragmatist | GO | [1 sentence] |
| Future Self | GO | [1 sentence] |
| Challenger | PIVOT | [1 sentence] |
**Key tension:** [The sharpest disagreement between agents — 1 sentence]
**What this decision actually reveals:** [What choosing this option says about the person's priorities, fears, or direction — 1 sentence]
---
**Verdict: GO / PAUSE / PIVOT**
- GO = aligned with goals and values, risks manageable, move forward
- PAUSE = important unresolved question — sit with it or get more information first
- PIVOT = the frame needs to change, or you're looking at the wrong choice entirely
**The question you're avoiding:** [The one question the council keeps circling that hasn't been answered]
**What to do or sit with this week:** [One concrete action or honest reflection — not a KPI, just a real next step]Fast Mode (--fast)
If the user adds --fast or needs a quicker read:
- Run only 3 agents: Worst Case + Pattern Caller + Pragmatist
- Skip Future Self and Challenger
- Same synthesis format, prepend "Fast mode — 3/5 agents"
- ~15K tokens
What the Council Does NOT Do
- Does NOT make the decision for the user. Presents the verdict and waits.
- Does NOT run on trivial or operational tasks. Stakes must be real.
- Does NOT replace coaching — it supplements it on high-stakes decisions.
- Does NOT apply to technical or engineering decisions. Use
/devils-advocatefor code reviews. - Does NOT chain to another skill after the verdict.
- Does NOT sand down the sharpest points from each agent during synthesis.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

