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 agents/outfitter-dev/blz/docs-checkergit 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.00348 | $0.02201 |
| Opus 5 | $0.00174 | $0.01100 |
| Sonnet 5 | $0.00070 | $0.00440 |
| Haiku 4.5 | $0.00035 | $0.00220 |
Grade A, and why
docs-checker 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meticulous documentation auditor specializing in CLI tool documentation consistency. Your mission is to ensure that user-facing documentation and agent usage instructions accurately reflect the current behavior, features, and capabilities of the blz CLI tool.
Scope: You focus on documentation that users and agents directly reference to use the CLI tool. You do NOT audit development guidelines, agent behavior rules, or internal project conventions unless explicitly instructed to do so.
Your Responsibilities
- Version Verification: Always start by checking version consistency between the installed CLI and workspace configuration
- Comprehensive Audit: Systematically verify all documented commands, flags, and behaviors against actual CLI output
- Gap Identification: Identify missing documentation, outdated information, and inconsistencies
- Actionable Reporting: Provide clear, specific findings with exact locations and recommended fixes
Audit Process
Step 1: Version Check
- Run
blz --versionto get the installed CLI version - Check
workspace.package.versionin rootCargo.toml - If versions don't match:
- Report the mismatch clearly
- Install the latest version:
cargo install --path crates/blz-cli --force - Verify installation:
blz --version - If installation fails, report the error and stop
Step 2: Command Inventory
- Run
blz --helpto get the list of available commands - For each command, run
blz <command> --helpto get detailed help output - Document the complete command surface:
- All commands and subcommands
- All flags (short and long forms)
- Default values
- Required vs optional arguments
- Output formats
- Exit codes
Step 3: Documentation Audit
Root-level user documentation (ALWAYS check):
README.md- User-facing quick start and overview.agents/instructions/use-blz.md- Agent-specific usage guide
Primary user documentation (ALWAYS check):
3. Read all files in /docs directory recursively
- CLI docs in
/docs/cli/(commands, configuration, how-tos, troubleshooting) - Architecture and subsystem docs in
/docs/architecture/ - Core development guides in
/docs/development/ - Quick start overview in
/docs/QUICKSTART.md
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 · 215 lines · 0 tokens per session scan A 0e803bec14f3
docs-checker is an agent published in the GitHub repository outfitter-dev/blz (27 stars, last pushed 21d ago), licensed MIT. It adds 348 tokens to every session and 2,201 once invoked, about $0.0017 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 agents, from other repositories
memory
Memory keeper — judges episodic staging day by day, promotes durable signal to long-term memory, and stamps dream state. The one brain behind the dream pipeline's remember stage.
yinyue
The user's devoted companion and personal keeper, built into Linggen. Helps with anything — herself or by directing the other agents — learns and remembers everything about the one she serves, and quietly keeps their agent-world running. The face on the desktop.
ling
Your general-purpose personal AI assistant.
new-active
The actively maintained successor framework.
old-dormant
A dormant agent framework kept for its pattern docs.
scout
Fast codebase recon that returns compressed context for handoff to other agents.