Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/flurdy/agent-skillsnpx agentmods add skills/flurdy/agent-skills/release-managerWrote 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/flurdy/agent-skills/release-manager)<a href="https://agentmods.dev/skills/flurdy/agent-skills/release-manager"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/release-manager/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/flurdy/agent-skills/release-manager"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/release-manager.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 11 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.03726 |
| Opus 5.5 | $0.00018 | $0.01490 |
| Sonnet 5.5 | $0.00009 | $0.00745 |
| Haiku 4.5 | $0.00005 | $0.00373 |
Grade A, and why
release-manager 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 today.
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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager
One invocation is one attended tick. Readiness is advisory; a READY result is not permission to
push. One immediate explicit answer authorizes one visible command, never a batch or a later tick.
For a passive dashboard use /release-status; /watch-release schedules this skill unchanged.
Usage
/release-manager
/release-manager web
Ownership
ready-to-release/scripts/release-gatesalone collects, normalizes, and evaluates release gates. Do not recompute them, fall back to independent checks, or override a hold with local tests.- This skill owns the attended push decision, local release decisions/rollout tracking, CI-failure tracking, and cadence. It never repairs setup, reconciles manifests, syncs configuration, restarts workloads, or flips flags. Missing adapters are a setup handoff, not an automatic fix.
/release-maintenanceowns explicitly requested reconciliation, config sync, restart, and evidence-backed rollout acknowledgement. Never invoke it from a manager/watch tick, even when the user answers a tick question. A maintenance request ends this tick with a handoff instead.- Run one active manager per project state file. Persist state only through the
release-statehelper below, never with Write, an editor or shell redirection. Aconflictmeans another writer changed the file: read again and redecide from fresh state, never resend the same patch blindly. Conflicts or malformed state pause mutations, never trigger a reset. Do not guess ownership from file age.
The shared evidence contract defines adapter
setup expectations and all release policy. release-ci and release-order remain supporting
adapters here, but only the readiness helper invokes them through the project collection contract.
State
.release-state.json stays local and gitignored. Read and write it only through the helper, from
the verified project root:
~/.agents/skills/release-manager/scripts/release-state read
~/.agents/skills/release-manager/scripts/release-state update --owner manager --expect <sha256|missing> --patch '<json>'
What ships with it
8 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.
- today Changed · +3 lines 0c09606c3ba1
- yesterday Changed · +40 lines 5a13b2d777ae
- 3d ago Changed · +46 lines · +1 tokens per session 5fbe2c9cc010
- 1mo ago Changed · -400 lines · -48 tokens per session de24734f3a62
- 1mo ago First seen · 556 lines · 93 tokens per session scan A 94e24eaf1b16
release-manager is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 3,726 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-31.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
factory-ship
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.