Borrowing it
Nothing to install: this file belongs to bitwize-music-studio/claude-ai-music-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bitwize-music-studio/claude-ai-music-skills/main/CLAUDE.mdgit 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/instructions/bitwize-music-studio/claude-ai-music-skills/claude-md)<a href="https://agentmods.dev/instructions/bitwize-music-studio/claude-ai-music-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/bitwize-music-studio/claude-ai-music-skills/claude-md/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/instructions/bitwize-music-studio/claude-ai-music-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/bitwize-music-studio/claude-ai-music-skills/claude-md.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.04770 | $0.04770 |
| Opus 5 | $0.02385 | $0.02385 |
| Sonnet 5 | $0.00954 | $0.00954 |
| Haiku 4.5 | $0.00477 | $0.00477 |
Grade A, and why
claude-ai-music-skills CLAUDE.md 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.
AI Music Skills - Claude Instructions
This is an AI music generation workflow using Suno. Skills contain domain expertise; this file contains workflow rules and structure that apply every session.
⚠️ CRITICAL: Finding Albums When User Mentions Them
WHENEVER the user mentions an album name, use the resume skill:
/bitwize-music:resume my-album
If skill unavailable, manual approach:
- Read
~/.bitwize-music/cache/state.json— searchstate.albumskeys (case-insensitive) - If cache missing/stale: read config → glob
{content_root}/artists/{artist}/albums/*/*/README.md→ rebuild cache withrebuild_state()MCP tool
DO NOT: search from cwd, use complex globs, assume paths, or use ls/find.
Album slugs are globally unique across genres; if health_check reports a slug collision, resolve it (rename or move the directory, then rebuild) before trusting lookups.
Configuration & Path Resolution
Config is always at: ~/.bitwize-music/config.yaml
ALWAYS read config fresh before moving/creating files, resolving path variables, or using artist name in paths. Never assume or remember values.
Path variables (from config):
{content_root}=paths.content_root{audio_root}=paths.audio_root{documents_root}=paths.documents_root{tools_root}=~/.bitwize-music{plugin_root}= the directory containing this CLAUDE.md file (=${CLAUDE_PLUGIN_ROOT}in skills)[artist]=artist.name
IMPORTANT — Mirrored path structure:
{content_root}/artists/[artist]/albums/[genre]/[album]/ # Album files (in git)
{audio_root}/artists/[artist]/albums/[genre]/[album]/ # Mastered audio
{documents_root}/artists/[artist]/albums/[genre]/[album]/ # PDFs (not in git)
Audio and document paths include [artist]/ after the root. Common mistake: omitting the artist folder.
First-time setup: cp config/config.example.yaml ~/.bitwize-music/config.yaml — see config/README.md.
MCP Server — Preferred Data Access
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 · 4,770 tokens per session scan A 146896596cb3
claude-ai-music-skills CLAUDE.md is an instructions file published in the GitHub repository bitwize-music-studio/claude-ai-music-skills (483 stars, last pushed 2d ago), licensed CC0-1.0. It adds 4,770 tokens to every session, about $0.0238 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).