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.
/plugin marketplace add richawo/yaps-codex-pluginnpx agentmods add plugins/richawo/yaps-codex-plugin/yaps-text-to-speechgit clone --depth 1 https://github.com/richawo/yaps-codex-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/plugins/richawo/yaps-codex-plugin/yaps-text-to-speech)<a href="https://agentmods.dev/plugins/richawo/yaps-codex-plugin/yaps-text-to-speech"><img src="https://agentmods.dev/badge/plugins/richawo/yaps-codex-plugin/yaps-text-to-speech.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
yaps-text-to-speech 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 3d 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
{
"name": "yaps-text-to-speech",
"displayName": "Yaps Text to Speech",
"version": "0.1.12",
"description": "Turn text into spoken audio, narration, or a voice-over with Yaps.",
"author": {
"name": "Yaps AI",
"email": "[email protected]",
"url": "https://www.yaps.ai"
},
"homepage": "https://www.yaps.ai",
"repository": "https://github.com/richawo/yaps-plugins",
"license": "MIT",
"keywords": [
"text-to-speech",
"tts",
"voice-over",
"audio"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 127 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 21 lines scan A d1b18cfad60b
yaps-text-to-speech is a plugin published in the GitHub repository richawo/yaps-codex-plugin (2 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
logo-designer-skill
Design and iterate on logos using SVG with Claude Code.
mojiemoji-github
GitHub Markdown 向け mojiemoji 画像スタンプを埋め込むスキル + サブエージェント + 6 必須パラメータゲートフック.
grokodex
Use local Grok from Claude Code: delegate tasks, Imagine images, and search X via MCP.
claude-city-plugin
Visualize your current project as a 3D city in the browser. Files become buildings, folders become districts, bugs become fires. Launch with /city.
remotion
Remotion video creation skills — best practices, animations, audio, captions, 3D, and more for building programmatic videos with React.
pollinations-claude-code
Pollinations AI for Claude Code CLI. Generate images, text, audio, video, and transcribe speech. BYOP OAuth login — users fund their own usage with pollen credits.