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/vldesigns/casebook/exportgit clone --depth 1 https://github.com/vldesigns/casebookWhat 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.00015 | $0.00249 |
| Opus 5 | $0.00008 | $0.00125 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
export 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
Export .casebook/case-study.md as a dated, shareable snapshot.
Read-only beyond writing the export files — never edit the case study from this command.
Step 1: Preflight.
- If
.casebook/case-study.mddoesn't exist, suggest running/casebook:initand stop.
Step 2: Export.
- Run: "$CLAUDE_PLUGIN_ROOT/scripts/tracker" export --pdf --open
Step 3: Report exactly what was produced.
- If a PDF was written: report both paths — the dated PDF and the dated HTML it was printed from.
- If no browser was found: report the HTML path only, and note the print-to-PDF fallback — open the HTML and print to PDF from the browser's own print dialog.
- Mention that each export is dated — "the case study as of today." A re-export next month is a different snapshot, not an overwrite; over time they build a progression.
Output as a short, plain confirmation of what was written and where, not a status report.
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 · 29 lines · 15 tokens per session scan A e41f8abc0c0a
export is a command published in the GitHub repository vldesigns/casebook (1 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 249 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-31.
Other commands, from other repositories
wisp-dashboard
Open the WISP dashboard in your browser.
flux-add
Quickly add a task to Flux from a brief description.
card
Open one self-contained OverClick card.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
build-docs
Build and serve the docs site locally with Jekyll.
specmanager-board
Open the SpecManager kanban board in your default browser.