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 skills/kenrogers/elevenlabs-claude-plugin/plugin-helpnpx skills add kenrogers/elevenlabs-claude-plugin --skill plugin-helpgit clone --depth 1 https://github.com/kenrogers/elevenlabs-claude-pluginWrote 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/kenrogers/elevenlabs-claude-plugin/plugin-help)<a href="https://agentmods.dev/skills/kenrogers/elevenlabs-claude-plugin/plugin-help"><img src="https://agentmods.dev/badge/skills/kenrogers/elevenlabs-claude-plugin/plugin-help.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.00017 | $0.00610 |
| Opus 5 | $0.00009 | $0.00305 |
| Sonnet 5 | $0.00003 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
plugin-help 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Run the check-elevenlabs-init hook using the Bash tool with
nodecommand to see if ElevenLabs knowledge has been initialized. - Let the user know if the ElevenLabs plugin has been initialized or not.
- If the ElevenLabs plugin has not been initialized, let the user know they should take care of this first by running
/elevenlabs:init:
⚠️
The ElevenLabs plugin hasn't been initialized for the current project.
Run `/elevenlabs:init` to get the plugin's full functionality.
- Display the following section to the user exactly as it is below.
--- --- 🔊 🔊 🔊 --- ---
🔊 ElevenLabs Plugin for Claude Code
What This Plugin Does
This plugin makes Claude Code work better with ElevenLabs by:
- Using the right documentation — Automatically fetches the latest ElevenLabs docs so Claude always has current API patterns
- Avoiding common mistakes — Provides ElevenLabs-specific best practices, anti-pattern detection, and SDK guidance so Claude doesn't hallucinate or use outdated approaches
- Guided workflows — Skills and commands to scaffold voice agents, add text-to-speech, test agents, and review code quality
- Proactive assistance — Detects when you're working with ElevenLabs and suggests relevant skills automatically
Quick Reference
| Command | Description |
|---|---|
/elevenlabs:init |
Set up ElevenLabs knowledge for your project |
/elevenlabs:expert-advice |
Review your ElevenLabs code against best practices |
/elevenlabs:update-docs |
Refresh the documentation index |
/elevenlabs:help |
Show this help page |
| Skill | Description |
|---|---|
/elevenlabs:build-agent |
Scaffold a conversational voice agent |
/elevenlabs:add-tts |
Add text-to-speech to your app |
/elevenlabs:test-agent |
Test voice agents with simulated conversations |
💬 Example Prompts
- "Build me a voice agent that can book appointments"
- "Add text-to-speech to my Next.js app"
- "Test my voice agent with a sample conversation"
- "Review my ElevenLabs code for best practices"
- "Update my ElevenLabs docs to the latest version"
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 · 59 lines · 17 tokens per session scan A dc2a2172fbbd
plugin-help is a skill published in the GitHub repository kenrogers/elevenlabs-claude-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 610 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…