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-releasegit 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.01255 |
| Opus 5 | $0.00000 | $0.00628 |
| Sonnet 5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00126 |
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Phase 1 — Determine next release
-
Run
git statusand confirm the working tree is clean and onmaster. If not, stop and report the problem. -
Run
git tag --sort=-v:refnameto list existing tags. Identify the most recent tag matchingv*.*.*-*and extract its stadium codename. -
Read the A–Z stadium table from
CHANGELOG.mdto find the next stadium:- No tags yet: start at
A(first stadium in the table). - Normal case: use the stadium that follows the last used codename alphabetically. If letters were skipped, pick the next after the highest existing codename — do not backfill gaps.
- Last codename is
Z(Zentralstadion): the list is finite. Stop and refer to ADR 0012 for guidance on extending or revisiting the convention.
- No tags yet: start at
-
Read the
[Unreleased]section ofCHANGELOG.mdand infer the version bump using these rules (applied in order — first match wins):- Any entry contains the word BREAKING (case-insensitive), a
BREAKING CHANGE:token in a commit footer, or a!suffix after the commit type/scope (e.g.feat!:orfeat(scope)!:) → major bump - Any
### Addedsubsection has entries → minor bump - Otherwise (only
### Changed,### Fixed,### Removed) → patch bump
- Any entry contains the word BREAKING (case-insensitive), a
-
Compute the next version by applying the bump to the current latest tag's semver (e.g.
v2.1.0-dusseldorf+ minor →2.2.0). -
Present a summary for confirmation before continuing:
- Last tag and stadium
- Next version and stadium codename
- Bump type and the reasoning (what triggered it)
- Proposed tag:
vX.Y.Z-{stadium} - Proposed branch:
release/vX.Y.Z-{stadium}
Wait for explicit approval before proceeding to Phase 2.
Phase 2 — Prepare release branch
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 · 122 lines · 0 tokens per session scan A f5ca17f45e99
pre-release 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 1,255 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-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.
deploy
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
pre-commit
Before running the checklist, run git fetch origin. If the current branch is behind origin/master, stop and rebase before proceeding.
sonicjs-release-engineer
You are a specialized agent that manages npm package releases and dependency updates for SonicJS. Your primary responsibilities are.