Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add shreyas-s-rao/claude-code-narrator/plugin install narratorWrote 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/skills/shreyas-s-rao/claude-code-narrator/speed)<a href="https://agentmods.dev/skills/shreyas-s-rao/claude-code-narrator/speed"><img src="https://agentmods.dev/badge/skills/shreyas-s-rao/claude-code-narrator/speed/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/shreyas-s-rao/claude-code-narrator/speed"><img src="https://agentmods.dev/badge/skills/shreyas-s-rao/claude-code-narrator/speed.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.00608 |
| Opus 5 | $0.00028 | $0.00304 |
| Sonnet 5 | $0.00011 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
speed 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 10d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Narrator Speech Speed
Step 1: Determine Scope
Check if the user said "locally", "for this directory", "for this project", or similar. If so, changes apply to the local config file in the current working directory.
- Global (default):
~/.claude-code-narrator/config - Local:
<cwd>/.claude-code-narrator/config
Step 2: Get the Speed Value
If the user specifies a speed value (e.g., "set speed to 1.5"), use that value. Valid range is 0.5 to 2.0. Default is 1.1.
If the user says "faster" or "speed up", read the current speed and increase it by 0.2 (capped at 2.0). If the user says "slower" or "slow down", read the current speed and decrease it by 0.2 (minimum 0.5).
If the value is outside the valid range, tell the user the valid range and ask them to pick a value.
If no specific value or direction is given, read the current speed from the appropriate config file (local if it exists and has a speed key, otherwise global) and show it to the user. Then ask what speed they would like using AskUserQuestion with these options:
- 0.7 — Slow, deliberate
- 1.0 — Natural pace
- 1.1 — Default
- 1.5 — Brisk
The user can also type a custom value.
Step 3: Set the Speed
Global mode (default):
Read ~/.claude-code-narrator/config and use the Edit tool to change the speed= line to the new value.
Local mode:
Read <cwd>/.claude-code-narrator/config. If the file exists, use the Edit tool to change or add the speed= line. If the file does not exist, create the <cwd>/.claude-code-narrator/ directory if needed, then create the config file with the Write tool containing just speed=<value>.
IMPORTANT: Do NOT use sed to edit state files — use the Read and Edit tools instead.
Step 4: Confirm
Tell the user the new speed value, then speak a test sentence so they can hear the difference:
echo "This is how I sound at the new speed." | bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/speak.sh" --force
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.
- 10d ago First seen · 52 lines · 57 tokens per session scan A ac05d3923bde
speed is a skill published in the GitHub repository shreyas-s-rao/claude-code-narrator (26 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 608 once invoked, about $0.0003 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 skills, from other repositories
sitrep-panel
Keep a live local HTML report updated as you work on a task — a status board, a running "what's happening now" narrative, screenshots, and a newest-first log — served on localhost so the user can watch progress in a browser tab instead of reading the transcript. Use when the user invokes /sitrep-panel, asks for a…
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
git-workflow
Use when starting feature work that needs a branch, creating worktrees for isolation, making atomic commits during development, or completing a development branch via merge, PR, preserve, or discard. Also use when the user says "set up worktree", "create PR", "finish this branch", "start feature", or when you need an…
parallel-dispatch
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Also use when multiple test files fail with different root causes, multiple subsystems are broken independently, or you want agents to work concurrently on separate problem domains. If tasks touch different…
sitrep
Situational awareness — where am I, what was I doing, what's next. Context recovery after compression, confusion, or mid-session reorientation.