An arrangement agent for planning musical instrumentation, section dynamics, energy maps, production briefs, and MIDI export. It loads only the reference material relevant to the requested arrangement task and sends that work to a role-specific sub-agent.

Use it to decide instruments, shape energy across song sections, prepare an artist-free production brief, or create a MIDI export for a release package.

It keeps unrelated arrangement guidance out of the working context and routes different tasks through the appropriate music role. It can also distinguish instrumentation, dynamics, and production-brief requests.

arranger — Skill for Claude Code by P47Phoenix/Claude-Plugins

Install

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.

Any agent

npx skills add P47Phoenix/Claude-Plugins --skill arranger

Clone the repo

git clone --depth 1 https://github.com/P47Phoenix/Claude-Plugins

Made for: Claude Code.

Or install music-team, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/arranger/github.svg)](https://agentmods.dev/skills/p47phoenix/claude-plugins/arranger)

Your own site

<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/arranger"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/arranger/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/arranger"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/arranger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,796 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00105	$0.02796
Opus 5.5	$0.00042	$0.01118
Sonnet 5.5	$0.00021	$0.00559
Haiku 4.5	$0.00011	$0.00280

Measured 2d ago against content hash d899bc127ae9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

arranger 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.

music-team/skills/arranger/SKILL.md · 252 lines

How it starts

The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Arranger Agent

Design Principle: Role Context Isolation

This skill keeps arrangement knowledge out of the main context window. When an arrangement task is requested, the task type is detected, only the matched role manifest, one output contract, the genre's ## Arrangement and ## Rhythm sections, and at most two technique files are loaded, and a sub-agent is spawned with that isolated context. The main context receives only the finished artifact.

There is one dispatched role name, instrumentation, matching music-flow/references/stages.yml (Stage 6: agent arranger, role instrumentation, task arrangement). dynamics and production-brief are task types routed inside the same manifest, references/roles/instrumentation.md. The orchestrator may pass them as ROLE: values (Template 2 supporting roles); this skill normalises them to the manifest.

Passed as `ROLE:`	Passed as `TASK_TYPE:`	Resolved task type	Artifact
`instrumentation`	`arrangement`	instrumentation	`arrangement.md` (draft)
`dynamics`	`dynamics`	dynamics	`arrangement.md` (edited in place, owner)
`production-brief`	`production-brief`	production-brief	`production-brief.md`

Phase 1: Task Detection

Detect the task type from (in priority order):

Pipeline fields -- ROLE: and TASK_TYPE: in the prompt (see Pipeline Invocation); they win.
Explicit mention -- "write the production brief", "map the dynamics", "pick the instruments".
Signals -- see the routing table below.
Artifacts present -- an arrangement.md with no production-brief.md and a request for notes for a mixer or producer routes to production-brief.

If ambiguous, ask before proceeding. Do not assume. Example: "make it bigger" could mean more instruments (instrumentation) or a wider energy swing (dynamics); ask which.

Declare before every task:

Role: instrumentation | Task: [TYPE] | References: [list of reference files]

Read the full file on GitHub · 252 lines

Files

What ships with it

9 files 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.

Changes

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 · 252 lines · 105 tokens per session scan A d899bc127ae9

Subscribe to this mod's changes

arranger is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 105 tokens to every session and 2,796 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.

Creative and media

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens