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 editing-skillsgit 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/editing-skills)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/editing-skills"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/editing-skills/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/editing-skills"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/editing-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 124 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00095 | $0.02065 |
| Opus 5 | $0.00048 | $0.01033 |
| Sonnet 5 | $0.00019 | $0.00413 |
| Haiku 4.5 | $0.00010 | $0.00206 |
Grade A, and why
editing-skills 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 4d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editing Skills in opencode-swarm
Skills in this repo exist across parallel trees (.opencode/skills/,
.claude/skills/, .agents/skills/) governed by explicit mirror contracts.
Editing a SKILL.md without knowing its contract silently desynchronizes the
OpenCode and Claude Code surfaces. Classify first, then edit.
Step 1 — Classify the skill
Look the slug up in src/config/skill-mirrors.ts:
- MIRRORED_ARCHITECT_MODE_SKILLS (brainstorm, specify, clarify-spec,
swarm-resume, clarify, discover, consult, pre-phase-briefing, council, deep-dive,
deep-research, issue-ingest, plan, critic-gate, design-docs):
.opencodeand.claudecopies must stay byte-identical. Any edit is a dual-tree edit — apply the identical change to both files. - ADAPTER (execute, phase-wrap, swarm-pr-review, swarm-pr-feedback,
swarm-pr-subscribe, swarm-ci-monitor):
.opencodeis canonical;.claudeand.agentswhere present are thin shims that must keep the exact relative reference../../../.opencode/skills/<slug>/SKILL.md(drift-check verifies the string).swarm-implementfollows the same operational adapter pattern, but is currently classified as an additional divergent contract because the additional-contract registry does not yet model non-architect adapter shims. - DIVERGENT: both trees exist, content intentionally differs — a
single-tree edit is fine.
codebase-review-swarmis inDIVERGENT_ARCHITECT_MODE_SKILLS;engineering-conventionsis a divergent entry inADDITIONAL_SKILL_MIRROR_CONTRACTS.swarm-implementandwriting-testsare classified divergent only because the additional-contract model does not yet have an adapter kind; operationally,.opencodeis canonical and.claudedelegates to it. - OPENCODE-ONLY:
loop(OPENCODE_ONLY_ARCHITECT_MODE_SKILLS) andrunning-tests(anopencode-onlyADDITIONAL contract) — do not create.claudemirrors (a.claude/skills/loopwould shadow Claude Code's built-in/loop). - ADDITIONAL contracts:
commit-prisdivergent(#1692). The.claudecopy is the repo-INTERNAL publication protocol (CI's pr-standards workflow declares it the source of truth); the.opencodecopy is the PORTABLE, project-agnostic version bundled into end-user projects, so the two trees intentionally differ — do not sync them byte-for-byte. The discovery shims in.agents/skills/commit-pr/and.github/skills/commit-pr/point at the repo-internal.claudefile as canonical. - Adapter skills (issue-tracer):
.opencode/skills/<slug>/SKILL.mdis the canonical protocol;.claude/skills/<slug>/SKILL.mdand.agents/skills/<slug>/SKILL.mdare thin shims that reference it via the relative path. Seesrc/config/skill-mirrors.tsfor thekind: adaptercontract. - No skill-mirrors.ts entry (qa-sweep, research-first, swarm, unswarm,
tech-debt-ci-review, rust-crate-ci, orchestrating-subagents, durable-session-state,
editing-skills, …): the
.claudefile is the source protocol and there is no.opencodecopy, no CI gate, and no npm shipment. But most are not single-file: many have a Codex adapter shim in.agents/skills/<slug>/that reads ".claude/skills/<slug>/SKILL.mdis the source protocol" (checkls .agents/skills/). Content edits to the.claudefile are safe — shims delegate — but renaming, moving, or removing one of these skills silently orphans its.agentsshim with zero drift-check coverage. Update or remove the shim in the same change. - Pre-flight for new skills (blocking): Before authoring any SKILL.md
content for a skill that should reach npm users, the slug MUST be registered
in all three places:
src/config/skill-mirrors.ts(classification),src/config/bundled-skills.ts(BUNDLED_PROJECT_SKILLS), andpackage.json#files. Creating content first and registering later is a common source of drift-check failures and missing shipments.
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.
- 4d ago Changed · +3 lines 65e3bf1475ab
- 10d ago First seen · 135 lines · 95 tokens per session scan A ce4f04b1456c
editing-skills is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (467 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 2,065 once invoked, about $0.0005 per session on Opus 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-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.