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/kat3samsin/claude-code-plugins/setup-claudionpx skills add kat3samsin/claude-code-plugins --skill setup-claudiogit clone --depth 1 https://github.com/kat3samsin/claude-code-pluginsWhat 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.00018 | $0.00488 |
| Opus 5 | $0.00009 | $0.00244 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade B, and why
setup-claudio scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
5. Updates your `~/.claude/settings.json` What it actually says
Claudio: Talk to Claude Code
This skill sets up an enhanced Claude Code experience with voice output:
- Audio announcements for task completions, permission requests, and questions
- Smart permission announcements that tell you exactly what's being requested
- Four output styles: Full, Concise, Direct, and Conversational
- Personalized with your name
How to Run
Users can trigger this skill by:
- Slash command:
/setup-claudio - Ask Claude: "Set up Claudio" or "Make Claude talk"
What It Does
- Asks for your name
- Lets you choose your preferred style:
- Full: Detailed responses with comprehensive audio summaries
- Concise: Brief, efficient responses with short audio
- Direct: No fluff, no praise, just facts (recommended)
- Conversational: Natural, friendly dialogue with warm audio
- Installs output styles to
~/.claude/output-styles/ - Installs TTS hooks for:
- PermissionRequest: Announces what specific permission is needed
- Notification: Announces when Claude has a question
- Stop: Announces when task is complete
- Updates your
~/.claude/settings.json - Confirms setup with audio feedback
After Setup
Switch styles anytime by editing ~/.claude/settings.json:
{
"outputStyle": "TTS Conversational"
}
Options: "TTS Full", "TTS Concise", "TTS Direct", "TTS Conversational"
Requirements
- macOS (uses
saycommand for TTS) jqfor settings configuration (brew install jq)- Optional: Premium voices (System Settings > Accessibility > Spoken Content > System Voice > Manage Voices)
Voice Customization
List available voices:
say -v '?'
Recommended voices:
Zoe (Premium)- Australian female (default)Samantha- American femaleDaniel- British male
Premium voices sound more natural but must be downloaded separately.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 69 lines · 18 tokens per session scan B 1d96545a8389
setup-claudio is a skill published in the GitHub repository kat3samsin/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 488 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…