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/masterleopold/book-capture/capturegit clone --depth 1 https://github.com/masterleopold/book-captureWhat 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.00020 | $0.02777 |
| Opus 5 | $0.00010 | $0.01388 |
| Sonnet 5 | $0.00004 | $0.00555 |
| Haiku 4.5 | $0.00002 | $0.00278 |
Grade A, and why
capture 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Book Capture Pipeline
Full pipeline: platform selection → screenshot capture → OCR text extraction → structured Markdown generation.
All AI-powered steps use Claude Code agents — no external API keys required.
Setup
Resolve paths:
PLUGIN_SCRIPTS=${CLAUDE_PLUGIN_ROOT}/scripts- Check for
.claude/book-capture.local.mdin the current working directory — if it exists, read YAML frontmatter forvault_root,captures_dir,entries_dir - If no settings file, auto-detect vault: look for
.obsidian/in current directory or parents VAULT_ROOT= detected vault root (or current directory)CAPTURES_BASE=<VAULT_ROOT>/<captures_dir>(default:Books/files/book-captures)ENTRIES_DIR=<VAULT_ROOT>/<entries_dir>(default:Books/entries)
Ensure dependencies are installed:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh" --check-only || bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh"
Step 1: Gather Information
Parse $ARGUMENTS for optional pre-filled values. Then ask the user for any missing information.
Platform selection (ask first, prominently):
Present these choices:
- Mac Kindle — Amazon Kindle desktop app (uses screencapture + Page Down navigation)
- Apple Books — Apple Books app (uses screencapture + arrow key navigation)
- Kindle Cloud Reader — Browser-based via Playwright (requires Amazon login)
- PDF — Image-based/scanned PDF files (uses Poppler pdftoppm)
Map to source values: kindle, books, cloud, pdf
Required:
- Source app: kindle / books / cloud / pdf (from platform selection above)
- Book ID: ASIN (for cloud/kindle), Book Title (for books), or identifier (for pdf)
- Book Title: Full title (for all sources)
- Author: Author name
- Category: One of the vault categories (AI, Marketing, Strategy, Finance, Management, etc.)
- Location: Where topic files should live (e.g.,
Knowledge/Marketing/BookTitle)
PDF-specific (required when source = pdf):
- PDF Path: Absolute path to the PDF file
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 · 285 lines · 20 tokens per session scan A ff29347d97d9
capture is a command published in the GitHub repository masterleopold/book-capture (10 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 2,777 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.