plan

A planning skill for designing audio plug-ins, which are programs that process or generate sound inside music software. It reads a creative brief and parameter specification, then creates the plug-in’s technical design and implementation plan.

In plain words
What is it for?
Use it to plan the sound-processing components, control behavior, technical architecture, and coding strategy for an audio plug-in.
Why use it?
It turns an audio idea and its controls into a clear structure before coding begins. It also assesses the work’s complexity and identifies an implementation approach.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/noizefield/audio-plugin-coder/plan
Any agent
npx skills add Noizefield/audio-plugin-coder --skill plan
Clone the repo
git clone --depth 1 https://github.com/Noizefield/audio-plugin-coder

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,310 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02310
Opus 5 $0.00000 $0.01155
Sonnet 5 $0.00000 $0.00462
Haiku 4.5 $0.00000 $0.00231

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

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agent/skills/plan/SKILL.md · 342 lines

How it starts

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

SKILL: ARCHITECTURE & PLANNING

Goal: Define DSP architecture, complexity assessment, and implementation strategy Trigger: /plan [Name] Input: Reads $PluginPath/.ideas/creative-brief.md and parameter-spec.md Output Location: $PluginPath/.ideas/


🎯 PHASE 2: PLAN (Architecture & Strategy)

Prerequisites:

  • $PluginPath/.ideas/creative-brief.md exists
  • $PluginPath/.ideas/parameter-spec.md exists
  • Phase 1 (DREAM) complete

Output Files:

  • $PluginPath/.ideas/architecture.md - DSP component design
  • $PluginPath/.ideas/plan.md - Implementation strategy and complexity assessment

📋 STEP 1: ARCHITECTURE DEFINITION

1.1 Read Input Contracts

Read these files in parallel:

  • $PluginPath/.ideas/creative-brief.md - Plugin concept and behavior
  • $PluginPath/.ideas/parameter-spec.md - Parameter definitions and ranges

1.2 Define DSP Architecture

Create $PluginPath/.ideas/architecture.md with this structure:

# DSP Architecture Specification

## Core Components
List the main DSP building blocks needed:

**Example for a compressor:**
- Input gain stage
- Sidechain detection (RMS/Peak)
- Gain computer (log/linear)
- Lookahead delay buffer
- Output gain stage

**Example for a delay:**
- Input buffer management
- Delay line (circular buffer)
- Feedback processing
- Mix control
- Output processing

## Processing Chain
Define the signal flow:

Input → [Component 1] → [Component 2] → ... → Output


**Example:**

Input → Input Gain → Sidechain → Detector → Gain Computer → Lookahead → Output Gain → Output


## Parameter Mapping
Map each parameter to DSP components:

| Parameter | Component | Function | Range |
|-----------|-----------|----------|-------|
| Threshold | Detector | Sets detection level | -60dB to 0dB |
| Ratio | Gain Computer | Sets compression ratio | 1:1 to 20:1 |
| Attack | Detector | Sets attack time | 0.1ms to 100ms |

## Complexity Assessment
Rate the plugin complexity (1-5):

**Level 1 (Simple):** Basic gain, simple filter, single parameter
**Level 2 (Moderate):** Multi-parameter, basic dynamics, simple modulation
**Level 3 (Advanced):** Multi-band processing, complex algorithms, state management
**Level 4 (Expert):** Synthesis engines, complex feedback, real-time analysis
**Level 5 (Research):** Machine learning, complex modeling, advanced DSP

**Score: [1-5]**
**Rationale: [Explain the complexity factors]**

Read the full file on GitHub · 342 lines

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.

  1. 2d ago First seen · 342 lines · 0 tokens per session scan A eee97ee63f61

Subscribe to this mod's changes

plan is a skill published in the GitHub repository Noizefield/audio-plugin-coder (313 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,310 tokens. 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.

Related

Other skills, from other repositories

general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…

heygen-com/hyperframes · 92 tokens

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

diagnostic-stem-delivery

Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.

HKUDS/OpenSpace · 23 tokens

vox-director

Turn ONE topic into a finished Vox-style paper-collage explainer / ad video, end to end on the Atlas Cloud API + local ffmpeg — script, collage keyframes, motion, voice-over, music, captions, all automated. Use this whenever the user wants a "Vox style" video, a paper/torn-paper collage animation, a "motion collage"…

Alisa0808/vox-director · 236 tokens

seedance-vocab-ja

This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.

Emily2040/seedance-2.0 · 50 tokens

model-compatibility

Model family compatibility matrix covering loaders, resolutions, samplers, CFG, VAE, ControlNet, and LoRA compatibility for SD 1.5, SDXL, Flux, SD3, and video models.

artokun/comfyui-mcp · 47 tokens