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/yeaight7/agent-powerupsnpx agentmods add skills/yeaight7/agent-powerups/pre-release-verificationWrote 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/yeaight7/agent-powerups/pre-release-verification)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/pre-release-verification"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/pre-release-verification/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/yeaight7/agent-powerups/pre-release-verification"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/pre-release-verification.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.00022 | $0.00500 |
| Opus 5 | $0.00011 | $0.00250 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
pre-release-verification 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Block releases until the repository state, CI status, local validation, and publish metadata are known and reproducible.
When to Use
- Before creating a release tag.
- Before deploying to production.
- Before approving a release candidate prepared by another agent.
- When CI is green but local package or catalog checks still need proof.
Do not use as a substitute for fixing failures. If any gate fails, stop and report the blocker.
Inputs
- Intended version or deployment identifier
- Current branch and commit
- CI status for the release commit
- Project-specific build, lint, test, and packaging commands
Workflow
- Confirm the working tree is clean:
git status --short
- Confirm the release commit and recent history:
git log --oneline --decorate -n 10
- Confirm CI is green for the exact commit. For GitHub:
gh run list --limit 5
gh run view <run-id> --json conclusion,status,headSha,url
- Run local validation. Use the project's documented commands, for example:
npm run build
npm test
python scripts/validate-skills.py
python scripts/validate-catalog.py
- Check for secrets or accidental local files:
git diff --stat
git status --short
- Report go/no-go with exact evidence.
Output
RELEASE VERIFICATION: go / no-go
Commit: <sha>
CI: <status and URL>
Local checks: <commands and results>
Blockers: <none or list>
Next action: <tag / deploy / stop>
Verification
- Working tree was clean or dirty files were reported.
- CI status was tied to the exact release commit.
- Local validation commands exited 0.
- No secrets or accidental local files were included.
- Go/no-go recommendation included evidence, not confidence.
Failure Modes
- Releasing from an uncommitted or untracked local state.
- Checking CI for a different commit than the release candidate.
- Treating lint/build success as full test coverage.
- Continuing after a failed gate because the release is "small".
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 · 90 lines · 22 tokens per session scan A 3a4311fd442f
pre-release-verification is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 22 tokens to every session and 500 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 skills, from other repositories
github-repo-management
Clone, create, fork repos; manage remotes, releases.
project-release-check
Validate this example project's release readiness. Use before publishing a release candidate.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
github
Use the GitHub CLI (gh) to inspect and manage repositories, pull requests, issues, workflows, releases, and API calls from the terminal. Use when a user asks to use gh/GitHub CLI, run GitHub repo or PR workflows, automate GitHub Actions from shell, or troubleshoot gh authentication and configuration.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
plugin-publish
A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.