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 wyattowalsh/agents --skill opencode-ensemblegit clone --depth 1 https://github.com/wyattowalsh/agentsWrote 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/wyattowalsh/agents/opencode-ensemble)<a href="https://agentmods.dev/skills/wyattowalsh/agents/opencode-ensemble"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/opencode-ensemble/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/wyattowalsh/agents/opencode-ensemble"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/opencode-ensemble.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.00049 | $0.02362 |
| Opus 5.5 | $0.00020 | $0.00945 |
| Sonnet 5.5 | $0.00010 | $0.00472 |
| Haiku 4.5 | $0.00005 | $0.00236 |
Grade A, and why
opencode-ensemble scanned grade A with 0 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode Ensemble
Use OpenCode Ensemble as a coordination system, not a shortcut for avoiding judgment. Parallel agents work best when the lead owns decomposition, sequencing, review, merge, and verification.
This repo vendors the upstream hueyexe/opencode-ensemble skill from tag v0.14.2 (b6bc7f706c13aa42d32e836ea647677d0b14c2f7) and tunes its model guidance for this OpenCode setup. Teammates should inherit the repo-managed OpenCode agent variants by default; pass an explicit team_spawn.model only when the task needs a deliberate model override.
Core Principle
Spawn teammates only for independent, verifiable work. A good Ensemble team has narrow task ownership, clear dependencies, and a lead that integrates results deliberately.
Dispatch Table
Route $ARGUMENTS by the user's request:
$ARGUMENTS pattern |
Mode | Action |
|---|---|---|
parallel, team, ensemble, delegate, teammate |
Team planning | Decide whether Ensemble is justified, then create one lead-owned team if useful. |
waves, parallel teams, subagents, fan out |
Wave planning | Model work as one team with role groups, task dependencies, and lead-owned gates. |
review teammate output, merge team, finish team |
Integration | Read results, shut down teammates, merge with team_merge, inspect diffs, and verify. |
models, model pool, which model |
Model guidance | Inherit repo defaults unless a deliberate team_spawn.model override is justified. |
| Empty or ambiguous | Suitability check | Explain when Ensemble helps, and prefer one scout or inline work when scope is small. |
Canonical Vocabulary
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 2.9 KB
- README.md 1.3 KB
- references/anti-patterns.md 4.4 KB
- references/coordination-patterns.md 5.1 KB
- references/eval-scenarios.md 3.5 KB
- references/lead-checklists.md 3.6 KB
- references/prompt-recipes.md 4.3 KB
- scripts/asset_toolkit/__init__.py 303 B runs code
- scripts/asset_toolkit/_shared.py 5.6 KB runs code
- scripts/asset_toolkit/common.py 3.0 KB runs code
- scripts/asset_toolkit/package.py 43 KB runs code
- scripts/asset_toolkit/validate_evals.py 11 KB runs code
- scripts/asset_toolkit/validate_hooks.py 13 KB runs code
- scripts/asset_toolkit/validate_skill.py 3.6 KB runs code
- scripts/check.py 1.5 KB runs code
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.
- 1mo ago First seen · 194 lines · 49 tokens per session scan A 11581b7fd853
opencode-ensemble is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 2,362 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…