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-commitgit 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.00377 |
| Opus 5 | $0.00000 | $0.00188 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
pre-commit 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 yesterday.
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
Pre-commit checklist
Before running the checklist, run git fetch origin. If the current branch is behind origin/master, stop and rebase before proceeding.
Run the pre-commit checklist for this project:
- Update
CHANGELOG.md[Unreleased]section — add an entry under the appropriate subsection (Added / Changed / Fixed / Removed) describing the changes made, referencing the issue number. - Run
uv run flake8 .— must pass. - Run
uv run black --check .— must pass (runuv run black .to auto-fix). - Run
uv run pytest --cov=./ --cov-report=term --cov-fail-under=80— all tests must pass, coverage must be ≥80%. - If Docker is running, run
docker compose build— must succeed with no errors. Skip this step with a note if Docker Desktop is not running. - If
coderabbitCLI is installed, runcoderabbit review --type uncommitted --prompt-only:- If actionable/serious findings are reported, stop and address them before proposing the commit.
- If only nitpick-level findings, report them and continue to the commit proposal.
- If
coderabbitis not installed, skip this step with a note.
Run steps 1–5, report the results clearly, then run step 6 (CodeRabbit review) if available, then propose a branch name and commit message for my approval using the format type(scope): description (#issue) (max 80 chars; types: feat fix chore docs test refactor ci perf). Do not create the branch or commit until I explicitly confirm.
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.
- yesterday First seen · 21 lines · 0 tokens per session scan A 66cc7aea62de
pre-commit is a command published in the GitHub repository nanotaboada/python-samples-fastapi-restful (137 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 377 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.