Speak through a buffered, interruptible agent voice service

Speak through a buffered, interruptible agent voice service is a skill for Claude Code, Codex from howdeploy/deploychan_mcp. It costs 51 tokens per session (869 once invoked), scanned A, original, MIT.

A workflow for delivering requested agent replies through a text-to-speech service, which turns written text into spoken audio. It manages the existing voice service, audio device, playback, early phrase delivery and confirmed cancellation.

In plain words
What is it for?
Use it when an agent must speak a response, maintain a warm speech connection, play a complete recording and cancel playback through the identified service and device.
Why use it?
It prevents duplicate speech submissions, accidental narration of unrelated replies and playback that cannot be stopped reliably. It also keeps the spoken answer short and suitable for listening rather than reading logs or markup.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when an agent must speak a response, maintain a warm speech connection, play a complete recording and cancel playback through the identified service and device.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/howdeploy/deploychan_mcp/buffered-agent-voice
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 howdeploy/deploychan_mcp --skill buffered-agent-voice
Clone the repo
git clone --depth 1 https://github.com/howdeploy/deploychan_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 Speak through a buffered, interruptible agent voice service

README.md
[![agentmods](https://agentmods.dev/badge/skills/howdeploy/deploychan_mcp/buffered-agent-voice/github.svg)](https://agentmods.dev/skills/howdeploy/deploychan_mcp/buffered-agent-voice)
Your own site
<a href="https://agentmods.dev/skills/howdeploy/deploychan_mcp/buffered-agent-voice"><img src="https://agentmods.dev/badge/skills/howdeploy/deploychan_mcp/buffered-agent-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.

agentmods 80×15 button for Speak through a buffered, interruptible agent voice service

Your own site · 80×15
<a href="https://agentmods.dev/skills/howdeploy/deploychan_mcp/buffered-agent-voice"><img src="https://agentmods.dev/badge/skills/howdeploy/deploychan_mcp/buffered-agent-voice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 869 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.00051 $0.00869
Opus 5.5 $0.00020 $0.00348
Sonnet 5.5 $0.00010 $0.00174
Haiku 4.5 $0.00005 $0.00087

Measured today against content hash fa8e8d2cd04e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Speak through a buffered, interruptible agent voice service 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 today.

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.

content/skills/buffered-agent-voice/SKILL.md · 75 lines

How it starts

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

Buffered agent speech

Identify the user's actual voice service, output device, selected voice/model, proxy, current volume, cancellation path and conversation binding. This skill contains no personal profile, API key, device address or ready-made session attachment. For the implementation details retrieve buffered-speech-and-cancellation through Deploychan MCP, and voice-pipeline-latency-and-lessons for measurement/negative evidence.

Deliver an explicitly requested answer

  • Reuse the existing private service interface and warm connection. Do not create a new script/session or restart a daemon just to speak one reply.
  • Prepare a direct, natural first sentence and a short complete answer. Avoid Markdown, paths, URLs and tool logs in speech. A short conversation may be a few sentences; a work summary states the result and a useful next step. Do not pad the first sentence with filler to reach a provider text threshold.
  • Use one bounded request or single-use permission for the identified conversation, then submit the final speech text promptly. Do not mix two submission methods for the same answer or enable automatic narration for subsequent unrelated tasks.
  • Preserve current speaker volume and mute. Do not change computer volume or the chosen voice/model/proxy unless that is part of the user's task.
  • Treat queue acceptance as acceptance only. State verified playback/listening evidence when available; do not retry an ambiguous paid request automatically.

Maintain the transport without regressing reliability

Keep input text incremental. Force generation after the first prepared phrase, continue text on the same provider socket and flush the remainder only if nonempty. For a ready text request use one input segment/flush. Handle intermediate audio-final boundaries without discarding later text or returning the connection to another job early. Keep frame alignment, length limits, timeouts and cleanup through cancellation.

Prepare and validate the full private WAV before starting the native device player. This deliberately avoids the proxy-sensitive live playback that failed in the case study. Do not remove buffering merely to improve the first-PCM number. Check the actual TTD protocol instead of copying fields from a different TTS WebSocket API.

Read the full file on GitHub · 75 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. today First seen · 75 lines · 51 tokens per session scan A fa8e8d2cd04e

Subscribe to this mod's changes

Speak through a buffered, interruptible agent voice service is a skill published in the GitHub repository howdeploy/deploychan_mcp (19 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 869 once invoked, about $0.0002 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-10-28.