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/dev-setupgit 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.00007 | $0.00481 |
| Opus 5 | $0.00003 | $0.00241 |
| Sonnet 5 | $0.00001 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
dev-setup 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
blz Development Environment Setup
Please help set up the development environment for the blz project. Mode: $ARGUMENTS
Setup Tasks
1. Environment Validation
- Check Rust toolchain (verify rust-toolchain.toml requirements)
- Validate required system dependencies
- Confirm git hooks and pre-commit setup
- Check Node.js for documentation tooling
2. Build & Dependencies
- Run
cargo build --releaseto ensure clean compilation - Execute
cargo testto verify all tests pass - Check
cargo clippyfor linting issues - Run formatting with
cargo fmt --check
3. Development Tools
- Install local blz binary with
cargo install --path crates/blz-cli - Set up shell completions for enhanced development experience
- Configure IDE/editor settings if applicable
- Validate benchmark environment with
cargo bench --dry-run
4. Project Validation
- Run the smoke test script:
./scripts/agent-check.sh - Verify documentation builds correctly
- Test CLI with sample sources from registry
- Check that all scripts in
./scripts/are executable and functional
5. Development Workflow
- Explain the git workflow and branch naming conventions
- Show how to run specific test suites efficiently
- Demonstrate performance profiling setup
- Guide through the release process basics
Setup Mode Instructions
Quick Mode ($ARGUMENTS contains "quick"):
- Focus on essential build and test validation
- Skip optional tooling and advanced setup
- Provide minimal viable development environment
Full Mode (default or $ARGUMENTS contains "full"):
- Complete development environment setup
- Include all optional tools and configurations
- Provide comprehensive workflow guidance
- Set up performance monitoring and profiling tools
Expected Outcome
After completion, the developer should have:
- A fully functional build environment
- All tests passing locally
- CLI tool installed and accessible
- Understanding of the development workflow
- Access to debugging and profiling tools
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 · 69 lines · 7 tokens per session scan A f8b462e6f51f
dev-setup is a command published in the GitHub repository outfitter-dev/blz (27 stars, last pushed 20d ago), licensed MIT. It adds 7 tokens to every session and 481 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 강제).