Council

What it does

When your agent uses it

• Convene the council
• Consult the other agents
• Ask the council
• Ask codex/cursor/gemini/grok what they think

Example prompts

• “/council”

What it can do on your machine

Read from SKILL.md and the folder at commit eb7cd10. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • claude
  • codex
  • gemini
  • opencode

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Council loads about 2k tokens when it runs. Until then it costs about 147 tokens; SKILL.md has 703 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~147

When it runs · the whole SKILL.md, loaded when a task matches

~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from kitze/council at commit eb7cd10, republished under its MIT licence (© kitze). 703 words, ~2,006 tokens.

name

council

description

Convene a council of AI coding agents before finalizing a plan. The agent you're talking to — whichever CLI is the lead (claude, codex, cursor, gemini, grok, opencode) — drafts a plan, presents it independently to every other agent CLI installed on the machine, each member gives ONE reply per turn, and the lead revises the plan for X turns before answering. Trigger words: council, convene the council, consult the other agents, ask the council, ask codex/cursor/gemini/grok what they think, second opinion from other agents, N turns of deliberation, deliberate before planning.

You are <member>, one of several AI coding agents serving on a council.
The lead agent, <self>, received a task from its user and must consult this council before presenting the final plan. This is consultation round <R> of <X>.
Council rules: members reply independently. You do not see other members' replies — only the lead's plan and, in later rounds, how it changed.

## The task (verbatim from the user)

<contents of task.md>

## <self>'s current plan (v<R>)

<contents of plan-vR.md>

[## What the lead changed since the previous round, and why

<contents of changes-vR.md>]

[## Your own reply in the previous round

<contents of round-(R-1)/replies/<member>.md>]

## How to reply

Give exactly ONE reply — your honest expert assessment of this plan:

1. First line: verdict — SHIP IT, SHIP WITH CHANGES, or RETHINK.
2. The 2-5 most important problems, risks, or gaps. Concrete and specific, strongest first.
3. Where you would do it differently: the alternative and why it wins.
4. If the plan is fundamentally sound, say so and name its single weakest point. Do not invent objections to sound useful.

You are advising, not implementing. Reading files in the current directory is fine; do NOT edit files, run state-changing commands, or write full implementations. Under ~400 words, plain markdown, no preamble.

You are advising, not implementing. You have NO tool access here — base your reply only on the material above; do not attempt to read files or run commands. Under ~400 words, plain markdown, no preamble.

# 🏛 Council on: <task one-liner>
*Lead: claude · Members: codex, cursor, grok · 2 turns · session: ~/.council/...*

## Turn 1
**claude (lead):** Proposed v1 — <2-3 line summary of the plan>
**codex:** SHIP WITH CHANGES — <2-3 line summary of the reply>
**cursor:** RETHINK — <...>
**grok:** <...>
**claude (lead):** Revised → v2: adopted <...>; rejected <...> because <...>

## Turn 2
...

## Final plan (v3)
<the full final plan>

*Changed my mind on: <...> · Held my ground on: <...> · Full replies: $SESSION/round-*/replies/*

© kitze, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in the repository root of kitze/council.

• SKILL.md
• LICENSE
• README.md

Open the folder on GitHubat commit eb7cd10