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 MageByte-Zero/spec-superflow --skill release-archivistgit clone --depth 1 https://github.com/MageByte-Zero/spec-superflowWrote 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/magebyte-zero/spec-superflow/release-archivist)<a href="https://agentmods.dev/skills/magebyte-zero/spec-superflow/release-archivist"><img src="https://agentmods.dev/badge/skills/magebyte-zero/spec-superflow/release-archivist/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/magebyte-zero/spec-superflow/release-archivist"><img src="https://agentmods.dev/badge/skills/magebyte-zero/spec-superflow/release-archivist.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 Excessive Agency · line 29 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00042 | $0.00973 |
| Opus 5.5 | $0.00017 | $0.00389 |
| Sonnet 5.5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
release-archivist 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 24d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Archivist
Bundled runtime
Before executing a CLI line below, replace its leading SSF with node "<plugin-root>/scripts/spec-superflow.mjs"; <plugin-root> is the absolute directory two levels above this file. Never run SSF literally or call an ssf from PATH.
Read SSF resume <change-dir> --json. In executing, complete verification and logical closure. In closing, perform only recorded pending physical finish, if merging is authorized. abandoned or a completed finish requires no work. Other states route through workflow-start.
New direct/planned changes
Use SSF workflow complete <dir> --verification-command "<required check command>". It runs final verification once; do not run the identical full suite immediately before invoking it. Planned execution additionally checks completed tasks, current full-range/wave review and any delta-spec publication. Direct execution needs no plan or review receipt. Ordinary failures stay in executing for focused repair. Do not add DP-6/DP-7 or another approval to authorized code delivery.
If the user explicitly accepts unfinished work or failed verification, use SSF workflow complete <dir> --accept-risk --confirm --reason "<decision and remaining issues>". Preserve every failure and report accepted-risk, not verified success. This ends code delivery without merging or deleting the branch. A plain closing transition cannot bypass failed checks. For verified work, physical integration remains a separate authorized operation. The remaining closure steps are legacy compatibility.
Bounded paths
Quick/direct Hotfix/Tweak record changed files, focused command and result, persist test_result: pass, then transition to closing. Hotfix must prove the original symptom fixed. Lightweight also needs its receipt's focused review and passing verification evidence. These paths require no contract, execution plan, wave reviews, audit, DP-6/DP-7 or SSF finish.
Full / legacy Hotfix
- Verify the final code snapshot with required build/test/validation commands. Reuse fresh results only when the code, environment and command are identical; don't rerun the same full suite just because the skill changed.
- Check contract coverage, design consistency, scope and unresolved findings against the actual diff. Cite commands/results; do not infer success from edits or unchecked claims.
- Require the current plan's review policy: one final whole-range review for Native
final, or the required wave receipts forwave/legacy plans. Do not request a duplicate review of unchanged evidence. - Synchronize actual delta specs using spec-merger while executing. If specs were explicitly omitted and no delta exists, don't recreate them.
- Run
SSF audit <dir>and record verification outcome (dp_6_result, timestamp andtest_result). Record DP-7 only with the user's archive authorization already obtained or explicitly requested. Do not fabricate missing decisions. - With blockers resolved, run
SSF state transition <dir> closing. This is logical closure; it does not claim merge or cleanup succeeded.
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.
- 24d ago Changed · +4 lines 6fc33647e991
- 26d ago Changed · -146 lines 6658a329b3c1
- 1mo ago Changed be59c594560b
- 1mo ago First seen · 186 lines · 42 tokens per session scan A 6618ee8d5be8
release-archivist is a skill published in the GitHub repository MageByte-Zero/spec-superflow (867 stars, last pushed 17d ago), licensed MIT. It adds 42 tokens to every session and 973 once invoked, about $0.0002 per session on Opus 5.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
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
mlops-collaboration
Prepare a project for public collaboration — license, code of conduct, docs, branch rulesets, templates, and git-cliff releases. Use when open-sourcing a repository, onboarding contributors, or cutting a tagged release.
github-release
Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.
create-github-pull-request-from-specification
Create GitHub Pull Request for feature request from specification file using pullrequesttemplate.md template.
ship
Take a finished local change through verification, UI checks, pull-request publication, CI and review follow-up, and the user-authorized merge outcome. Use when implementation is complete and the user says "ship it" or "get this merged," or as the final stage of $build. Do not use to implement new feature scope.