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/metabuilder-labs/tokenjam/optimizegit clone --depth 1 https://github.com/Metabuilder-Labs/tokenjamWhat 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.00026 | $0.00170 |
| Opus 5 | $0.00013 | $0.00085 |
| Sonnet 5 | $0.00005 | $0.00034 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
optimize 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
tj optimize
!tj optimize --since "${ARGUMENTS:-30d}" 2>&1 || echo "tj is not installed. Run /onboard first, or install with npx tokenjam@latest / pipx install tokenjam."
Instructions
Summarize the optimize report above: the biggest recoverable-cost findings and the concrete fix each one suggests. If it reports no usage data yet, tell the user that's expected until TokenJam has ingested at least one session — run /onboard first if they haven't.
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 · 12 lines · 26 tokens per session scan A c32607037057
optimize is a command published in the GitHub repository Metabuilder-Labs/tokenjam (106 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 170 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 commands, from other repositories
tma1-peer
List recent sessions on this project by agent — peers (Codex, OpenClaw, Copilot CLI) or your own.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
review
Review proposed ADRs for lifecycle progression — accept implemented decisions, deprecate stale ones, archive trivial ones.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
push
Validate and push commits with lint, type, and build checks.
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.