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 validate-albumgit 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/validate-album)<a href="https://agentmods.dev/skills/bitwize-music-studio/claude-ai-music-skills/validate-album"><img src="https://agentmods.dev/badge/skills/bitwize-music-studio/claude-ai-music-skills/validate-album/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/validate-album"><img src="https://agentmods.dev/badge/skills/bitwize-music-studio/claude-ai-music-skills/validate-album.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.00033 | $0.02121 |
| Opus 5 | $0.00016 | $0.01060 |
| Sonnet 5 | $0.00007 | $0.00424 |
| Haiku 4.5 | $0.00003 | $0.00212 |
Grade A, and why
validate-album 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Album Validator Agent
Your Task
Input: $ARGUMENTS (album name, e.g., sample-album)
Validate that an album has all required files in the correct locations, catching path issues and missing content before they become problems.
Step 1: Load Config & Find Album
-
Call
get_config()— returns paths (content_root,audio_root,documents_root) andartist.name- If config missing, STOP and report:
[FAIL] Config file missing: ~/.bitwize-music/config.yaml Run /configure to set up the plugin.
- If config missing, STOP and report:
-
Call
find_album(album_name)— fuzzy match by name, slug, or partial- If not found, STOP and report (MCP returns available albums):
[FAIL] Album not found: {album-name}
- If not found, STOP and report (MCP returns available albums):
-
Optionally call
validate_album_structure(album_slug)— runs structural validation checks and returns{passed, failed, warnings, skipped, issues[], checks[]}. This MCP tool handles directory structure, required files, audio placement, and track content checks in one call.
Note: The MCP validate_album_structure tool performs many of the checks below automatically. You can use its results directly or run the manual checks for more detailed reporting.
Step 3: Run Validations
Initialize Counters
passed = 0failed = 0warnings = 0skipped = 0issues = [](list of fix commands)
Output Header
═══════════════════════════════════════════════════════════
ALBUM VALIDATION: {album-name}
═══════════════════════════════════════════════════════════
Validation Categories
CONFIG
CONFIG
──────
| Check | Pass | Fail |
|---|---|---|
| Config file exists | [PASS] Config file exists |
[FAIL] Config file missing |
| content_root defined | [PASS] content_root: {value} |
[FAIL] content_root not defined |
| audio_root defined | [PASS] audio_root: {value} |
[FAIL] audio_root not defined |
| artist defined | [PASS] artist: {value} |
[FAIL] artist.name not defined |
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 · 236 lines · 33 tokens per session scan A 44ef6144f11d
validate-album 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 33 tokens to every session and 2,121 once invoked, about $0.0002 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
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.
bun-test-lifecycle
Use for test lifecycle hooks: beforeAll, afterAll, beforeEach, afterEach, fixtures, preload.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
api-contract-testing
Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact. Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications.