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/cli-testgit 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.00009 | $0.00483 |
| Opus 5 | $0.00005 | $0.00242 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
cli-test 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
blz CLI Comprehensive Test
Please perform a comprehensive test of the blz CLI tool with the following focus: $ARGUMENTS
Test Plan
1. Environment & Setup
- Verify
blzis properly installed and accessible - Check version information with
blz --version - Validate configuration directory structure
- Test help output for main command and subcommands
2. Core Functionality Tests
- Search Operations: Test various search patterns, filters, and output formats
- Source Management: Add, list, update, and remove sources
- Index Operations: Test indexing, updates, and cache management
- Configuration: Verify config file handling and environment variables
3. Edge Cases & Error Handling
- Invalid input validation
- Network connectivity issues
- Corrupted cache handling
- Permission errors
- Large dataset performance
4. Output Format Testing
- Text output formatting and readability
- JSON output structure and validity
- Error message clarity and helpfulness
- Search result relevance and ranking
5. Integration Testing
- Shell completion functionality
- Pipe/redirection compatibility
- Exit codes for scripting
- Configuration precedence (env vars vs config files)
Expected Deliverables
- Test Summary: Overall health status of the CLI
- Performance Metrics: Search latency, indexing speed, memory usage
- Issue Report: Any bugs, inconsistencies, or UX problems found
- Improvement Suggestions: Specific recommendations with priority levels
Special Instructions
- Use verbose output (
-vor--verbose) when available to capture detailed logs - Test with both small and large document sets if possible
- Verify that all documented features work as described in help text
- Pay attention to consistency across similar commands (flags, output format, etc.)
- Test error recovery and graceful degradation scenarios
If you identify any issues, please:
- Document exact reproduction steps
- Include relevant error messages or unexpected outputs
- Suggest specific fixes or improvements
- Prioritize issues by severity (critical, high, medium, low)
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 · 65 lines · 9 tokens per session scan A 904c7dd09e90
cli-test is a command published in the GitHub repository outfitter-dev/blz (27 stars, last pushed 20d ago), licensed MIT. It adds 9 tokens to every session and 483 once invoked, about $0.0000 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
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 강제).