Borrowing it
Nothing to install: this file belongs to ma2za/python-substack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ma2za/python-substack/main/.gemini/commands/release/verify.tomlgit clone --depth 1 https://github.com/ma2za/python-substackWrote 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/python-substack/verify)<a href="https://agentmods.dev/commands/ma2za/python-substack/verify"><img src="https://agentmods.dev/badge/commands/ma2za/python-substack/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.1 | $0.00000 | $0.00166 |
| Opus 5 | $0.00000 | $0.00083 |
| Sonnet 5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
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 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
description = "Verify a release candidate without publishing it"
prompt = """ Verify the current python-substack release candidate against GEMINI.md and docs/releasing.md. Inspect the worktree and version-bearing files first. Confirm pyproject.toml, substack/init.py, CHANGELOG.md, and the release page agree, and confirm the target version does not already have a Git tag.
Run all safe offline tests, collection checks, Poetry validation, build, distribution metadata checks, and base plus MCP wheel smoke checks that are possible in this environment. Do not run live Substack tests, publish, tag, push, create a GitHub release, or modify release content merely to make a check pass.
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.
- 3d ago First seen · 18 lines · 0 tokens per session scan A be9c6ca16707
verify is a command published in the GitHub repository ma2za/python-substack (168 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 166 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-09-03.
Other commands, from other repositories
speckit.spex.finish
Smoke test + squash + merge/keep (land the code on main).
4-close-project
Name: 4-close-project Purpose: Apply an OpenSpec change through TDD, verify it, prepare or update the PR, and leave archive for after merge.
explore-release
This legacy command is a rename notice only. Its workflow is now rpi-explore-release.
FinishQa
Release sign-off — verifies all TC outcomes recorded, no P0/P1 defects open, drafts plain-language release notes. Transitions ADO to Done.
publish-gate
Pre-publish smoke verification — pack, install into a tmpdir, run the configured smoke command, assert expected output. Catches the "code worked locally but the published tarball is broken" class of bug.
qa-ship
Run Phase 5 QA validation, acceptance testing, and release preparation.