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/billbuchanan-code/claude-code-power-setup/voice-skillnpx skills add billbuchanan-code/claude-code-power-setup --skill voice-skillgit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWhat 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.00011 | $0.01781 |
| Opus 5 | $0.00005 | $0.00890 |
| Sonnet 5 | $0.00002 | $0.00356 |
| Haiku 4.5 | $0.00001 | $0.00178 |
Grade A, and why
voice-skill 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write in [Your Name]'s Voice
Draft professional communications in your authentic voice. Adapts tone and structure based on the audience and medium.
This skill runs as a two-step process:
- Draft in BB's voice using the rules below and the style guide.
- Natural-language cleanup pass using the
natural-languageskill to strip AI tells and bloat, while preserving BB's voice exactly.
Process
-
Parse the request from $ARGUMENTS. Extract:
- The core message or intent (what needs to be communicated)
- The recipient(s) if mentioned
- The medium/channel if mentioned
-
If medium is not specified, ask. Present these options:
- Quick internal (Slack, text, brief email to team) -- 1-3 sentences, no greeting needed
- Internal directive (email to direct reports/team with context) -- name + comma, 2-5 sentences
- Professional external (client, prospect, partner email) -- warm but professional, clear next step
- Formal client (escalation, course correction, high-stakes) -- "Dear [Name]," structured sections
- Board/investor update (MD&A style) -- "Hello all," with Financial + Operational highlights
- Introduction (connecting two people) -- brief bios, why they should connect
- Other (describe it)
-
Read the style guide at
~/.claude/skills/bill-voice-skill/STYLE_GUIDE.mdto align with BB's voice patterns. -
STEP 1 - Draft the communication applying these rules:
Tone Calibration
| Medium | Greeting | Length | Sign-off | Typo-tolerance |
|---|---|---|---|---|
| Quick internal | None | 1-3 sentences | None or "BB" | High |
| Internal directive | Name + comma | 2-5 sentences | "Thanks" or "BB" | Medium |
| Professional external | "Hi [Name]," or "[Name]," | 3-8 sentences | "Best, BB" or "Thanks, Bill" | Low |
| Formal client | "Dear [Name]," | Multi-paragraph, sections | "Bill Buchanan" | None |
| Board/investor | "Hello all," | Structured bullets | "Thanks, BB" | None |
| Introduction | "[Name] and [Name]," | 2-3 paragraphs | "Best, BB" | None |
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 · 142 lines · 11 tokens per session scan A 256afe444e13
voice-skill is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,781 once invoked, about $0.0001 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.
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…