test-in-serum

test-in-serum is a skill for Claude Code from Celian-mrc/serum-mcp. It costs 108 tokens per session (872 once invoked), scanned A, original, MIT.

A pre-release checker for SerumPreset files, which are saved presets for the Serum music synthesizer. It scans the file's CBOR data types and gives a readable summary before a real Serum loading test.

In plain words
What is it for?
Use it after generating or editing presets to scan every file, stop on wire-format failures, and decide when it is safe to ask someone to test the preset in Serum.
Why use it?
Automated tests can miss file-format errors that only make the synthesizer crash when the preset is loaded.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is uv run python scripts/check_preset.py "<path-to-preset>" ["<path-to-preset-2>" ...].

Good fit Use it after generating or editing presets to scan every file, stop on wire-format failures, and decide when it is safe to ask someone to test the preset in Serum.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Celian-mrc/serum-mcp
agentmods
npx agentmods add skills/celian-mrc/serum-mcp/test-in-serum

Made for: Claude Code.

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.

agentmods badge for test-in-serum

README.md
[![agentmods](https://agentmods.dev/badge/skills/celian-mrc/serum-mcp/test-in-serum/github.svg)](https://agentmods.dev/skills/celian-mrc/serum-mcp/test-in-serum)
Your own site
<a href="https://agentmods.dev/skills/celian-mrc/serum-mcp/test-in-serum"><img src="https://agentmods.dev/badge/skills/celian-mrc/serum-mcp/test-in-serum/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.

agentmods 80×15 button for test-in-serum

Your own site · 80×15
<a href="https://agentmods.dev/skills/celian-mrc/serum-mcp/test-in-serum"><img src="https://agentmods.dev/badge/skills/celian-mrc/serum-mcp/test-in-serum.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 872 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00108 $0.00872
Opus 5 $0.00054 $0.00436
Sonnet 5 $0.00022 $0.00174
Haiku 4.5 $0.00011 $0.00087

Measured 11d ago against content hash 051bb4d6f78c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

test-in-serum 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 11d 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.

.claude/skills/test-in-serum/SKILL.md · 61 lines

How it starts

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

Test a serum-mcp preset before asking the user to load it

This project's own hard-won lesson (see docs/PARAMETER_SCHEMA.md and CONTRIBUTING.md): unit tests and round-trip checks are not sufficient to prove a generated preset works. The first fully-tested preset this project shipped still crashed FL Studio ~2 seconds after being selected, from a CBOR wire-type mismatch no amount of self-consistent round-tripping could catch. That specific failure class is now automatable; whether the preset actually sounds right, or loads without some other real-Serum-only issue, is not -- that part still needs the user.

Steps

  1. Run the automated scan on every preset file involved:

    uv run python scripts/check_preset.py "<path-to-preset>" ["<path-to-preset-2>" ...]
    

    If mid-session code changes to src/serum_mcp/ haven't been picked up by a normal uv run yet (e.g. the entry-point .exe is locked by a connected MCP server process, a known Windows gotcha this session hit repeatedly), use uv run --no-sync python scripts/check_preset.py ... instead.

  2. If it reports FAIL (a CBOR wire-type issue): stop -- do not tell the user to load the file. This means a real bug slipped past preset/validator.py's normalization. Go fix preset/mapping.py (or wherever the offending value was written), rerun the scan, and only proceed once it's clean. This is a hard gate, not a warning to note and move past.

  3. If it reports OK: summarize the preset's key sections (oscillators, filters, envelope shape, FX chain, mod routes -- whatever's relevant to what was just generated/edited) for the user in a few lines, pointing out anything worth specifically checking in Serum's UI (e.g. "a new FX type that's never been tested live before", "a custom-synthesized wavetable", "an edited param that should have changed vs. what should have stayed the same").

  4. Ask the user to load it and report back -- don't declare the feature/fix done based on the scan alone. If this was verifying a fix for something the user already reported, be specific about what changed and what you want them to check (the original symptom, not just "does it work").

Read the full file on GitHub · 61 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. 11d ago First seen · 61 lines · 108 tokens per session scan A 051bb4d6f78c

Subscribe to this mod's changes

test-in-serum is a skill published in the GitHub repository Celian-mrc/serum-mcp (5 stars, last pushed 9d ago), licensed MIT. It adds 108 tokens to every session and 872 once invoked, about $0.0005 per session on Opus 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-31.

Related

Other skills, from other repositories

resolume-mcp-tester

Test and operate the Resolume MCP server (resolume-mcp-server) end-to-end against a live Resolume Arena. Use when verifying tool behavior, running smoke tests, doing safe live VJ demos, or validating new tools added to the project. Includes white-out prevention rules, state restoration patterns, and agent invocation…

mackatwentytsuru/resolume-mcp-server · 75 tokens

acestep-songwriting

Music songwriting guide for ACE-Step. Provides professional knowledge on writing captions, lyrics, choosing BPM/key/duration, and structuring songs. Use this skill when users want to create, write, or plan a song before generating it with ACE-Step.

timoncool/ACE-Step-Studio · 55 tokens

maya-scripting

Bootstrap stage — escape hatch for Maya work that has no packaged skill yet. Agents should prefer searchskills / dcccapabilitymanifest → loadskill → typed tools (inputSchema + annotations) from domain skills; use executepython or executemel only when no skill matches, for bulk in-process loops, or for API…

dcc-mcp/dcc-mcp-maya · 100 tokens

threebrowser-studio-mcp

Author, inspect, render, validate, animate, and save Three.js WebGPU projects in the native ThreeBrowser Studio through its real threestudio MCP tools. Use whenever Codex is asked to build or edit a ThreeBrowser Studio scene, material, Blender-style shader or texture graph, animation, lighting setup, camera, or…

SamG-Coder/ThreeBrowserStudio · 122 tokens

ad-creative-v2

Ad Creative workflow skill. Use this skill when the user needs Create, iterate, and scale paid ad creative for Google Ads, Meta, LinkedIn, TikTok, and similar platforms. Use when generating headlines, descriptions, primary text, or large sets of ad variations for testing and performance optimization and the operator…

diegosouzapw/awesome-omni-skills · 85 tokens

maya-bifrost

Authoring stage - typed Bifrost procedural modeling and graph construction in Maya. Use to create graph shapes or boards, add Bifrost nodes, set input defaults, and connect ports. Not for ordinary Maya DG nodes (maya-node-graph), polygon edits (maya-mesh-ops), or arbitrary Python/MEL (maya-scripting).

dcc-mcp/dcc-mcp-maya · 75 tokens