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 skills add kunitoki/sonic-skills --skill juce-guidegit clone --depth 1 https://github.com/kunitoki/sonic-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/skills/kunitoki/sonic-skills/juce-guide)<a href="https://agentmods.dev/skills/kunitoki/sonic-skills/juce-guide"><img src="https://agentmods.dev/badge/skills/kunitoki/sonic-skills/juce-guide/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/kunitoki/sonic-skills/juce-guide"><img src="https://agentmods.dev/badge/skills/kunitoki/sonic-skills/juce-guide.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.00108 | $0.00975 |
| Opus 5.5 | $0.00043 | $0.00390 |
| Sonnet 5.5 | $0.00022 | $0.00195 |
| Haiku 4.5 | $0.00011 | $0.00097 |
Grade A, and why
juce-guide 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 2mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JUCE Audio Plugin — Build Guide
Five steps from empty folder to distributable plugin. Do each step in order; skip none.
Step 1 — Project setup (CMake + JUCE)
- Add JUCE as a git submodule or FetchContent target; call
add_subdirectory(JUCE). - Use
juce_add_plugin(MyPlugin FORMATS VST3 AU Standalone ...)to declare the plugin target. - Set
PLUGIN_MANUFACTURER_CODE,PLUGIN_CODE,IS_SYNTH,NEEDS_MIDI_INPUTin the same call. - Link
juce::juce_audio_processors juce::juce_audio_utils juce::juce_dspto the target.
Step 2 — AudioProcessor skeleton
- Subclass
juce::AudioProcessor; overrideprepareToPlay,releaseResources,processBlock. - In
prepareToPlay: storesampleRateandmaximumBlockSize, allocate internal buffers, reset all state (filters, envelopes, delay lines — unconditionally). - In
processBlock: read only pre-cached raw parameter pointers; never allocate, never call JUCE String ops or DBG(). - Implement
getStateInformation/setStateInformationusingapvts.copyState()andapvts.replaceState()with aMemoryOutputStream/MemoryBlock.
Step 3 — Parameters via APVTS
- Declare a static
createParameterLayout()method that returnsAudioProcessorValueTreeState::ParameterLayout. - Construct
apvts(*this, nullptr, "Parameters", createParameterLayout())as a member. - After constructing APVTS, cache raw pointers once:
gainParam = apvts.getRawParameterValue("Gain"). - In
processBlock, dereference withgainParam->load()— no APVTS calls on the audio thread. - Use
AudioProcessorValueTreeState::ParameterAttachment(orSliderAttachment) in the editor, never in the processor.
Step 4 — Editor and UI
- Subclass
juce::AudioProcessorEditor; callsetSize(w, h)in the constructor. - Override
paintfor background / labels; overrideresizedto lay out components withsetBounds. - Declare
juce::Slidermembers; attach each viajuce::AudioProcessorValueTreeState::SliderAttachment. - Keep all UI state in the editor — the processor must function correctly with no editor open.
- The editor holds a reference to the processor (passed in constructor); never store a raw editor pointer in the processor.
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.
- 2mo ago First seen · 65 lines · 108 tokens per session scan A e13cf9f8714a
juce-guide is a skill published in the GitHub repository kunitoki/sonic-skills (23 stars, last pushed 5mo ago), licensed Unlicense. It adds 108 tokens to every session and 975 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-08-30.
juce-guide compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| juce-guidekunitoki/sonic-skills | Skill | 23 | 5mo ago | Unlicense | A | 108 | Claude Code, Codex |
| coding-guidance-qtn-n-code/n-n-code-skills | Skill | 4 | 5d ago | MIT | A | 67 | Claude Code, Codex |
| coding-guidance-cppn-n-code/n-n-code-skills | Skill | 4 | 5d ago | MIT | A | 72 | Claude Code, Codex |
| cpp-proJeffallan/claude-skills | Skill | 12k | 7d ago | MIT | A | 79 | Claude Code |
| embedded-stm32Mindrally/skills | Skill | 297 | 29d ago | Apache-2.0 | A | 87 | Claude Code |
| cppMindrally/skills | Skill | 297 | 29d ago | Apache-2.0 | A | 23 | Claude Code |
| backend-developmentMindrally/skills | Skill | 297 | 29d ago | Apache-2.0 | A | 31 | Claude Code |