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/dotnet.samples.aspnetcore.webapi/pre-commitgit clone --depth 1 https://github.com/nanotaboada/Dotnet.Samples.AspNetCore.WebApiWhat 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.00342 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
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 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
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
dotnet build --configuration Release— must succeed. - Run
dotnet test --settings .runsettings— all tests must pass. - If
dotnet csharpieris available, rundotnet csharpier --check .— must pass (rundotnet csharpier .to auto-fix). Skip this step with a note if not installed. - 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–4, report the results clearly, then run step 5 (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.
- 2d ago First seen · 16 lines · 0 tokens per session scan A 95228f0ff853
pre-commit is a command published in the GitHub repository nanotaboada/Dotnet.Samples.AspNetCore.WebApi (10 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 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-31.
Other commands, from other repositories
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.
pre-commit
Before running the checklist, run git fetch origin. If the current branch is behind origin/master, stop and rebase before proceeding.
pre-release
Run the pre-release checklist for this project.
pre-commit
Before running the checklist, run git fetch origin. If the current branch is behind origin/master, stop and rebase before proceeding.
make-avaloniaui-custom-control
HTML/CSS to AvaloniaUI AXAML conversion command.
dumpstack
Helps examine thread call stacks. While clrstack is more commonly used for managed call stacks, dumpstack can also be used to inspect stack frames, including native ones.