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 P47Phoenix/Claude-Plugins --skill music-releasegit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWrote 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/p47phoenix/claude-plugins/music-release)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/music-release"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/music-release/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/p47phoenix/claude-plugins/music-release"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/music-release.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.00092 | $0.01260 |
| Opus 5.5 | $0.00037 | $0.00504 |
| Sonnet 5.5 | $0.00018 | $0.00252 |
| Haiku 4.5 | $0.00009 | $0.00126 |
Grade A, and why
music-release 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Music Release
Runs inline via the Skill tool (dispatch: skill), not as an Agent dispatch.
Stage 7c. Inline skill (no sub-agent): it copies, formats and summarises artifacts that already passed their gates. It
writes no new lyric, chord or note, and edits no source artifact. Layout and grammar live in
references/contracts/package-output.md; the type matrix and loop rules are in music-flow/references/stages/07-release.md.
Phase 1: Preconditions
- Resolve the song directory:
.song/activenames the slug; the directory is.song/<slug>/. Standalone with no.song/active, ask which directory holds the artifacts, or use the current one. - Read
state.jsonforsong_type,run_id,loops_used,gates,gate_overrides,accepted_best. Missingstate.json(standalone): note "no gate history" inrelease-notes.mdand continue. - Release starts only after 7b passed:
gates.releaseis PASS or SKIPPED, orchallenge-report.mdhas no BLOCKER row. Otherwise stop and sayNOT RELEASABLE: BLOCKER rows remain; package nothing. - Read
brief.mdfront-matter for title, genre and language.
Phase 2: Package by type
| Type | Files written to package/ |
|---|---|
| FULL_SONG, JINGLE, REVISE | lyric-sheet.md, lead-sheet.abc, song.mid, one-pager.md, release-notes.md |
| INSTRUMENTAL | lead-sheet.abc, song.mid, one-pager.md, release-notes.md (no lyric sheet) |
| ADAPT_GENRE | the full set plus a copy of adaptation-report.md |
| TOPLINE | lyric-sheet.md, lead-sheet.abc, song.mid, release-notes.md |
| LYRICS_ONLY, REWRITE | lyric-sheet.md, release-notes.md |
| AUGMENT_LYRICS | lyric-sheet.md (the whole augmented lyric), new-sections.md (only the added sections), release-notes.md |
| THEORY, PARODY_ADAPT | nothing (not released) |
Write each file per references/contracts/package-output.md. Create package/ first (mkdir -p). Never write outside it.
MIDI export
For every type with chords.md or melody.abc, run from the song directory:
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 · 93 lines · 92 tokens per session scan A 4b4a3ed2ec33
music-release is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 1,260 once invoked, about $0.0004 per session on Opus 5.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-10-26.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…