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 clarify-specgit 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/clarify-spec)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/clarify-spec"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/clarify-spec.svg" alt="Measured on agentmods" 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.00027 | $0.01566 |
| Opus 5 | $0.00014 | $0.00783 |
| Sonnet 5 | $0.00005 | $0.00313 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
clarify-spec 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 7d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarify Spec 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: CLARIFY-SPEC
Activates when: /swarm sdd status reports a single resolved EFFECTIVE spec (non-null) AND it contains [NEEDS CLARIFICATION] markers; OR user says "clarify", "refine spec", "review spec", or "/swarm clarify" is invoked; OR architect transitions from MODE: SPECIFY or MODE: BRAINSTORM with open markers.
/swarm sdd status reflects readEffectiveSpecSync, which returns null (NO effective spec) for: no sources at all, multiple competing sources (e.g. openspec/ AND .specify/), multi-feature Spec-Kit without a selected feature, or any other unresolvable state. CLARIFY-SPEC does NOT activate in these null cases — tell the user: "No resolved effective spec exists. Disambiguate with /swarm sdd project --source <source> or --feature <feature>, or run /swarm specify to generate one first." and stop.
CONSTRAINT: CLARIFY-SPEC must NEVER create a spec. Always consult /swarm sdd status to determine the effective spec source before proceeding.
- Read the effective spec resolved by
/swarm sdd status(native.swarm/spec.mdOR OpenSpecopenspec/OR Spec-Kit.specify/— read the resolved spec FIRST before making any changes). - Scan for ambiguities beyond explicit
[NEEDS CLARIFICATION]markers:- Vague adjectives ("fast", "secure", "user-friendly") without measurable targets
- Requirements that overlap or potentially conflict with each other
- Edge cases implied but not explicitly addressed in the spec
- Acceptance criteria (SC-###) that are not independently testable
- Present all spec modifications using delta format with ## ADDED/MODIFIED/REMOVED Requirements sections:
-
ADDED Requirements: New requirements being added to the spec
-
MODIFIED Requirements: Existing requirements being revised (show old vs new)
-
REMOVED Requirements: Requirements being deleted (show what was removed)
-
- Delegate to
the active swarm's sme agentfor domain research on ambiguous areas before presenting questions. - Present questions to the user ONE AT A TIME (max 8 per session):
- Offer 2–4 multiple-choice options for each question
- Mark the recommended option with reasoning (e.g., "Recommended: Option 2 because…")
- Allow free-form input as an alternative to the options
- After each accepted answer, write the resolution to the resolved effective source (source-aware write-back):
- NATIVE effective spec (
.swarm/spec.mdexists): update.swarm/spec.mdwith the resolution directly. - NON-NATIVE effective spec (openspec/specify-only, NO native
.swarm/spec.md): do NOT write.swarm/spec.md— this would silently shadow the non-native source. Instead:- (a) If the resolved source supports in-place edits (e.g., OpenSpec sections), update the source artifacts directly.
- (b) If no in-place edit path exists, ask the user: "The effective spec lives in
<source>. To persist this resolution as a native spec, run/swarm sdd projectfirst to materialize one, or I can stop here. Proceed?" — if the user consents to project, materialize via/swarm sdd projectthen write.swarm/spec.md; otherwise stop. - (c) If neither (a) nor (b) applies, stop and tell the user the clarification cannot be auto-written to a non-native source without a projection step.
- Replace the relevant
[NEEDS CLARIFICATION]marker or vague language with the accepted answer. - If the answer invalidates an earlier requirement, update it to remove the contradiction.
- NATIVE effective spec (
- Stop when: all critical ambiguities are resolved, user says "done" or "stop", or 8 questions have been asked.
- Report a ## Clarification Summary: total questions asked, requirements added/modified/removed, remaining open ambiguities (if any), and suggest next step (
PLANif spec is clear, or continue clarifying).
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.
- 7d ago First seen · 66 lines · 27 tokens per session scan A 822f6c6b34ce
clarify-spec is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (463 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,566 once invoked, about $0.0001 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-contract
Co-write an armada contract (REQUIREMENTS.md) one question at a time. Use when drafting or updating a feature contract before implementation.
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.
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.