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/testflightgit clone --depth 1 https://github.com/zhu-xiaowei/BatonWrote 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/commands/zhu-xiaowei/baton/testflight)<a href="https://agentmods.dev/commands/zhu-xiaowei/baton/testflight"><img src="https://agentmods.dev/badge/commands/zhu-xiaowei/baton/testflight.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.00020 | $0.00173 |
| Opus 5 | $0.00010 | $0.00086 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
testflight 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.
What it actually says
Ship a new TestFlight build. Run the release script — it auto-bumps
CFBundleVersion in src-tauri/gen/apple/project.yml, builds the release IPA,
validates it, and uploads to TestFlight via the App Store Connect API:
npm run release:ios
Run it in the background (build + upload takes several minutes) and monitor the output. When it finishes, report the result: the bumped CFBundleVersion, the IPA path, and whether validation + upload succeeded. If it fails, show the error.
Do not commit the project.yml version bump unless asked.
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 · 19 lines · 20 tokens per session scan A 807f21f45fe3
testflight is a command published in the GitHub repository zhu-xiaowei/Baton (9 stars, last pushed 9d ago), licensed MIT. It adds 20 tokens to every session and 173 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
ios-release
Prepare and execute an iOS release (patch/minor/major).
android-release
Prepare and execute an Android release (patch/minor/major).
upload
Archive, upload, and submit to external TestFlight (full loop with monitor).
hotfix
Ship a fix to production ahead of the next release — the two-PR pattern (main + release-branch twin). Runs only when the user invokes it explicitly.
release-notes
Draft curated release notes for a milestone release.
app-ship
Ship a release — runs security review, then release-manager, gating on QA sign-off and clean bug board.