llm-council · am-will — Claude Code skill: a council of CLI planners
This skill runs several CLI agents as independent planners, strips their identities, and merges the results into one final plan. Useful when a single model's bias is the problem.
npx skills add am-will/codex-skills --skill llm-council -a claude-codeWhat llm-council does
The skill spins up a council of planners: Codex, Claude, Gemini, OpenCode, or your own command. Each agent gets the same brief and writes a plan without seeing the others. Then the plans are anonymized, shuffled, and handed to a judge, so neither model name nor position sways the verdict.
You run it with python3 scripts/llm_council.py run --spec /path/to/spec.json. The lineup lives in agents.planners, and agents.judge overrides the judge; leave it out and the first planner takes that seat. Defaults are written by python3 scripts/llm_council.py configure to $XDG_CONFIG_HOME/llm-council/agents.json or ~/.config/llm-council/agents.json. Plans land as Markdown, run artifacts under ./llm-council/runs/<timestamp>.
Check the agents config before the first run: with no file present, the skill tells you to run ./setup.sh. Python 3 is required. Do not close the session while the council works — yielding before the 30-minute mark and before judge.md and final-plan.md are saved kills the run. Answering the intake questions is optional, but the skill notes that more detail improves the final plan.
What it helps with
- get independent plans from several CLI agents for one task
- remove one-model bias when picking an approach
- merge competing plans into a single document with a judge's reasoning
- survive a planner failure through retries
- keep a run on disk for later review
Example prompts for the agent
- run llm-council on this task and assemble the planner council
- configure a council of Codex, Claude and OpenCode, then run it
- run llm-council and save the final plan under llm-council/runs
How to install llm-council
1Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill llm-council -a claude-code2Manually: put the files in place
~/.claude/skills/llm-council/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/llm-council/
1Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill llm-council -a codex2Manually: put the files in place
.agents/skills/llm-council/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill llm-council -a cursor2Manually: put the files in place
.cursor/skills/llm-council/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install am-will/codex-skills llm-council2Manually: put the files in place
.github/skills/llm-council/SKILL.md1Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill llm-council -a gemini-cli2Platform CLI
gemini skills install https://github.com/am-will/codex-skills --path skills/llm-councilManually: put the files in place
.devin/skills/llm-council/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill llm-council -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about llm-council
How do I install llm-council in Claude?
Run npx skills add am-will/codex-skills --skill llm-council -a claude-code. The skill lands at ~/.claude/skills/llm-council/SKILL.md.
What does llm-council do?
It launches several CLI agents as planners, anonymizes and shuffles their plans, then has a judge merge them into final-plan.md.
What does llm-council need to run?
Python 3 and a configured agents file; without one, the skill asks you to run ./setup.sh. The lineup is set in agents.planners.
Similar skills
All skills for Agent setup: memory, context, orchestration →llm-council by other authors comes first.