What is swarm-resume?

A workflow for safely continuing an approved coding plan from the repository's current state. It checks the saved plan and cleans up leftover worktrees and branches from an earlier session.

Use it to resume an interrupted swarm task, reconcile its plan with the active session, and continue from the current task.

It prevents resumed work from using stale instructions or conflicting temporary branches.

swarm-resume — Skill for Claude Code by ZaxbyHub

Install

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.

Any agent

npx skills add ZaxbyHub/opencode-swarm --skill swarm-resume

Clone the repo

git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/swarm-resume/github.svg)](https://agentmods.dev/skills/zaxbyhub/opencode-swarm/swarm-resume)

Your own site

<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/swarm-resume"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/swarm-resume/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/swarm-resume"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/swarm-resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 553 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00024	$0.00553
Opus 5	$0.00012	$0.00277
Sonnet 5	$0.00005	$0.00111
Haiku 4.5	$0.00002	$0.00055

Measured 11d ago against content hash 3e5e02f9db74, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

swarm-resume 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 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.

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.

.claude/skills/swarm-resume/SKILL.md · 28 lines

How it starts

The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resume 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: RESUME

If .swarm/plan.md exists:

Read plan.md header for "Swarm:" field
If Swarm field missing or matches the active swarm id:
- Reconcile stale worktree state before resuming: prune/adopt stale .swarm-worktrees/ lane directories and swarm-lane/* git branches left from the prior session. Drive this via the /swarm reset-session recovery command (internal: cleanupOrphanedBranches) so the resumed run starts from a clean provisioning state.
- Resume at current task
If Swarm field differs (e.g., plan says "local" but the active swarm id is "cloud"):
- Update the plan's Swarm field to the active swarm id via save_plan (do not hand-edit plan.md — it is a derived projection).
- Purge any memory blocks (persona, agent_role, etc.) that reference a different swarm's identity — your identity comes from this system prompt only
- Delete the SME Cache section from context.md (stale from other swarm's agents)
- Update context.md Swarm field to the active swarm id
- Inform user: "Resuming project from [other] swarm. Cleared stale context. Ready to continue."
- Reconcile stale worktree state before resuming: prune/adopt stale .swarm-worktrees/ lane directories and swarm-lane/* git branches left from the prior session. Drive this via the /swarm reset-session recovery command (internal: cleanupOrphanedBranches) so the resumed run starts from a clean provisioning state.
- Resume at current task If .swarm/plan.md does not exist → New project, proceed to MODE: SPECIFY If new project: Run complexity_hotspots tool (90 days) to generate a risk map. Note modules with recommendation "security_review" or "full_gates" in context.md for stricter QA gates during QA gate selection (stricter gates). Optionally run todo_extract to capture existing technical debt for plan consideration. After initial discovery, run sbom_generate with scope='all' to capture baseline dependency inventory (saved to .swarm/evidence/sbom/).

Read the full file on GitHub · 28 lines

Changes

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 · 28 lines · 24 tokens per session scan A 3e5e02f9db74

Subscribe to this mod's changes

swarm-resume is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (467 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 553 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.

agent-swarm ai-agents ai-coding automation bun cli

armada-contract

Co-write an armada contract (REQUIREMENTS.md) one question at a time. Use when drafting or updating a feature contract before implementation.

rafmacalaba/armada · 33 tokens

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.

rafmacalaba/armada · 33 tokens

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…

selftune-dev/selftune · 148 tokens

swarm-resume