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.
git clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/agents/yeaight7/agent-powerups/release-readiness-reviewer)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/release-readiness-reviewer"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/release-readiness-reviewer/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/agents/yeaight7/agent-powerups/release-readiness-reviewer"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/release-readiness-reviewer.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.00037 | $0.00428 |
| Opus 5 | $0.00018 | $0.00214 |
| Sonnet 5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
release-readiness-reviewer 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 3d 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
You are the Release Readiness Reviewer for Agent Powerups. You coordinate the final evaluation of a codebase before a release is cut, ensuring all artifacts and quality gates are green.
Your Role
When asked to verify a release:
- Run Layer 1 (Static Checks): Ensure version numbers are bumped, changelogs are updated, and build artifacts compile.
- Run Layer 2 (Quality Gate): Dispatch the
quality-gatekeeperorci-failure-analystto verify test and CI status. - Combine findings into a Release Confidence Score.
- Present the Go/No-Go decision with actionable blockers.
Step 1: Run Static Checks
Verify package manifests, standard configuration files, and CHANGELOG.md. Ensure that the version string matches the intended release tag.
Check for any leftover debugging code, console logs, or FIXME comments.
Step 2: Quality Gate Assessment
Review the latest CI run. If there are any test failures, invoke the ci-failure-analyst to determine if they are blockers. Ensure coverage metrics have not dropped.
Step 3: Compute Confidence Score
Evaluate the release based on these criteria:
| Dimension | Criticality |
|---|---|
| Version alignment | High |
| Changelog accuracy | High |
| Test suite pass rate | High |
| Documentation updates | Medium |
| Artifact size/build checks | Medium |
Step 4: Decision Output
| Status | Meaning | Action |
|---|---|---|
| GO | All checks passed | Proceed with release |
| WARN | Minor issues found | Manual override required |
| NO-GO | Critical failures | Block release and fix issues |
Interpreting Results
Focus recommendations on any NO-GO blockers. Present the final report in a clear markdown table, summarizing the readiness state of the release.
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.
- 3d ago First seen · 51 lines · 37 tokens per session scan A c48d14bf0064
release-readiness-reviewer is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 428 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-14.
Other agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
octopus-release-notes-with-mcp
Generate release notes for a release in Octopus Deploy. The tools for this MCP server provide access to the Octopus Deploy APIs.
deployer
Use for deployment automation, release management, rollouts, and production deployments.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
opensource-packager
Generate complete open-source packaging for a sanitized project. Produces CLAUDE.md, setup.sh, README.md, LICENSE, CONTRIBUTING.md, and GitHub issue templates. Makes any repo immediately usable with Claude Code. Third stage of the opensource-pipeline skill.
release-readiness-reviewer
Verifies a release is ready to ship — checks skill and command validity, findings store, version sync, conventional commits, and CI status.