durable-session-state SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
durable-session-state from zaxbyhub/opencode-swarm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zaxbyhub/opencode-swarm/durable-session-state@git:20261012.097422cPins git:20261012.097422c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zaxbyhub/opencode-swarm
- Path
.claude/skills/durable-session-state/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261012.097422c, committed Oct 12, 2026
- First version recorded
- Jul 2, 2026
- Size
- 3,619 bytes
- Repository stars
- 518
- License
- MIT
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a session restart.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Durable Session State Long swarm-mode sessions outlive their context window. Compaction summarizes history, and summaries lose exactly the things the swarm gates depend on: which diff a reviewer approved, what evidence was recorded, which decisions are settled. Without durable artifacts, a resumed session re-litigates settled decisions or — worse — treats a stale approval as current. Persist state to files as you go; treat the conversation as cache, not storage. ## Where artifacts live - Generic swarm tasks: `.claude/session/tasks/<task-slug>/` in the project. - Issue-tracer work: `.agents/issue-traces/<issue-slug>/` (that skill's own schema — `08b-implementation-review.md`, `09-final-critic.md` — wins for its work). - Never write task artifacts to the repo root, and never under `.swarm/` — that directory is the OpenCode plugin's runtime state, not Claude Code's. - These artifacts are working state, not deliverables: do not commit them unless the user asks. Before committing, check `git status` and exclude them explicitly. ## What to persist Keep it to four small files per task; update in place: …
Read the whole file at its exact version.
How to install
mdr add zaxbyhub/opencode-swarm/durable-session-state@sha256:7a30dbd4f5c40661The line at the top of this page pins the label git:20261012.097422c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ndwbfp4bvwmuwxsm)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 2, 2026 and Oct 12, 2026, about one every 34 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.097422c latest | 2026-10-12 | 097422c | 3,619 B | A | view · diff |
| git:20260904.ddbab7e | 2026-09-04 | ddbab7e | 3,607 B | A | view · diff |
| git:20260711.5972d3e | 2026-07-11 | 5972d3e | 3,602 B | A | view · diff |
| git:20260702.fa69d6a | 2026-07-02 | fa69d6a | 3,579 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3619 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zaxbyhub/opencode-swarm · 518 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ndwbfp4bvwmuwxsm GET https://markdownregistry.com/api/v1/resolve?ref=zaxbyhub/opencode-swarm/durable-session-state GET https://markdownregistry.com/api/v1/blob/7a30dbd4f5c40661ae06347671897c6db0fb368be9488e66bb5570c6bb7fa505
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from zaxbyhub/opencode-swarm
Every file in zaxbyhub/opencode-swarm