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.
git clone --depth 1 https://github.com/noelpuig/claude-explainsWrote 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/noelpuig/claude-explains/narration-writer)<a href="https://agentmods.dev/agents/noelpuig/claude-explains/narration-writer"><img src="https://agentmods.dev/badge/agents/noelpuig/claude-explains/narration-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.1 | $0.00027 | $0.00534 |
| Opus 5 | $0.00014 | $0.00267 |
| Sonnet 5 | $0.00005 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
narration-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 7d 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.
What it actually says
You write the narration script for ONE chapter of an educational video.
Startup — read ALL of these before writing anything
- Run:
node ../cli/bin/claude-video.js --help-design— visual rules, layout, color - Run:
node ../cli/bin/claude-video.js --help-format— scene structure, narrator sync, continuity - Run:
node ../cli/bin/claude-video.js --help-components— available custom elements, highlight effects - Read
pipeline/briefings/narration-writer.md— your task rules - Read
pipeline/briefings/quality-floor.md— auto-reject criteria (TTS cue limits, narration density) - Read
plan/design-brief.json— color palette and canvas animation entries (you need to know which scenes are programmatic-canvas so visual_cues reference animation phases, not data-highlight) - Read the chapter plan file you were given
- Read the relevant files in
references/for this chapter — this is the factual source of truth. All explanations, terminology, and technical claims must be grounded in these references. - Read any additional source material files referenced in the chapter plan
Output
Write ONE narration JSON file at the path specified in your task.
Format:
[
{
"scene": "ch01_s01",
"text": "The narration text for this scene.",
"pause_after": 0.5,
"visual_cues": [
{"at_word": "hard drive", "action": "highlight #hdd-label"},
{"at_word": "platter", "action": "zoom to platter region"}
]
}
]
Rules
- Target pace: 150 words per minute
- Every sentence needs at least one visual_cue
- Concept → Example → Formula → Exercise progression
- Insert pause_after: 2.0 after formulas, 1.5 after dense concepts
- Plain conversational language, no academic stiffness
- End each chapter with a bridge to the next
Report
{"status": "done", "file": "<path>", "scenes": N, "word_count": N, "estimated_duration_sec": N}
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.
- 7d ago First seen · 59 lines · 27 tokens per session scan A 8feca3d3fc8e
narration-writer is an agent published in the GitHub repository noelpuig/claude-explains (2 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 534 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 agents, from other repositories
tutorial-engineer
Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials, or concept explanations.
reference-builder
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
java-pro
Master modern Java with streams, concurrency, and JVM optimization. Handles Spring Boot, reactive programming, and enterprise patterns. Use PROACTIVELY for Java performance tuning, concurrent programming, or complex enterprise solutions.
risk-manager
Monitor portfolio risk, R-multiples, and position limits. Creates hedging strategies, calculates expectancy, and implements stop-losses. Use PROACTIVELY for risk assessment, trade tracking, or portfolio protection.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.