Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add southlab-ai/Claude-Plugin-Marketplace/plugin install the-councilWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/southlab-ai/claude-plugin-marketplace/council-setup)<a href="https://agentmods.dev/skills/southlab-ai/claude-plugin-marketplace/council-setup"><img src="https://agentmods.dev/badge/skills/southlab-ai/claude-plugin-marketplace/council-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/southlab-ai/claude-plugin-marketplace/council-setup"><img src="https://agentmods.dev/badge/skills/southlab-ai/claude-plugin-marketplace/council-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.00452 |
| Opus 5 | $0.00010 | $0.00226 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade C, and why
council-setup scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- macOS/Linux: `curl -LsSf https://astral.sh/uv/install.sh | sh` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- macOS/Linux: `curl -LsSf https://astral.sh/uv/install.sh | sh` What it actually says
Council Setup
Step 1: Check uv
Run: uv --version
If not found, tell the user to install uv:
- macOS/Linux:
curl -LsSf https://astral.sh/uv/install.sh | sh - Windows:
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Step 2: Install dependencies
Run: uv sync --directory "${CLAUDE_PLUGIN_ROOT}"
Step 3: Verify MCP server can import
Run: uv run --directory "${CLAUDE_PLUGIN_ROOT}" python -c "from src.server import mcp; print('MCP OK: ' + str(len(mcp._tool_manager.list_tools())) + ' tools')"
Step 4: Check agent teams
Check if agent teams are enabled: look for CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS in the environment or VS Code settings. If not set, tell the user:
- "Agent teams are required. Add
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1to your environment variables or VS Code settings."
Step 5: Auto-initialize (if in a project)
Check if the current working directory looks like a project (has a .git/ directory, package.json, pyproject.toml, Cargo.toml, or similar). If yes, AND .council/ does not already exist:
- Ask: "Initialize the council in this project now? (y/n)"
- If yes: call
council_memory_initwith the current project directory. - If no: tell them they can run
/council:initlater in any project.
Step 6: Done
Tell the user:
- "Setup complete. Restart Claude Code to connect the MCP server."
- "Then run
/council:consult <question>to catch blind spots in your next decision." - If auto-init was done: "Council already initialized here — you can consult right after restart."
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 36 lines · 19 tokens per session scan C ecea0e0a5d31
council-setup is a skill published in the GitHub repository southlab-ai/Claude-Plugin-Marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 452 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cosmergon
Persistent multi-agent economy where autonomous AI agents compete for resources, trade on a marketplace, and benchmark decision-making against a standing population of always-on agents. Invite other agents for energy rewards. Auto-registers — no API key needed.
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
oma-scholar
Scholarly research companion using Knows sidecar spec (.knows.yaml). Generates, validates, reviews, queries, and compares structured research-paper sidecars, and fetches them from knows.academy. Use for academic literature search, survey synthesis, paper authoring assistance, and peer review with token-efficient…
browser_cdp
A health check for Python code that produces a score, letter grade, and measures of issues such as complexity, duplication, dead code, dependencies, and architecture.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.