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/nanotaboada/python-samples-fastapi-restful/pre-releasegit clone --depth 1 https://github.com/nanotaboada/python-samples-fastapi-restfulWhat 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.00780 |
| Opus 5 | $0.00000 | $0.00390 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
pre-release 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-release checklist
Run the pre-release checklist for this project.
Working style: propose before acting at every step — do not commit, push, open PRs, or create tags until I explicitly confirm.
Phase 1 — Determine next release
-
Verify working tree: Confirm we are on
masterwith a clean working tree. If behind the remote, proposegit pulland wait for confirmation before pulling. -
Detect current release and propose next: Read
CHANGELOG.mdfor the coach naming convention (A–Z table) and the most recent release heading. Rungit tag --sort=-v:refnameto confirm the latest tag. Then:-
Next codename: next letter in the A–Z sequence after the current one. Use lowercase with no spaces for the tag (e.g.
eriksson); Title Case for the CHANGELOG heading (e.g.Eriksson). If no tags exist yet, start atA(first coach in the table). If letters were skipped, pick the next after the highest existing codename — do not backfill gaps. If the last codename isZ(Zeman), the list is finite — stop and flag that the naming convention needs to be revisited. -
Version bump — infer from
[Unreleased]:Condition Bump Any entry marked BREAKING (case-insensitive), BREAKING CHANGE:token in a commit footer, or!suffix after type/scope (e.g.feat!:)MAJOR Entries under Added MINOR Only Changed / Fixed / Removed PATCH -
If
[Unreleased]has no entries, stop and warn — there is nothing to release.
Present a summary before proceeding:
Current: v2.1.0-delbosque Proposed: v2.2.0-eriksson (MINOR — new features in Added) Branch: release/v2.2.0-eriksson Tag: v2.2.0-eriksson -
Phase 2 — Prepare release branch
-
Create release branch:
release/vX.Y.Z-{codename}. -
Update CHANGELOG.md: Move all content under
[Unreleased]into a new versioned heading[X.Y.Z - Codename] - {today's date}. Replace[Unreleased]with a fresh empty template:
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 · 89 lines · 0 tokens per session scan A 6c3bc13cfd91
pre-release is a command published in the GitHub repository nanotaboada/python-samples-fastapi-restful (137 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 780 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
add-endpoint
Scaffold a new API endpoint with full layering.
review
Review code changes against project conventions.
reparent
Rebase alembic migrations to maintain a linear history when multiple heads exist.
checkpoint
Create a checkpoint by staging the changes you have made using git. usage: git [-v | --version] [-h | --help] [-C ] [-c = ] [--exec-path[= ]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir= ] [--work-tree= ] [--namespace= ] [--super-prefix= ]…
update-docs
Given the changes in the current branch, update the docs in @tracecat/docs where necessary.
pre-release
Run the pre-release checklist for this project. Work through all three phases in order, pausing for explicit confirmation at each decision point before proceeding. Never create a branch, commit, tag, or push without approval.