Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ZaxbyHub/opencode-swarm --skill councilgit clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/zaxbyhub/opencode-swarm/council)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/council"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/council/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/zaxbyhub/opencode-swarm/council"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/council.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 168 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00028 | $0.02339 |
| Opus 5 | $0.00014 | $0.01170 |
| Sonnet 5 | $0.00006 | $0.00468 |
| Haiku 4.5 | $0.00003 | $0.00234 |
Grade A, and why
council scanned grade A with 1 finding 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Citing `bunSpawnSync` / `child_process.spawnSync` behavior from documentation that pre-dates the current version. How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council Protocol
This protocol is loaded on demand by the architect runtime. The architect prompt keeps only activation, action, and hard safety constraints; the full execution details live here.
MODE: COUNCIL
Activates when: user invokes /swarm council <question> (optionally with
--spec-review).
Purpose: convene a fixed three-agent multi-model General Council (generalist / skeptic / domain expert) for an advisory deliberation. The architect runs a curated web research pass upfront, dispatches the three agents in parallel with the gathered RESEARCH CONTEXT, routes any disagreements back for one targeted reconciliation round, and synthesizes the final user-facing answer directly.
This mode is ADVISORY. It does not block any other workflow and does not modify
code, plans, or specs. The output is for the user (general mode) or for the spec
being drafted (spec_review mode is available via /swarm council --spec-review
for manual spec review). General Council advisory input is offered as an early
workflow option in MODE: BRAINSTORM (Phase 1b) and MODE: PLAN before
save_plan.
Pre-flight (always run first)
- Read
council.generalfrom the resolved opencode-swarm config. Resolution is global first (~/.config/opencode/opencode-swarm.json), then project override (.opencode/opencode-swarm.json). A global config is valid and must be used when no project override is present; do not fail after checking only the project file. Ifcouncil.general.enabledis not true OR no search API key is configured (neithercouncil.general.searchApiKeynor the corresponding env varTAVILY_API_KEY/BRAVE_SEARCH_API_KEY), surface to the user: "General Council is not enabled. Set council.general.enabled: true and configure a search API key in global ~/.config/opencode/opencode-swarm.json or project .opencode/opencode-swarm.json." Then STOP.
Research Phase (always run before dispatching council agents)
- Formulate 1-3 targeted
web_searchqueries that best capture the information needed to answer the question. Prefer specific, keyword-focused queries over broad ones.
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.
- 2d ago Changed · +3 lines b4159ff778d8
- 9d ago First seen · 186 lines · 28 tokens per session scan A 8aaab79dd5c8
council is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (466 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 2,339 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
armada-gate
Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.
armada-contract
Co-write an armada contract (REQUIREMENTS.md) one question at a time. Use when drafting or updating a feature contract before implementation.
selftune
Self-improving skills toolkit that watches real agent sessions, detects missed triggers, grades execution quality, and improves skill packages through evals, replay, baselines, review, and post-deploy watch. Use when verifying or publishing a skill, improving instructions or routing, checking skill health, grading…
armada-dispatch
Dispatch subagents in parallel with disjoint file scope. Use when facing 2+ independent tasks, multiple files, or parallel phases. Triggers on: parallelize, dispatch subagents, run in parallel.
armada-voyage-finish
Voyage-finalization ritual. Load at voyage end, dispatch a galleon subagent to rebase, fix TODO PR refs, regen scaffold, push, open/update PR. Triggers on: finish voyage, finalize, rebase, PR.
armada-ledger
Pick the right ledger for a finding. Use when writing defects, adversarial findings, or security findings. Triggers on: ledger, defect, adversarial, security finding, DEF-001, ADV-001, SEC-001.