Borrowing it
Nothing to install: this file belongs to jeremyruppel/claude-collider. 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/jeremyruppel/claude-collider/main/.claude/skills/arrange-tape/SKILL.mdgit clone --depth 1 https://github.com/jeremyruppel/claude-colliderWrote 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/jeremyruppel/claude-collider/arrange-tape)<a href="https://agentmods.dev/skills/jeremyruppel/claude-collider/arrange-tape"><img src="https://agentmods.dev/badge/skills/jeremyruppel/claude-collider/arrange-tape/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/jeremyruppel/claude-collider/arrange-tape"><img src="https://agentmods.dev/badge/skills/jeremyruppel/claude-collider/arrange-tape.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 118 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00030 | $0.01373 |
| Opus 5.5 | $0.00012 | $0.00549 |
| Sonnet 5.5 | $0.00006 | $0.00275 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
arrange-tape 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arrange Tape
This skill composes an arrangement for a tape — the performance plan for how elements are introduced, removed, and layered over time.
What is an arrangement?
A tape's .scd defines all the musical elements (Pdefs, Ndefs, effects, sidechains). An arrangement defines when each element plays and stops, turning a static loop into a track with structure.
Arrangements use CCArrangement — a declarative class where you list sections as [name, bars, elements] arrays. The class handles all Pdef/Ndef start/stop diffing and uses TempoClock.schedAbs for drift-free timing.
Process
Step 1: Understand the tape
Read the tape's .md and .scd files to understand:
- What elements exist (all Pdef/Ndef names)
- The tempo (needed to calculate total duration)
- The vibe/genre (informs pacing and conventions)
- Effects and sidechains (may need to be activated/deactivated per section)
Step 2: Plan the arrangement with the user
Propose a section-by-section plan. Use standard arrangement conventions for the genre. Common structures:
Dance/electronic (~2-4 min):
- Intro → Build → Drop → Break → Drop 2 → Outro
Ambient/textural:
- Emerge → Develop → Peak → Dissolve
Hip-hop/R&B:
- Intro → Verse → Hook → Verse 2 → Hook → Outro
For each section, specify:
- Name and length in bars
- Which elements are active during that section
- Any parameter changes (effect tweaks, filter sweeps, etc.)
Present the plan as a table or outline and get user approval before writing code.
Step 3: Write the arrangement
IMPORTANT: The arrangement does NOT go into the tape's .scd file. Tape .scd files define elements only — no arrangement logic. Instead, do one of:
Option A: Live performance — Execute via cc_execute during a session.
Option B: Separate file — Write to tapes/<name>-arrangement.scd if the user wants to save it.
The arrangement code follows this pattern:
// First, execute the tape's .scd to define all elements
// (but remove .play from each Pdef/Ndef — arrangement controls when they start)
// Then execute the arrangement:
CCArrangement([
[\intro, 8, [\kick, \hat]],
[\build, 8, [\kick, \hat, \bass, \rim]],
[\drop, 16, [\kick, \hat, \bass, \rim, \lead, \pad]],
[\break, 8, [\hat, \pad]],
[\drop2, 16, [\kick, \hat, \bass, \rim, \lead, \pad]],
[\outro, 8, [\kick, \hat]],
]).play;
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.
- 1mo ago First seen · 135 lines · 30 tokens per session scan A 352d2452f47a
arrange-tape is a skill published in the GitHub repository jeremyruppel/claude-collider (59 stars, last pushed 12d ago), licensed MIT. It adds 30 tokens to every session and 1,373 once invoked, about $0.0001 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-08-30.
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…