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 MotWakorb/ai-agent-dev-team --skill release-checkgit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/motwakorb/ai-agent-dev-team/release-check)<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/release-check"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/release-check.svg" alt="Measured on agentmods" 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.00040 | $0.01320 |
| Opus 5 | $0.00020 | $0.00660 |
| Sonnet 5 | $0.00008 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
release-check 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness Check
Release-execution agents fire on mechanical triggers ("PRs merged, branch protection on"). This skill validates the semantic state mechanical triggers miss: are there open P0/P1 bugs the release would skip, verification agents still running, PRs awaiting review? The PO is the decider; this skill produces the checklist.
See _shared/orchestration.md §"Pre-Release Semantic Checks" for the underlying rule.
Model Selection
This skill runs as the orchestrator — no persona dispatches. Model inherits from the parent. If a specific item on the checklist needs a persona's read ("is this CVE release-blocking at our tier?"), spawn that persona separately at sonnet.
Preflight
- Identify the release. Version, tag, or branch. If the PO invoked
/release-check 0.17.0, use that. If bare, ask. - Identify sprint scope. Look for
docs/sprint-scope.md,SPRINT.md, or a label convention in the bead system. If unclear, ask: "What's the sprint label or milestone for this release?" - Identify the bead system. Default:
bdifbd listsucceeds. Otherwise, ask the PO how to query open bugs.
Process
Step 1: Query open bugs in sprint scope
bd list --status open --priority 0 --label sprint:<sprint>
bd list --status open --priority 1 --label sprint:<sprint>
Adjust syntax for the actual bead system. Record counts and IDs per priority.
Step 2: Check in-flight verification agents
Identify any agents the orchestrator spawned for QA, security review, code review, or test verification that are still running against artifacts this release would include. Record agent IDs and what they're verifying.
Step 3: Check open PRs targeting the release branch
gh pr list --search "is:open base:<release-branch>" --json number,title,reviewDecision,statusCheckRollup
Open PRs targeting the release branch are decisions the release would skip. Record numbers and states.
Step 4: Check security gate state
If the project uses CodeQL or similar, verify the last scan on the release branch is green. If gated to main only, note that the release-cut PR to main is the validation point.
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 · 88 lines · 40 tokens per session scan A 3261a9035a00
release-check is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 25d ago), licensed MIT. It adds 40 tokens to every session and 1,320 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-08-31.
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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.