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 bradlay/claude-code-recipes --skill release-readinessgit clone --depth 1 https://github.com/bradlay/claude-code-recipesWrote 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/bradlay/claude-code-recipes/release-readiness)<a href="https://agentmods.dev/skills/bradlay/claude-code-recipes/release-readiness"><img src="https://agentmods.dev/badge/skills/bradlay/claude-code-recipes/release-readiness/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/bradlay/claude-code-recipes/release-readiness"><img src="https://agentmods.dev/badge/skills/bradlay/claude-code-recipes/release-readiness.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.00085 | $0.00957 |
| Opus 5.5 | $0.00034 | $0.00383 |
| Sonnet 5.5 | $0.00017 | $0.00191 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
release-readiness 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 18d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness
Answer in one auditable pass: is this upgrade or promotion already done, and if not, is it safe to do? This skill is read-only. It never bumps, commits, promotes, or closes PRs; it says which of those is safe.
Arguments: an optional free-text [target-bump] (for example
"framework 7 / bundler 8") that turns on the compatibility step. Ask which
branches are involved if the repository has more than one long-lived branch
(call them <lower> and <upper>, for example develop and main).
Steps: run each, quote the raw result, never assert from memory
- Divergence, by content. Ahead/behind commit counts mislead: after
squash or rebase merges, a branch can be "behind" while holding all the same
content. Compare content instead:
git fetchfirst.git diff --stat <upper>...<lower>: what<lower>would bring.git diff --stat <lower>...<upper>: content on<upper>that<lower>never had. Non-empty means real divergence; investigate it before any promotion.
- Dependency-bot PRs (needs
gh):gh pr list --state open --author app/dependabot(or your bot). For each, compare the target version with the lockfile on the base branch:- SUBSUMED: the base already has the target or newer, so the PR is redundant.
- PENDING: the bump is still outstanding.
- OVERRIDE-CONFLICT: a resolution or override rule pins below the target, so the override must change first.
- UNKNOWN: grouped, lockfile-only, or unparseable. Inspect by hand; never count it as done.
- Compatibility, only when
[target-bump]is given or step 2 shows PENDING:- Outdated check with the ecosystem's tool (see dependency-scan).
- Peer-dependency and engine constraints for the bump (the package's
peerDependencies, required runtime versions, any platform compatibility date your deployment target uses). Cite the release notes you used.
- The project's own gates, if it has them. CI status on the branch head
(
gh run list --branch <lower> --limit 5), open issues labeled as release blockers, any security-scan results. Report what is live; do not assume a clean board. - Environment consistency, if relevant. For multi-service or multi-env repositories, differences in configuration between environments that the promotion would expose.
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.
- 18d ago First seen · 73 lines · 85 tokens per session scan A 7d42e2219a36
release-readiness is a skill published in the GitHub repository bradlay/claude-code-recipes (2 stars, last pushed 4d ago), licensed MIT. It adds 85 tokens to every session and 957 once invoked, about $0.0003 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-10-17.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…