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 rekordcloud/sonovault-mcp --skill skillgit clone --depth 1 https://github.com/rekordcloud/sonovault-mcpWrote 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/rekordcloud/sonovault-mcp/skill)<a href="https://agentmods.dev/skills/rekordcloud/sonovault-mcp/skill"><img src="https://agentmods.dev/badge/skills/rekordcloud/sonovault-mcp/skill/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/rekordcloud/sonovault-mcp/skill"><img src="https://agentmods.dev/badge/skills/rekordcloud/sonovault-mcp/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00100 | $0.01802 |
| Opus 5.5 | $0.00040 | $0.00721 |
| Sonnet 5.5 | $0.00020 | $0.00360 |
| Haiku 4.5 | $0.00010 | $0.00180 |
Grade A, and why
sonovault-music-metadata scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.sonovault.now/v1/tracks/search?artist=Daft+Punk&title=One+More+Time&limit=5" \ How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You query the SonoVault music metadata API: 93M+ tracks with ISRC, ISWC, genre, BPM, musical key, label, release dates, and cross-platform IDs.
Setup
- Base URL:
https://api.sonovault.now - Every request needs the API key header:
x-api-key: $SONOVAULT_API_KEY - Read the key from the
SONOVAULT_API_KEYenvironment variable. If it is missing, tell the user to get a free key at https://sonovault.now (1,000 requests/month, no credit card) and export it. - All responses are JSON, snake_case. List endpoints paginate with
next_cursor; pass it back ascursor.next_cursoris null on the last page.
If the environment has the SonoVault MCP server available (sonovault-mcp), prefer its tools over raw HTTP.
When to activate
- The user asks about a track, artist, label, or release: genre, label, release date, ISRC.
- The user has an ISRC or ISWC code, or wants one.
- The user wants a track's ID or link on another platform.
- The user has a list to enrich: a radio play log, a DJ library export, a CSV of ISRCs.
Core recipes
Find a track (and its ISRC)
Search requires BOTH artist and title. There is no free-text q parameter.
curl -s "https://api.sonovault.now/v1/tracks/search?artist=Daft+Punk&title=One+More+Time&limit=5" \
-H "x-api-key: $SONOVAULT_API_KEY"
Each result carries id, title, artists, isrc, duration, bpm, key_alphanumeric, key_musical, key_open, keys, genre, subgenre, and releases (album title, label, release_date). The search is fuzzy: it survives (Original Mix) suffixes, feat. credits, and messy casing, so pass raw playout strings as-is.
Tempo and key
Every track (search, ISRC lookup, by id, browse, resolve, release tracklists) carries:
bpm: full tempo, up to 2 decimals (174, not 87).key_alphanumeric: 1 to 12 plusA(minor) orB(major), e.g.10B.key_musical: e.g.D,Am,F#m,Ebm.key_open: Open Key notation, lowercase, e.g.3d,1m.keys: every key held, one{key_alphanumeric, key_musical, key_open, source}per source.
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.
- yesterday Changed · +12 lines · +5 tokens per session 55cbc9605100
- 25d ago Changed 6d1ed980681b
- 1mo ago First seen · 98 lines · 95 tokens per session scan A b53fb8494497
sonovault-music-metadata is a skill published in the GitHub repository rekordcloud/sonovault-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 100 tokens to every session and 1,802 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.