project-tts-responder

project-tts-responder is a skill for Claude Code, Codex from Engr-FaizanAli/text-to-speech-mcp. It costs 79 tokens per session (1,241 once invoked), scanned A, original, MIT.

A voice-output skill that reads agent responses, files, or selected text aloud using your computer’s built-in speech system.

In plain words
What is it for?
Use it to listen to responses as they are produced, hear a complete response at the end, or request audio for a particular file or text block.
Why use it?
It helps when reading the screen is inconvenient or when you want to hear a spoken walkthrough of the agent’s work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to listen to responses as they are produced, hear a complete response at the end, or request audio for a particular file or text block.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/engr-faizanali/text-to-speech-mcp/project-tts-responder
Install

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.

Any agent
npx skills add Engr-FaizanAli/text-to-speech-mcp --skill project-tts-responder
Clone the repo
git clone --depth 1 https://github.com/Engr-FaizanAli/text-to-speech-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for project-tts-responder

README.md
[![agentmods](https://agentmods.dev/badge/skills/engr-faizanali/text-to-speech-mcp/project-tts-responder/github.svg)](https://agentmods.dev/skills/engr-faizanali/text-to-speech-mcp/project-tts-responder)
Your own site
<a href="https://agentmods.dev/skills/engr-faizanali/text-to-speech-mcp/project-tts-responder"><img src="https://agentmods.dev/badge/skills/engr-faizanali/text-to-speech-mcp/project-tts-responder/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.

agentmods 80×15 button for project-tts-responder

Your own site · 80×15
<a href="https://agentmods.dev/skills/engr-faizanali/text-to-speech-mcp/project-tts-responder"><img src="https://agentmods.dev/badge/skills/engr-faizanali/text-to-speech-mcp/project-tts-responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,241 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.01241
Opus 5 $0.00039 $0.00620
Sonnet 5 $0.00016 $0.00248
Haiku 4.5 $0.00008 $0.00124

Measured 12d ago against content hash 4e01a56e2b59, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

project-tts-responder 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 12d 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.

skills/project-tts-responder/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TTS Responder

This skill drives the speak_text tool exposed by the Text to Speech MCP server: a local, no-API-key server that gives any MCP client a voice using the speech synthesizer built into the host operating system.

Choosing a mode

Use the mode the user asks for. If they do not say, default to Batch.

A host project can make one mode the standing default by saying so in its own agent instructions, for example "narrate every response in Batch mode unless the user opts out". Without that, this skill applies only when the user asks for audio.

1. Batch — one playback at the end of the turn

Display every intermediate update and the final response normally, calling nothing yet. After the final response has been sent and is visible, make a single speak_text call containing every visible intermediate update in chronological order followed by the exact final response, separated by blank lines. That is the only speak_text call for the turn.

Send the final response first, so it is on screen before playback starts. Nothing further should follow the playback call unless it fails.

2. Streaming — narrate as you go

For each visible intermediate update: display the text, then call speak_text with that exact text, and wait for playback to finish before producing the next update. Do the same for the final response last.

Streaming suits demos and walkthroughs. It costs one call per update, so it is the wrong default for ordinary work.

3. Read specific content on request

When asked to read, play, or speak a named file or block of text, call speak_text once with that content verbatim. Add no commentary inside the call. If the content exceeds the tool's input limit, say which part you are reading and read a clearly stated excerpt.

What to read aloud

Only user-visible assistant content:

  • Progress updates already sent during this turn.
  • The final answer, exactly as sent.
  • Command results only when they already appear in those visible messages.
  • File paths and report names when they help.
  • Any interactive question or interrupt, including every option offered.

Read the full file on GitHub · 128 lines

Changes

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.

  1. 12d ago First seen · 128 lines · 79 tokens per session scan A 4e01a56e2b59

Subscribe to this mod's changes

project-tts-responder is a skill published in the GitHub repository Engr-FaizanAli/text-to-speech-mcp (1 stars, last pushed 23d ago), licensed MIT. It adds 79 tokens to every session and 1,241 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

agent-desktop

Reliable computer use via native OS accessibility trees. Use when an AI agent needs to see and operate desktop applications (click buttons, fill forms, navigate menus, read UI state, toggle checkboxes, scroll, drag, type text, take screenshots, manage windows, use clipboard, manage notifications). Covers 59 command…

lahfir/agent-desktop · 210 tokens

harness-design-fuzzing

Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2 multi-component / T3 full build), systematic input exploration, the two-coverage distinction (fuzzer-feedback vs audit)…

provos/ironcurtain · 147 tokens

memory-safety-c-cpp

Reference vocabulary for memory-safety vulnerabilities in native C/C++ code — bug-class taxonomy, common arithmetic patterns that lead to corruption, dispatch-family discipline, type-confusion idioms, use-after-free patterns, and exploitability factors. Read when analyzing, hypothesizing, designing harnesses for, or…

provos/ironcurtain · 113 tokens

email-formatting

Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.

provos/ironcurtain · 53 tokens

json-schema-emails

Canonical shape of the .workflow/emails/emails.json file passed between the fetch and summarize states — required fields (sender, recipient, subject, date, body), types, and field semantics. Read this whenever you write or read emails.json so producer and consumer agree on the shape.

provos/ironcurtain · 62 tokens

kmsg

Use KMSG to read, watch, and send KakaoTalk messages safely from a coding agent. Use whenever the user mentions KakaoTalk or kmsg and wants chat discovery, recent messages, monitoring, text or image delivery, setup checks, or CLI troubleshooting. Do not use for other messaging platforms or private KakaoTalk protocol…

channprj/kmsg · 71 tokens