mcpbeat

LLM Council

rohitg00/llm-council

Provider-agnostic multi-LLM deliberation. Three phases — independent responses, cross-model anonymized ranking, chairman synthesis. Provider config from env (OPENAI/ANTHROPIC/FIREWORKS/OPENROUTER/custom OpenAI-compatible base URL). Persists transcript to a wiki page when --wiki <slug> is passed. Use when the user wants multiple AI perspectives, consensus-building, or the "LLM Council" approach for high-stakes reviews, plan critique, or contested learning rules.

4k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
2755
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/rohitg00/pro-workflow --skill llm-council

The instruction itself

9 sections, as written by the author

LLM Council

Karpathy's LLM Council pattern, provider-agnostic. dair-academy's version hardcoded Fireworks; ours reads any OpenAI-compatible endpoint via env.

When to use

  • High-stakes plan review (/plan crosses N-file threshold)
  • Conflicting learning-rules → re-resolve via vote
  • User invokes /council "<query>" or /wiki council
  • Architecture decisions where you want multiple viewpoints captured
  • Persisting deliberation as a wiki page for future reference

Three phases

  • Independent: each model answers in parallel
  • Ranking: each model ranks anonymized peer responses
  • Synthesis: chairman model reads all responses + rankings → final answer

Provider config

Provider chosen via env. First-match wins:

| Env var | Provider | Default base URL |

|---------|----------|------------------|

| ANTHROPIC_API_KEY | Anthropic | https://api.anthropic.com |

| OPENAI_API_KEY | OpenAI | https://api.openai.com/v1 |

| OPENROUTER_API_KEY | OpenRouter | https://openrouter.ai/api/v1 |

| FIREWORKS_API_KEY | Fireworks | https://api.fireworks.ai/inference/v1 |

| LLM_COUNCIL_BASE_URL + LLM_COUNCIL_API_KEY | Custom OpenAI-compat | (user-supplied) |

Override per-run with --provider openai|anthropic|openrouter|fireworks|custom.

Default model rosters per provider live in scripts/council.js and can be overridden via --models CSV and --chairman <id>.

Commands

node $SKILL_ROOT/scripts/council.js run "<query>" [--models id1,id2,id3] [--chairman id] [--provider <name>] [--wiki <slug>]
node $SKILL_ROOT/scripts/council.js providers
node $SKILL_ROOT/scripts/council.js show <session-id>

--wiki <slug> writes the full transcript to <wiki>/derived/council/<session-id>.md and registers it via wiki-cli.js page so it shows in FTS5 search.

Output

Each session writes:

~/.pro-workflow/council/<session-id>/
├── config.json           # query, models, chairman, provider
├── phase1_responses.json # raw API responses per model
├── phase2_rankings.json  # anonymized ranking outputs
├── phase3_synthesis.txt  # chairman's final answer
└── final_output.md       # human-readable bundle

Console prints the markdown bundle. Pipe to pbcopy / tee as needed.

Hard rules

  • Never skip the ranking phase. It's the core of the council pattern.
  • Save raw responses to disk verbatim. No summarization in storage.
  • Anonymize responses for ranking — models see Response A/B/C/..., not peer names.
  • The chairman sees both real names AND rankings.
  • Display all three phases to the user. No phase elision.

Cost awareness

The script logs per-call latency + tokens on supported providers. Multiply by your provider rate to estimate. Council cost grows linearly with len(models)^2 (each model ranks all others) plus the chairman.

Default council size: 3-5 models. More models = exponentially more ranking calls.

Use with wiki

/wiki council agent-memory "should we adopt episodic memory in our agents?"

Loads agent-memory wiki context as system prompt prefix, runs council, persists transcript as wiki/derived/council/<id>.md. The transcript becomes searchable via /wiki ask.

How to use it

Copy the folder

Take rohitg00/llm-council from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.