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 Sistema2D/FrameCode-VibeWork --skill release-checklistgit clone --depth 1 https://github.com/Sistema2D/FrameCode-VibeWorkWrote 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/sistema2d/framecode-vibework/release-checklist)<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/release-checklist"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/release-checklist/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/sistema2d/framecode-vibework/release-checklist"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/release-checklist.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.00463 |
| Opus 5.5 | $0.00018 | $0.00185 |
| Sonnet 5.5 | $0.00009 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
release-checklist 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 1mo 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.
Release checklist
Purpose
Prepare and validate an application or FCVW framework release while keeping version namespaces, migration, rollback, evidence, and publication authority coherent.
Use conditions
Use for version selection, release-record assembly, tag/release preparation, or publication closeout. Read-only version questions do not authorize a release mutation.
First decision
Classify the release:
- Application: use
changelogs/and the application's version source. - Framework: use
framework-releases/,FRAMEWORK_LOCK.md,OWNERSHIP.md, andMIGRATIONS.md.
Never mix the namespaces.
Inputs
Completed plans, unreleased fragments, target version, test evidence, deployment/rollback information, and publication authority.
Procedure
- Select included plans and confirm states.
- Decide semantic bump and compatibility.
- Assemble the appropriate release record from its template.
- Check version source and related links.
- Run application tests and governance validation appropriate to risk.
- Confirm migration, backup, deployment, and rollback where applicable.
- Publish only after target validation and explicit authority.
- Record external tag/release evidence separately.
Framework-specific checks
- role manifest/ownership is current;
- clean artifact excludes project records and comparison fixtures;
- schema changes have migrations;
- clean-template validator passes;
- downstream preservation paths are documented;
- artifact checksum is recorded.
Non-responsibilities
- inferring permission to push, tag, deploy, or publish;
- claiming external publication without evidence;
- bumping the application version for a governance-only framework update by default.
Required output
Release type, version, included plans, validation, migration/rollback, publication state, and residual gaps.
Validation and exit
The record is internally coherent, blocking gates pass, and published is used only after actual publication.
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.
- 1mo ago Changed · -6 lines · +34 tokens per session f70d262dc809
- 2mo ago First seen · 72 lines · 12 tokens per session scan A 969a51934a65
release-checklist is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (29 stars, last pushed 29d ago), licensed Apache-2.0. It adds 46 tokens to every session and 463 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
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
forge-deliver
An orchestration layer for coordinating a complete software delivery process from a request through release and documentation.
forge-ship
A release workflow for Git projects that either opens a pull request or merges it and synchronizes the local base branch. It distinguishes submitted, pushed, merged, and deployed states.
ensemble-release
Automated release workflow orchestration with quality gates, smoke test integration, (Codex skill for /ensemble:release).