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/zhu-xiaowei/baton/packagegit clone --depth 1 https://github.com/zhu-xiaowei/BatonWhat 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.00013 | $0.00183 |
| Opus 5 | $0.00006 | $0.00092 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
package 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
Build the release packages for the current package.json version and copy them
into release/<version>/ as Baton.apk, Baton.dmg, Baton.exe.
Run the packaging script (it reads the version itself, builds all three platforms independently, and copies the artifacts):
bash scripts/package-all.sh
This takes several minutes (each platform compiles Rust). When it finishes,
report the SUMMARY block verbatim — which platforms succeeded, where each file
landed and its size, and any that failed. Do not re-run failed platforms
unless asked. iOS is intentionally excluded (separate TestFlight flow via
npm run release:ios).
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 · 21 lines · 13 tokens per session scan A db76ad7dd730
package is a command published in the GitHub repository zhu-xiaowei/Baton (9 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 183 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 commands, from other repositories
querying
Query documents from a search index using type-safe filters with support for pagination, sorting, field selection, scoring, and highlighting. Count matching documents efficiently without returning results.
index-management
Create, inspect, and drop search indexes. Wait for indexing to complete after data changes. Indexes automatically track Redis keys matching a specified prefix.
release-notes
Draft curated release notes for a milestone release.
create-issue
Create a GitHub issue from the repo's templates, with the right type and labels.
soc2-review
Assess SOC 2 readiness against the Trust Services Criteria and produce a readiness dashboard.
overview
Unified cost dashboard combining state, plan, actual costs, projected costs, drift, and recommendations.