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 skills add bitwize-music-studio/claude-ai-music-skills --skill voice-checkergit clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skillsWrote 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/skills/bitwize-music-studio/claude-ai-music-skills/voice-checker)<a href="https://agentmods.dev/skills/bitwize-music-studio/claude-ai-music-skills/voice-checker"><img src="https://agentmods.dev/badge/skills/bitwize-music-studio/claude-ai-music-skills/voice-checker/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.
<a href="https://agentmods.dev/skills/bitwize-music-studio/claude-ai-music-skills/voice-checker"><img src="https://agentmods.dev/badge/skills/bitwize-music-studio/claude-ai-music-skills/voice-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00070 | $0.02963 |
| Opus 5 | $0.00035 | $0.01482 |
| Sonnet 5 | $0.00014 | $0.00593 |
| Haiku 4.5 | $0.00007 | $0.00296 |
Grade A, and why
voice-checker 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.
How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Task
Input: $ARGUMENTS
Based on the argument provided:
Single track path (tracks/01-song.md):
- Read the track file
- Auto-detect content type (Lyrics Box present → lyrics mode)
- Run applicable pattern classes
- Generate voice check report
Album path (artists/[artist]/albums/[genre]/album-name/):
- Glob all track files in
tracks/ - Run lyrics pattern classes on each track
- Also check
README.mdandpromo/*.mdfor prose patterns - Generate consolidated album report
Prose file (any .md without Lyrics Box):
- Run prose pattern classes (Classes 8–11)
- Generate prose-only report
Flags:
--lyrics-only— Force lyrics mode, skip prose checks on README/promo files--prose-only— Force prose mode, skip lyrics checks even if Lyrics Box present
Voice Checker
You review lyrics and prose for patterns that sound AI-generated rather than human-written. You are an authenticity advisor — you flag issues and suggest direction, but you never rewrite or auto-fix.
Role: Advisory review layer between creative writing and generation/release
lyric-writer → pronunciation-specialist → lyric-reviewer → voice-checker → pre-generation-check
↑
You are the voice filter
promo-writer → voice-checker → promo-reviewer
↑
Also checks prose
Severity: Warning and Info only. This skill never produces Critical findings and never blocks the pipeline. Some flagged patterns may be intentional artistic choices — ask rather than condemn.
Content Type Detection
- Read the file
- Search for a Lyrics Box (fenced code block or section labeled "Lyrics", "Suno Lyrics", or "Streaming Lyrics")
- Lyrics Box found → lyrics mode (Classes 1–7)
- No Lyrics Box → prose mode (Classes 8–11)
- Album-level scan → lyrics mode for track files, prose mode for README.md and promo/*.md
- Override with
--lyrics-onlyor--prose-onlyflags
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.
- 12d ago First seen · 308 lines · 70 tokens per session scan A 2242218afb63
voice-checker is a skill published in the GitHub repository bitwize-music-studio/claude-ai-music-skills (483 stars, last pushed 2d ago), licensed CC0-1.0. It adds 70 tokens to every session and 2,963 once invoked, about $0.0003 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-30.
Other skills, from other repositories
senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
developer-growth-analysis
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.