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/python-substack/preparegit 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/prepare)<a href="https://agentmods.dev/commands/ma2za/python-substack/prepare"><img src="https://agentmods.dev/badge/commands/ma2za/python-substack/prepare.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.00216 |
| Opus 5 | $0.00000 | $0.00108 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
prepare 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 2d 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 = "Prepare a versioned release candidate without publishing it"
prompt = """ Prepare python-substack release {{args}} end to end, stopping before commit, tag, push, GitHub release creation, PyPI publication, or announcement.
Read GEMINI.md, docs/releasing.md, CHANGELOG.md, pyproject.toml, substack/init.py, the relevant Git history, and the current worktree first. Require one explicit semantic version argument and refuse to reuse an existing version or tag. Preserve unrelated worktree changes.
Implement any remaining release preparation that is supported by the actual changes: synchronize the version in pyproject.toml and substack/init.py, add the top CHANGELOG.md entry, and create docs/releases/.md. Do not invent features or claims. Run the offline validation and package checks from docs/releasing.md that are safe in the current worktree. Do not run live tests.
Finish with the changed files, exact validation results, unresolved blockers, and the maintainer actions still required before publication. """
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.
- 2d ago First seen · 21 lines · 0 tokens per session scan A 684e9cc361f3
prepare is a command published in the GitHub repository ma2za/python-substack (168 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 216 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
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
release
Create a stable release using the automated justfile target with comprehensive validation.
beta
Create a new beta release using the automated justfile target with quality checks and tagging.
changelog
Analyze commits and generate formatted changelog entry for a version.
release-check
Comprehensive pre-flight check for release readiness without making any changes.
release-prepare
Require one explicit semantic version argument. Refuse an existing published version or Git tag.