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 agentmods add skills/fission-ai/openspec/release-openspecnpx skills add Fission-AI/OpenSpec --skill release-openspecgit clone --depth 1 https://github.com/Fission-AI/OpenSpecWhat 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 | $0.00088 | $0.02759 |
| Opus 5 | $0.00044 | $0.01380 |
| Sonnet 5 | $0.00018 | $0.00552 |
| Haiku 4.5 | $0.00009 | $0.00276 |
Grade A, and why
release-openspec 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 2d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release OpenSpec
Run the OpenSpec release workflow as a resumable state machine. Inspect live GitHub state on every invocation and take only the next safe action. Do not assume an earlier invocation completed.
Principles
- Treat
Fission-AI/OpenSpecandorigin/mainas the release source of truth. - Default to a read-only audit when the user asks for status, readiness, or advice.
- Treat a request to release, prepare a release, continue, or resume as authorization to perform the applicable release actions.
- Preserve the user's checkout. Never discard unrelated changes or switch their current branch just to prepare a changeset.
- Use a temporary worktree from current
origin/mainfor release-authored commits when the checkout is dirty or not onmain. - Never approve your own PR. Human review is a deliberate gate.
- Treat merge-queue entry as an intermediate state, not a merge. Advance only after GitHub reports
mergedAtand the commit is present onmain. - Never create the automated Version Packages PR manually. The Changesets action owns it.
- Never push an empty commit merely to retrigger CI. Diagnose the failed or missing run first.
- Report URLs, the state reached, and the exact human action needed whenever pausing.
Know the two PR types
Keep these distinct in output and decisions:
- Changeset PR: A normal human-authored PR that adds one or more
.changeset/*.mdfiles. Prefer adding a changeset to the feature/fix PR; create a catch-up changeset PR only for already-merged work that should be included. - Version Packages PR: The automated
changeset-release/mainPR titledchore(release): version packages. Merging or adding changesets tomainupdates this same PR. Merging it publishes the stable release.
An open Version Packages PR does not prohibit a catch-up changeset PR. It means a catch-up PR is useful only when the audit finds missing release-worthy work. Once that PR merges, wait for the existing Version Packages PR to update.
What ships with it
2 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.
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.
- 2d ago First seen · 181 lines · 88 tokens per session scan A 56b391b3b4e8
release-openspec is a skill published in the GitHub repository Fission-AI/OpenSpec (66,949 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 2,759 once invoked, about $0.0004 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
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
openprd-experience-quality-candidate-eval-20260609000941
Use when the current task overlaps this draft project experience and you should verify fit before reusing it.
openprd-experience-quality-candidate-eval-20260614024546
Use when the current task overlaps this draft project experience and you should verify fit before reusing it.
openprd-experience-quality-candidate-eval-20260621153509
Use when the current task overlaps this draft project experience and you should verify fit before reusing it.
openprd-experience-diagnostic-candidate-eval-20260607125040
Use when the current task overlaps this draft project experience and you should verify fit before reusing it.
openprd-experience-diagnostic-candidate-eval-20260607145749
Use when the current task overlaps this draft project experience and you should verify fit before reusing it.