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/madarco/agentbox/release-notesgit clone --depth 1 https://github.com/madarco/agentboxWhat 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.00070 | $0.04336 |
| Opus 5 | $0.00035 | $0.02168 |
| Sonnet 5 | $0.00014 | $0.00867 |
| Haiku 4.5 | $0.00007 | $0.00434 |
Grade C, and why
release-notes scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
git diff --no-index "$tmp/package/dist/index.d.ts" packages/provider-sdk/dist/index.d.ts; rm -rf "$tmp" How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are writing the next release-notes entry for @madarco/agentbox. The
changelog is at apps/cli/CHANGELOG.md (Keep a Changelog format). Produce
short, user-facing notes — not a commit dump.
If $ARGUMENTS is nightly, skip to section 9 — a nightly is a different
flow (pre-release version, [Unreleased] instead of a version heading, no git
tag, --tag nightly on the publish). Sections 1-3 still apply for gathering and
curating the notes; 4, 5, 6 and 8 do not.
1. Find the range
- Last release anchor:
git describe --tags --abbrev=0(e.g.v0.9.0). If that fails (no tags), fall back to the lastNew releasecommit:git log --grep='^New release$' -1 --pretty=%H. - The range is
<anchor>..HEAD.
2. Gather material (not just subjects)
git log <anchor>..HEAD --no-merges --pretty=format:'===%h %s%n%b'— read the bodies, they carry the real "why".git log <anchor>..HEAD --stat --oneline— gauge surface area.- If a commit message is thin but the diff looks user-visible, inspect it with
git log -1 -p <hash> -- <path>.
3. Curate — this is the point
- Drop noise: merge commits, CI / typecheck / lint / bugbot fixes, version bumps, and internal refactors or doc/copy tweaks with no user-visible effect.
- Merge related commits into a single bullet (e.g. several
feat(vercel)/fix(cloud)commits → one "Vercel provider" line). Aim for a handful of bullets per heading, not one per commit. - Group under these headings, in this order, omitting any that are empty:
### Breaking,### Added,### Changed,### Fixed,### Removed. - Rewrite for a CLI user: what changed for someone running
agentbox, terse, past tense, no commit hashes. Mention the flag / config key / command name when relevant. Call out anything that breaks existing scripts under Breaking.
4. Pick the version
- Decide the bump from the commits: any breaking change → minor while pre-1.0
(note it under Breaking), any
feat→ minor, else patch. Compute the next version from the currentapps/cli/package.jsonversion. - If
$ARGUMENTSnames a bump (patch/minor/major), use that instead.
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 · 308 lines · 70 tokens per session scan C e547c5889915
release-notes is a command published in the GitHub repository madarco/agentbox (378 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 4,336 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
cleanup
Clean up TTS cache files to free up disk space.
deps-age
Analyze dependency freshness and maintenance activity.
test-summary
Command "test-summary" from vishnu2kmohan/mcp-server-langgraph, covering generate comprehensive test summary, 🧪 test summary generation, step 1: determine test scope, step 2: run tests and collect results and run tests with json output.
release-prep
Automated release readiness validation.