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 agentmods add commands/ma2za/google-news-api/release-verifygit clone --depth 1 https://github.com/ma2za/google-news-apiWrote 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/ma2za/google-news-api/release-verify)<a href="https://agentmods.dev/commands/ma2za/google-news-api/release-verify"><img src="https://agentmods.dev/badge/commands/ma2za/google-news-api/release-verify.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 | $0.00000 | $0.00195 |
| Opus 5 | $0.00000 | $0.00097 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
release-verify 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 4d 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
Verify a release candidate
Read AGENTS.md, the entire .agents/PRIVATE_RELEASE_PLAN.md,
.agents/FAILURE_RETROSPECTIVE.md, and docs/releasing.md. Inspect the
worktree and version-bearing files first.
Confirm pyproject.toml, CHANGELOG.md, README examples, the selected private
plan release, the latest published PyPI version, and Git tags agree. Confirm the
target version has not already been used.
Run all safe offline tests, collection checks, pre-commit checks, Poetry validation, builds, distribution metadata checks, and base plus MCP wheel smoke checks possible in the environment. Do not modify release content merely to make a check pass.
Do not publish, tag, push, create a GitHub release, or run live integration tests unless the maintainer explicitly requests those actions.
Report failures first, then successful checks and the exact remaining manual or CI-gated release steps.
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.
- 4d ago First seen · 21 lines · 0 tokens per session scan A 09afc7cd2c1a
release-verify is a command published in the GitHub repository ma2za/google-news-api (17 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 195 tokens. 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-30.
Other commands, from other repositories
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
ship
Deliver the increment. Then go live with a rollback you have run.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
release-tag
Create and push a version tag after a release PR has been merged.
release
Orchestrate a complete release workflow with quality gates, version bumping, and publishing automation.