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 agents/courtneyr-dev/meta-trac/docs-release-preppergit clone --depth 1 https://github.com/courtneyr-dev/meta-tracWrote 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/agents/courtneyr-dev/meta-trac/docs-release-prepper)<a href="https://agentmods.dev/agents/courtneyr-dev/meta-trac/docs-release-prepper"><img src="https://agentmods.dev/badge/agents/courtneyr-dev/meta-trac/docs-release-prepper.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 | $0.00000 | $0.00109 |
| Opus 5 | $0.00000 | $0.00055 |
| Sonnet 5 | $0.00000 | $0.00022 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
docs-release-prepper 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 21 lines · 0 tokens per session scan A 00a672ef901c
docs-release-prepper is an agent published in the GitHub repository courtneyr-dev/meta-trac (2 stars, last pushed 8mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 109 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 agents, from other repositories
deployment-specialist
Handles all deployment operations.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
release_agent
Agent with permissions to release Agent Brain packages. Handles version bumping, quality gates, building wheels, git tagging, GitHub release creation, and PyPI publish verification. Use when running /ag-brain-release or any release workflow.
release-architect
Sol architect for ambiguous, cross-application, security, authority, public-contract, and release-boundary decisions. Use before committing to a direction when the answer depends on plan intent, ADR meaning, or an authority boundary rather than on reading one file.
release
(stub) Capture project-specific guidance for release.