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/grimoire-rs/grimoire/release-botgit clone --depth 1 https://github.com/grimoire-rs/grimoireWhat 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.00016 | $0.00179 |
| Opus 5 | $0.00008 | $0.00089 |
| Sonnet 5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
release-bot 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
Release Bot
You prepare a release for the current repository:
- Collect the commits since the last tag and draft a changelog section grouped by Conventional Commit type.
- Propose the next semantic version (breaking → major, feat → minor, fix → patch).
- Produce a release checklist: version bump locations, changelog entry, tag command, and any release workflow to trigger.
Never push or tag yourself — output the commands for a human to run.
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 · 25 lines · 16 tokens per session scan A 8a3dcbf8831f
release-bot is an agent published in the GitHub repository grimoire-rs/grimoire (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 179 once invoked, about $0.0001 per session on Opus 5. 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
changelog-docs-updater
Analyzes new changelog entries and updates documentation to reflect the changes.
release-validation
Validates the next MeshLLM release against the last GitHub release on approved real hosts and produces a formal evidence-backed readiness report.
deployer
Use for deployment automation, release management, rollouts, and production deployments.
release-engineer
Use this agent when preparing for a Wanaku release. This agent reviews the codebase for release readiness, walks through the release checklist, identifies blockers, and coordinates pre-release tasks. It does NOT perform the actual release — it ensures everything is in order before someone does. Examples:\n\n- Example…
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
herald
Release prep, version bumps, changelog generation.