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 marchatton/agent-skills --skill wf-releasegit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/marchatton/agent-skills/wf-release)<a href="https://agentmods.dev/skills/marchatton/agent-skills/wf-release"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/wf-release/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/marchatton/agent-skills/wf-release"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/wf-release.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.00039 | $0.00499 |
| Opus 5 | $0.00019 | $0.00249 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
wf-release 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 7d 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.
What it actually says
wf-release
Purpose
Ship changes safely with a minimal release checklist, changelog/release notes, and post-release verification.
Prefer prd.json as the source of truth for what shipped (user story IDs + acceptance criteria).
plan.md may exist for rollout/rollback notes, but it’s optional.
Inputs
- Plan/PRD acceptance criteria (prefer
prd.json) - Release scope + rollout constraints
- Monitoring + rollback requirements
- Target repo + branch/PR
Outputs
- Release notes / changelog entry / post-release notes (as needed)
- GO/NO-GO decision with verification evidence
- Optional learning entry via
compound-docs
Steps
- (Recommended) Pickup if starting fresh thread / resuming
- Invoke
pickupif repo/branch/PR state is not fresh.
- Confirm scope + rollout shape Capture:
- what is shipping (and what is not)
- rollout strategy (flags, staged, canary)
- rollback steps (including data)
- monitors to watch
- link to
prd.json(and plan.md if present)
- Pre-release verification (mandatory)
- Run verify skill.
- If verify fails: NO-GO unless user explicitly accepts risk.
- Release artefacts
- Draft release notes / changelog entry (keep it short, user-facing)
- Prefer listing shipped stories by ID (US-xxx) from
prd.json - Note any operator actions (migrations, flags, config)
- Post-release verification
- State what to check after deploy (smoke checks + metrics)
- If available, record evidence (screenshots/logs)
- Compound (recommended when non-trivial)
- If anything surprising happened (flaky tests, rollout gotcha, weird failure mode): suggest
compound-docs
- Context boundary (recommended) If handing off to another agent/person or switching workflows:
- invoke
handoff - recommend new thread for next work:
/newthenpickup
Verification
- Verify skill run pre-release (required).
Go/No-Go
- GO if verify is green, rollback plan exists, and monitors listed.
- NO-GO otherwise.
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.
- 7d ago First seen · 70 lines · 39 tokens per session scan A bbec796b0a88
wf-release is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 499 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.