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/commands/yeaight7/agent-powerups/release-check)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/release-check"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/release-check/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/commands/yeaight7/agent-powerups/release-check"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/release-check.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.00024 | $0.00335 |
| Opus 5 | $0.00012 | $0.00168 |
| Sonnet 5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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 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
Release Readiness Certification
Run the complete Agent Powerups release pipeline to ensure the repository is ready for a new version tag.
Process Overview
This command orchestrates a full readiness review.
1. Artifact Verification
- Check that the
package.json,Cargo.toml, or relevant manifests contain the target version$ARGUMENTS. - Ensure
CHANGELOG.mdhas an entry for the target version, with categorized changes (Features, Fixes, Breaking).
2. Deep Quality Gate
- Trigger a full test suite run including integration and end-to-end tests if available.
- Ensure zero linting errors and clean type checks.
- Verify that there are no remaining FIXME, TODO(release), or unresolved merge conflict markers.
3. Dependency Audit
- Run a quick security audit on dependencies.
- Flag any critical vulnerabilities that must be resolved before cutting the release.
4. Certification Badge
Assign a confidence badge based on the results:
| Badge | Criteria |
|---|---|
| 🟢 Ready | All versions match, changelog is perfect, tests pass, no vulnerabilities. |
| 🟡 Warn | Tests pass, but changelog lacks detail or minor dependency warnings exist. |
| 🔴 Blocked | Tests fail, versions mismatch, or critical security vulnerabilities found. |
Output
Generate a comprehensive Release Certification markdown report detailing the findings in each phase and explicitly stating the final Go/No-Go decision.
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 · 40 lines · 24 tokens per session scan A bc60bab222db
release-check is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 24 tokens to every session and 335 once invoked, about $0.0001 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 commands, from other repositories
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
release
Verify, write the CHANGELOG, cut a version — then hand the release sequence back.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
t800-update
A command for updating the T-800 agent system from its GitHub repository. GitHub is a service for storing and versioning code.
release
Automates the release preparation and CI/CD handoff process.
ship
Puts approved code into production and closes the cycle. PR + CI + deploy + simplify + docs + cleanup. Use after /fractal:review approves.