google-news-api: Command for Claude Code

.agents/commands/release-verify.md

release-verify is a command for Claude Code from ma2za/google-news-api. It costs 0 tokens per session (192 once invoked), scanned A, original, MIT.

A release-checking command that inspects project instructions, release plans, documentation, version files, packages, and Git tags. A release candidate is a version that is nearly ready to publish.

In plain words
What is it for?
Use it to verify a Python release candidate with offline tests, metadata checks, builds, pre-commit checks, and wheel smoke tests. It reports failures and lists remaining manual or CI-only steps.
Why use it?
It catches mismatched versions, missing release information, and build or packaging problems before publication. It also keeps publishing and other irreversible release actions under maintainer control.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is ma2za/google-news-api's own configuration. It tells Claude Code how to work on google-news-api itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything google-news-api configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ma2za/google-news-api. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ma2za/google-news-api/main/.agents/commands/release-verify.md
Clone the repo
git clone --depth 1 https://github.com/ma2za/google-news-api

Made for: Claude Code.

Wrote 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.

agentmods badge for release-verify

README.md
[![agentmods](https://agentmods.dev/badge/commands/ma2za/google-news-api/release-verify/github.svg)](https://agentmods.dev/commands/ma2za/google-news-api/release-verify)
Your own site
<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/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.

agentmods 80×15 button for release-verify

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 192 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00192
Opus 5.5 $0.00000 $0.00077
Sonnet 5.5 $0.00000 $0.00038
Haiku 4.5 $0.00000 $0.00019

Measured 28d ago against content hash 4c215188a847, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 28d 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.

.agents/commands/release-verify.md · 21 lines

What it actually says

Verify a release candidate

Read AGENTS.md, the entire 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 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.

Changes

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.

  1. 28d ago Changed 4c215188a847
  2. 2mo ago First seen · 21 lines · 0 tokens per session scan A 09afc7cd2c1a

Subscribe to this mod's changes

release-verify is a command published in the GitHub repository ma2za/google-news-api (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 192 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.

Related

release-verify compared with commands from other repositories

release-verify next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-verifyma2za/google-news-apiCommand02d agoMITA0Claude Code
releaseexistential-birds/beagleCommand851mo agoApache-2.0A12Claude Code
release-tagexistential-birds/beagleCommand851mo agoApache-2.0A11Claude Code
deployNickRomanek/clawbridgeCommand2319d agoApache-2.0A0Claude Code
releasegeekatron/jerryCommand375d agononeA0Claude Code
plan-release-trainPranavNagrecha/AwesomeSalesforceSkillsCommand2616d agononeA0Claude Code
release-notesPranavNagrecha/AwesomeSalesforceSkillsCommand2616d agononeA0Claude Code