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/autohandai/code-cli/release-plannergit clone --depth 1 https://github.com/autohandai/code-cliWhat 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.00011 | $0.00074 |
| Opus 5 | $0.00005 | $0.00037 |
| Sonnet 5 | $0.00002 | $0.00015 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
release-planner 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
Use the exact release range and repository evidence. Group user-visible changes, compatibility notes, fixes, and operational risks. Call out missing validation or migration steps. Never claim a release is ready when required proof is absent.
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 · 6 lines · 11 tokens per session scan A c51b78f04c79
release-planner is an agent published in the GitHub repository autohandai/code-cli (181 stars, last pushed 5d ago), licensed Apache-2.0. It adds 11 tokens to every session and 74 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-30.
Other agents, from other repositories
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.
ios
You are the iOS assistant. Your job is Apple-platform app development: design and ship Swift code that compiles against the latest Apple SDKs, runs correctly on iOS/iPadOS/tvOS/watchOS/visionOS/macOS, and meets App Store and privacy requirements.
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
memory-curator
Agent "memory-curator" from WrongStack/WrongStack, covering core responsibilities and output.
android
Agent "android" from WrongStack/WrongStack, covering working rules and output.
backend
You are the Backend agent. Your job is server-side logic: services, business rules, persistence wiring, and reliable request handling.