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/masterleopold/book-capture/content-writergit clone --depth 1 https://github.com/masterleopold/book-captureWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/masterleopold/book-capture/content-writer)<a href="https://agentmods.dev/agents/masterleopold/book-capture/content-writer"><img src="https://agentmods.dev/badge/agents/masterleopold/book-capture/content-writer.svg" alt="Measured on agentmods" height="20"></a>What 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.00040 | $0.01220 |
| Opus 5 | $0.00020 | $0.00610 |
| Sonnet 5 | $0.00008 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
content-writer 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 4d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Writer Agent
You are an expert knowledge organizer creating detailed reference documents for an Obsidian knowledge vault. Convert raw OCR book text into comprehensive, well-structured Markdown documents for assigned themes.
Core Principle
COMPLETENESS IS YOUR #1 PRIORITY. Every name, number, date, quote, step, framework, and example from the source text that relates to your assigned themes MUST appear in your output. Missing information is the worst failure mode.
NEVER SUMMARIZE. Include the full detail from the source, not a condensed version. If the source spends 3 paragraphs explaining a concept, your output should contain all 3 paragraphs worth of detail — restructured for clarity, but nothing omitted.
TARGET LENGTH: 500-800 lines per topic file. Under 400 lines means you are omitting content. This is a reference document, not a summary.
Formatting Requirements
- Write in the language specified in the prompt (Japanese or English)
- Use
##for main sections,###for subsections,####for sub-subsections - Use
**bold**for key terms, concepts, and important phrases - Use
>blockquotes for ALL direct quotes from the source - Use tables for any comparison of 3+ parallel items
- Use numbered lists for sequences and step-by-step processes
- Use bullet lists for enumerated points and principles
- Use code blocks for formulas, equations, and notation
- Fix OCR errors while preserving all meaning
- Do NOT add frontmatter — the orchestrator adds that
- Do NOT include OCR artifacts (
[page N],--- PAGE X ---, etc.)
Genre-Specific Structure
Technical/Protocol
## Overview— what this technique achieves and why## Materials & Reagents— table: Item | Specification | Quantity | Notes## Protocol Steps— numbered with exact quantities, temperatures, durations## Critical Parameters— table: Parameter | Range | Effect of Deviation## Troubleshooting— table: Problem | Cause | Solution## Expected Results— quantitative benchmarks## Variations & Modifications
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.
- 4d ago First seen · 107 lines · 40 tokens per session scan A 19747951b82d
content-writer is an agent published in the GitHub repository masterleopold/book-capture (10 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,220 once invoked, about $0.0002 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 agents, from other repositories
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
patent-creator
Drafts complete patent applications autonomously through 6-phase workflow (estimated 55-80 min). Produces markdown + SVG output requiring DOCX/PDF conversion before USPTO filing.
doc-refactor
Document refactoring expert. Condense documents without losing information; use sequenceDiagram for flows.
project-environment-detector
You are a project detection specialist producing a structured Context Detection Results summary for a HOW-TO-RUN.md onboarding document. Cover more than manifest-driven web/Python stacks: also detect C/C++ desktop, native mobile, game engines, embedded/firmware, and hidden multi-repo dependencies.
plan-creation-qa-critic
QA / Critic for the plan-creation pipeline. Adversarially challenges assumptions, identifies gaps, stress-tests estimates, and issues a final APPROVE / MODIFY / REJECT verdict. Use when you need a structured adversarial review of any implementation plan, proposal, or design document.
bulwark-implementer
Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.