Borrowing it
Nothing to install: this file belongs to shreyaskarnik/voice-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shreyaskarnik/voice-mcp/main/.claude/skills/voice/SKILL.mdgit clone --depth 1 https://github.com/shreyaskarnik/voice-mcpWrote 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/shreyaskarnik/voice-mcp/voice)<a href="https://agentmods.dev/skills/shreyaskarnik/voice-mcp/voice"><img src="https://agentmods.dev/badge/skills/shreyaskarnik/voice-mcp/voice/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/shreyaskarnik/voice-mcp/voice"><img src="https://agentmods.dev/badge/skills/shreyaskarnik/voice-mcp/voice.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.00010 | $0.00500 |
| Opus 5.5 | $0.00004 | $0.00200 |
| Sonnet 5.5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
voice 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 2mo 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
Help the user pick a Kokoro TTS voice. If they provided a voice name as $ARGUMENTS, confirm that choice. Otherwise, show them the options below and ask which they'd like.
Available voices
English (American) — lang "a"
Female: af_alloy, af_aoede, af_bella, af_heart (default), af_jessica, af_kore, af_nicole, af_nova, af_river, af_sarah, af_sky Male: am_adam, am_echo, am_eric, am_fenrir, am_liam, am_michael, am_onyx, am_puck
English (British) — lang "b"
Female: bf_alice, bf_emma, bf_isabella, bf_lily Male: bm_daniel, bm_fable, bm_george, bm_lewis
Hindi — lang "h"
Female: hf_alpha, hf_beta Male: hm_omega, hm_psi
Spanish — lang "e"
Female: ef_dora Male: em_alex
French — lang "f"
Female: ff_siwis
Italian — lang "i"
Female: if_sara Male: im_nicola
Japanese — lang "j"
Female: jf_alpha, jf_gongitsune, jf_nezumi, jf_tebukuro Male: jm_kumo
Portuguese — lang "p"
Female: pf_dora Male: pm_alex
Mandarin Chinese — lang "z"
Female: zf_xiaobei, zf_xiaoni, zf_xiaoxiao, zf_xiaoyi Male: zm_yunjian, zm_yunxi, zm_yunxia, zm_yunyang
Voice naming convention
- First letter = language (a=American, b=British, h=Hindi, etc.)
- Second letter = gender (f=female, m=male)
- Rest = voice name
Once the user picks a voice, demonstrate it by calling speak() with a short sample sentence using that voice. Remind them they can change it anytime with /voice.
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.
- 2mo ago First seen · 53 lines · 10 tokens per session scan A aa431f26d0c6
voice is a skill published in the GitHub repository shreyaskarnik/voice-mcp (16 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 500 once invoked, about $0.0000 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.