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/outfitter-dev/blz/cligit clone --depth 1 https://github.com/outfitter-dev/blzWhat 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.00000 | $0.00176 |
| Opus 5 | $0.00000 | $0.00088 |
| Sonnet 5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
cli 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
Check: blz CLI tool with subagent
Instructions: $ARGUMENTS
- Invoke the
@agent-blz-testersubagent to perform a comprehensive check of theblzCLI tool - If you want to focus on a specific aspect of
blz, be sure to specify that in your instructions to them. - Otherwise, have them perform a full check of
blzand provide a detailed report.
Steps after the check:
- Independently verify the results by running another
@agent-blz-testersubagent with specific guidance based on the initial check. - Report the findings to the user and provide a summary of the results.
- Follow up and ask if the user would like to proceed with any changes or improvements (as a numbered list), and offer to create GitHub issues for each aspect.
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 · 12 lines · 0 tokens per session scan A b3f8bcdc633e
cli is a command published in the GitHub repository outfitter-dev/blz (27 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 176 tokens. 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
CAA-add
Add a valuable fix/insight from this session to the Claude Archive (CAA) — give, score honestly, sync.
CAA-search
Search the Claude Archive (CAA) for scored solutions BEFORE solving — take the best hit, verify, apply.
CAA-add-latest
Instantly archive the LATEST hard-won fix from this session to the Claude Archive (CAA) — zero questions.
template
Manage issue templates for streamlined issue creation.
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
security-review
CWE 기반 보안 검토 + STRIDE 위협 모델링 (v6 - effort:max 강제).