agentleFS
markphelpsmarkphelps/agent-plugins/skills/council/SKILL.md

council

Skill6 starsChanged 49 days agoMITView on GitHub

You are the lead. Before giving the user a final plan, deliberate with the other agent CLIs installed on this machine: propose → hear ONE reply from each member → revise, repeated for X turns. Members never see each other's replies — only your plan and, in later rounds, what changed. The deliverable is the final plan plus the deliberation shown as a conversation. Do NOT implement anything unless the user explicitly asked for execution after planning. 0. Parse. TASK…

156 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

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.
  • TironFoxSkill

    agent-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

  • renepfSkill

    motion-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

  • RojiosSkill

    defi-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

  • scottwaterSkill

    modernize

    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

  • RojiosSkill

    dart-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

  • scottwaterSkill

    leaving-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

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    1. Detect members: Every CLI in the table below whose binary exists (command -v) and answers --version within ~15s — minus SELF.

    line 31
  2. Distinctive:

    Read the replies. A member that times out, errors, or returns empty is noted in the transcript ("cursor: no reply — timeout") and the round …

    line 50
  3. Distinctive:

    No padding: if the feedback is thin, say so.

    line 135

“Common” is measured: kept by at least 6 in 10 of the 139 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Council

You are the lead. Before giving the user a final plan, deliberate with the other agent CLIs installed on this machine: propose → hear ONE reply from each member → revise, repeated for X turns. Members never see each other's replies — only your plan and, in later rounds, what changed. The deliverable is the final plan plus the deliberation shown as a conversation. Do NOT implement anything unless the user explicitly asked for execution after planning.

Protocol

0. Parse. TASK = the user's ask, verbatim. X = the number of turns they said ("1 turn", "3 turns"...), default 1. X is exact: run all X rounds even if round 1 is unanimous approval, and never add extra rounds. SELF = the product you run in: Claude Code → claude, Codex → codex, Cursor → cursor, Gemini CLI → gemini, Grok → grok, OpenCode → opencode.

1. Detect members. Every CLI in the table below whose binary exists (command -v) and answers --version within ~15s — minus SELF. If the user names members ("council with just codex and grok"), use only those. If none are available, say so and present your solo plan explicitly marked as un-counciled — never fake a council.

2. Session. SESSION=~/.council/$(date +%Y%m%d-%H%M%S)-<short-slug>, mkdir -p "$SESSION". Write the ask verbatim to task.md. Do your normal thinking/exploration, then write your honest first plan to plan-v1.md — complete enough to critique: approach, steps, files/tools touched, tradeoffs.

3. Deliberate — for each round R in 1..X:

  • Build one prompt per member from the template below → $SESSION/round-R/prompts/<member>.md.
  • Invoke all members in parallel in one shell command (background jobs + wait), from the project directory the task concerns, each capped at ~300s. Reply → $SESSION/round-R/replies/<member>.md, stderr → a log file. macOS has no timeout command; use perl -e 'alarm shift; exec @ARGV' 300 <cmd...>.
  • Read the replies. A member that times out, errors, or returns empty is noted in the transcript ("cursor: no reply — timeout") and the round continues.
  • Revise: weigh each opinion on its merits — adopt what's right, reject what's wrong (keeping your position is allowed, with reasons). Write plan-v(R+1).md (full revised plan) and changes-v(R+1).md (what changed and why, what you rejected and why — describe suggestions by content, never by member name: all members see this file next round).

4. Answer with the deliberation formatted as a conversation, then the final plan (template at the bottom).

Member CLIs

$PF = that member's prompt file, $RF = its reply file. Run from the project directory.

memberinvocationwhy these flags
claudeclaude -p < "$PF" > "$RF"print mode auto-denies write/exec tools; reads are fine
codexcodex exec --skip-git-repo-check -s read-only --color never -o "$RF" - < "$PF" > /dev/null 2>&1read-only sandbox; final message lands in $RF via -o
cursorcursor-agent -p --output-format text --mode plan --trust "$(cat "$PF")" > "$RF"plan mode is read-only; --trust scopes cwd trust to this run (headless refuses untrusted dirs without it)
geminigemini --skip-trust --approval-mode plan -p "$(cat "$PF")" > "$RF"plan mode is read-only; --skip-trust for headless in untrusted dirs
grokgrok --output-format plain --system-prompt-override "$GROK_SYS" --prompt-file "$PF" > "$RF"see the grok note; binary is sometimes installed as agent
opencodeopencode run "$(cat "$PF")" > "$RF"advisory-only enforced at prompt level

The grok note. Headless grok silently cancels the entire run (empty output, exit 0, stream ends stopReason:"Cancelled") the moment the model attempts a tool call — and its stock system prompt makes it attempt one on any work-shaped prompt. Two-part fix, both required: pass --system-prompt-override with

GROK_SYS="You are one member of a council of AI coding agents, asked for a one-shot written assessment of another agent's plan. Reply directly with plain markdown text following the instructions in the user message. Do not use tools, do not ask questions, do not wait for anything."

and give grok the no-tools closing paragraph in its prompt (below). Grok is the one member that advises without reading the repo.

Member prompt template

Sections in [...] only when they apply. Everything is plain text you substitute.

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.

For grok only, replace the final paragraph with:

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.

Rules

  • Independence: one invocation per member per round; never re-query a member within a round, never forward one member's reply to another.
  • Faithful summaries: in the transcript, include each member's strongest objection even — especially — when you rejected it.
  • No padding: if the feedback is thin, say so; don't manufacture disagreement or extra rounds.

Final answer format

# 🏛 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/\*

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.