council

Um método para reunir quatro perspectivas sobre decisões ambíguas, como escolher entre um monorepo, que guarda vários projetos em um único repositório, e vários repositórios separados. As perspectivas incluem arquitetura, ceticismo, pragmatismo e crítica.

In plain words
What is it for?
Serve para comparar caminhos, discutir decisões de lançamento, avaliar alternativas de organização de código e tomar decisões de avançar ou parar.
Why use it?
Ajuda a revelar riscos e compromissos quando existem várias opções razoáveis. Também reduz a tendência de aceitar a primeira ideia sem questioná-la.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/junmystery/agent-guidance-python/council
Any agent
npx skills add JunMystery/Agent-Guidance-Python --skill council
Clone the repo
git clone --depth 1 https://github.com/JunMystery/Agent-Guidance-Python

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,390 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 98% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.01390
Opus 5 $0.00019 $0.00695
Sonnet 5 $0.00008 $0.00278
Haiku 4.5 $0.00004 $0.00139

Measured 2d ago against content hash fd578d63aace, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

This is a copy

98% identical to council — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/council/SKILL.md · 204 lines

How it starts

The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Council

Convene four advisors for ambiguous decisions:

  • the in-context Claude voice
  • a Skeptic subagent
  • a Pragmatist subagent
  • a Critic subagent

This is for decision-making under ambiguity, not code review, implementation planning, or architecture design.

When to Use

Use council when:

  • a decision has multiple credible paths and no obvious winner
  • you need explicit tradeoff surfacing
  • the user asks for second opinions, dissent, or multiple perspectives
  • conversational anchoring is a real risk
  • 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 santa-method
Breaking a feature into implementation steps planner
Designing system architecture architect
Reviewing code for bugs or security code-reviewer or santa-method
Straight factual questions just answer directly
Obvious execution tasks just do the task

Roles

Voice Lens
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

The three external voices should be launched as fresh subagents with only the question and relevant context, not the full ongoing conversation. That is the anti-anchoring mechanism.

Workflow

1. Extract the real question

Reduce the decision to one explicit prompt:

  • what are we deciding?
  • what constraints matter?
  • what counts as success?

If the question is vague, ask one clarifying question before convening the council.

2. Gather only the necessary context

If the decision is codebase-specific:

  • collect the relevant files, snippets, issue text, or metrics
  • keep it compact
  • include only the context needed to make the decision

Read the full file on GitHub · 204 lines

Changes

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.

  1. 2d ago First seen · 204 lines · 38 tokens per session scan A fd578d63aace

Subscribe to this mod's changes

council is a skill published in the GitHub repository JunMystery/Agent-Guidance-Python (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,390 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to council, differing in 3 lines, and is treated as a copy.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

xcodebuildmcp-structured-output-review

Use when reviewing XcodeBuildMCP structured output schema changes, schema versioning, manifest outputSchema metadata, and JSON fixture compatibility.

getsentry/XcodeBuildMCP · 37 tokens

opik-diagnose

Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…

comet-ml/opik-mcp · 147 tokens

mcp-transport-contract-auditor

Route shaft-mcp transport-contract audits to the canonical playbook.

ShaftHQ/SHAFT_ENGINE · 22 tokens

create-operator

MUST READ before creating or moving any operator (createop, copyop, setopposition, or executepython builds). Required verification, canonical positioning recipe, and error-checking steps.

dylanroscover/Embody · 42 tokens

cortex-automate

Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…

cdeust/Cortex · 93 tokens