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 agentmods add skills/generous-corp/pulp/vst3npx skills add Generous-Corp/pulp --skill vst3git clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/generous-corp/pulp/vst3)<a href="https://agentmods.dev/skills/generous-corp/pulp/vst3"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/vst3.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.16303 |
| Opus 5 | $0.00023 | $0.08152 |
| Sonnet 5 | $0.00009 | $0.03261 |
| Haiku 4.5 | $0.00005 | $0.01630 |
Grade C, and why
vst3 scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/Library/Audio/Plug-Ins/VST3/MyPlugin*.vst3 How it starts
The opening of the file, as written. The whole thing — 1,206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VST3 Skill
Use this skill when touching Pulp's VST3 adapter, when answering
questions about how a Pulp plugin behaves inside Cubase / Nuendo /
Studio One / Reaper (VST3 lane) / FL Studio / Ableton Live (VST3
lane), or when a pluginval run surfaces something odd. VST3 is one
of Pulp's three first-class plugin formats alongside CLAP and AU v3.
When to use
- Editing
core/format/src/vst3_adapter.cppor its header. - Changing the generator macro
PULP_VST3_PLUGIN(…)incore/format/include/pulp/format/vst3_entry.hpp. - Changing bus-arrangement negotiation, parameter registration, MIDI event routing, state save/restore, or editor lifecycle.
- A VST3 host reports a behaviour issue — sidechain not exposed, mono↔stereo swap crashes the track, automation not recorded, tempo-sync glitches, preset load misbehaves.
- A
pluginval --strictness-level 5run regresses. - Working on the ARA VST3 surface — but first read the
araskill.
Files and entry points
| Role | Path |
|---|---|
| Core adapter (C++) | core/format/src/vst3_adapter.cpp |
Adapter header / PulpVst3Processor |
core/format/include/pulp/format/vst3_adapter.hpp |
| Entry-point generator macro | core/format/include/pulp/format/vst3_entry.hpp |
Editor IPlugView implementation |
core/format/src/vst3_plug_view.cpp, core/format/include/pulp/format/vst3_plug_view.hpp |
| Info.plist template (macOS bundle) | tools/cmake/PulpInfoPlist.vst3.in |
| VST3 SDK fetch | external/vst3sdk — git clone --depth 1 --branch v3.8.0_build_66 https://github.com/steinbergmedia/vst3sdk.git (MIT) |
| CLI validator invocation | tools/cli/cmd_validate.cpp (pluginval --strictness-level 5 --timeout-ms 30000 --validate …) |
There is no hand-written PulpVst3.cmake helper — the VST3 target is
wired directly in the top-level CMakeLists.txt / PulpPlugin CMake
surface.
The VST3 editor lives in a sibling file (vst3_plug_view.cpp) that is
owned by the view-bridge skill per skill_path_map.json. Edits
to the editor surface trigger the view-bridge skill rather than
this one.
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.
- today First seen · 1,206 lines · 46 tokens per session scan C e97744f2089b
vst3 is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 16,303 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…