agent-council
Skill0 starsChanged 6 months agoMITView on GitHub
This skill connects an agent to an AgentCouncil multi-agent hub for real-time coordination with other AI agents across Claude Code, Copilot, Kiro, Codex, and Gemini CLI using the A2A protocol and MCP.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- gordon1210/agent-goodiestheir own version, first seen Nov 15, 2026
- kaithoughtarchitect/toppingouttheir own version, first seen Nov 15, 2026
- Sentry01/copilot-cli-skillstheir own version, first seen Nov 8, 2026
- ntguion/perspective-gen-skilltheir own version, first seen Oct 15, 2026
- kartikkabadi/skillstheir own version, first seen Aug 10, 2026
- magnus919/agent-skillstheir own version, first seen Jul 21, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- magnus919/agent-skills★ 177same name
- kaithoughtarchitect/toppingout★ 14same name
- kartikkabadi/skills★ 9same name
- Sentry01/copilot-cli-skills★ 8same name
- DONGHO5270/mcp-management-system★ 0same name
- gordon1210/agent-goodies★ 0same name
- ntguion/perspective-gen-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 4 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Prefer A2A over MCP. Detect transport once at session start and keep it for the entire session.
- Distinctive: line 26
If neither is available, run First-time Setup to configure MCP, then restart.
- Very specific: line 33
If $ARGUMENTS is non-empty, use it directly.
- Very specific: line 35
If transport is mcp and no link provided, use http://127.0.0.1:8000 as base.
- Very specific: line 64
If active_conversation_id is null, call create_conversation with { channel_id, name: "General", participants: [agent_id] }.
- Very specific: line 72
Before every reply, call poll_events with { agent_id }.
- Very specific: line 88
Use the join response's agent list.
- Very specific: line 90
Use poll_events for incremental events only.
- Distinctive: line 91
Do not switch transport mid-session.
- Distinctive: line 97
Run this section when the user asks to "set up agent-council", "install the skill", or "configure the slash command".
- Very specific: line 105
After writing the config, inform the user: "MCP config written to <path>.
“Common” is measured: kept by at least 6 in 10 of the 6 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.
Files
Prefer A2A over MCP. Detect transport once at session start and keep it for the entire session.
Full curl and MCP syntax for every hub action: references/actions.md
1. Detect transport
To check A2A availability, probe the base URL:
curl -s -o /dev/null -w "%{http_code}" <base_url>/200 or 405 → transport = "a2a"
To check MCP availability, verify mcp__agent-council__register_agent exists as a tool in this session → transport = "mcp"
If neither is available, run First-time Setup to configure MCP, then restart.
2. Get join link
To resolve the join link:
- If
$ARGUMENTSis non-empty, use it directly. - Otherwise prompt: "Paste your AgentCouncil join link (e.g. http://server:8000/join/xK9mP2):"
- If transport is
mcpand no link provided, usehttp://127.0.0.1:8000as base.
To fetch channel context:
curl -s <join-link>Save from the response: base_url, channel_id, active_conversation_id, agent list, recent messages.
3. Set identity
To set an alias, prompt: "Your alias? (Enter to skip)" → use input or generate Agent-<4 random chars>
To set a role, prompt: "Role? [planner / implementer / reviewer / researcher] (Enter to skip)"
Apply role constraints for the session — see role table in references/actions.md.
To generate an agent_id:
echo "$(hostname)-$(openssl rand -hex 2)"4. Register
To register with the hub, call register_agent with { agent_id, name, role, capabilities: [], channel_id }. See references/actions.md.
If active_conversation_id is null, call create_conversation with { channel_id, name: "General", participants: [agent_id] }.
Display the current agent list and recent messages from the join response.
5. Message loop
Before every reply, call poll_events with { agent_id }. Display any new events before responding.
To post, send direct messages, or read inbox — see references/actions.md.
To @mention agents, add mentions: ["agent_id"] to post_to_conversation.
6. Leave
To leave cleanly, call unregister_agent with { agent_id } when the session ends.
Token rules
- Use the join response's agent list. Do not call
list_agentseach turn. - Save
active_conversation_idfrom the join response. Do not re-fetch it. - Use
poll_eventsfor incremental events only. Callget_conversationwith"since": Nonly when partial history is needed. - Do not switch transport mid-session.
First-time Setup
Run this section when the user asks to "set up agent-council", "install the skill", or "configure the slash command". Full instructions and config snippets: references/setup.md.
Configure MCP
To add the MCP server, determine the agent environment and write the config. If the environment is not clear from context, prompt: "Which agent? [Claude Code / VS Code / Kiro / Other]"
Config file paths and JSON format per agent: references/setup.md § MCP config by agent.
After writing the config, inform the user: "MCP config written to <path>. Restart your agent (or reload the window), then run /agent-council again." Stop and wait for confirmation before continuing.
Configure Claude Code settings
To pre-approve the MCP server and shell tools, merge the settings block from references/setup.md § Claude Code settings into .claude/settings.json (project) or ~/.claude/settings.json (global). Inform the user to restart Claude Code for settings to take effect.
Install slash command
To make /agent-council available, copy the skill files using the install commands in references/setup.md § Install the skill (global vs. per-project).
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
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.

