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/webern/mx/mx-api-add-featurenpx skills add webern/mx --skill mx-api-add-featuregit clone --depth 1 https://github.com/webern/mxWhat 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.00037 | $0.00558 |
| Opus 5 | $0.00018 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
mx-api-add-feature 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 yesterday.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add an mx::api feature
Read the mx-api-doctrine skill before designing, implementing, or reviewing the change.
Investigate
Establish the requested user-facing behavior before choosing an implementation:
- Find the relevant MusicXML elements and attributes in the schema and corpus.
- Check whether
mx::apialready represents the feature under a different shape or name. - Inspect the generated
mx::coretypes, which always implement the requested features. - Find analogous api types, reader/writer code, and tests to use as patterns.
Design and implement
Choose an api shape using the doctrine and precedent rather than mirroring MusicXML's shape. Keep the change focused on the requested behavior, but include whatever representation is needed to make that behavior sound.
Feature work commonly touches:
- public data types in
src/include/mx/api/ - core-to-api translation in
src/private/mx/impl/*Reader*or*Functions* - api-to-core translation in
src/private/mx/impl/*Writer*or*Functions* - enum conversion in
src/private/mx/impl/Converter.* - tests in
src/private/mxtest/api/
These are landmarks, not a checklist. Follow the closest existing feature through both translation directions and change only the files the design requires. Do not edit generated core files by hand.
Verify
- Check API round-trip discovery with
make api-roundtrip-discoverto see if you have unlocked a file. If so, add it to the round-trip baselinesrc/private/mxtest/api/roundtrip-baseline.txt. If your changes did not unlock a file, still add it and note that it was discovered already passing.
If your reader and writer functions seem complex, add testing. Here are some ideas:
- an in-memory
ScoreDataround trip withmxtest::roundTrip. Probe theScoreDatavalues in the unit test. - XML output/input checks with
mxtest::toXmlandmxtest::fromXml
Run the applicable gates from AGENTS.md; api feature work normally includes make api-test,
make api-roundtrip, and make fmt.
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.
- yesterday First seen · 55 lines · 37 tokens per session scan A 469c9b4d6857
mx-api-add-feature is a skill published in the GitHub repository webern/mx (93 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 558 once invoked, about $0.0002 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-30.
Other skills, from other repositories
musicbox
Use when the user wants to play/pause/skip music, control volume, seek, search songs/playlists, query NetEase Music data, or operate NetEase MusicBox. Drives MusicBox through the musicbox CLI + daemon; never simulates terminal keypresses to the curses TUI.
spotatui-dj
Be the DJ for spotatui, the terminal music player, by driving its MCP server. Use whenever the user asks for music, asks you to DJ, wants tracks queued, played, skipped, or searched, asks what they have been listening to, or mentions spotatui.
videoagent-audio-studio
Tired of juggling multiple audio APIs? This skill gives you one-command access to TTS, music generation, sound effects, and voice cloning. Use when you want to generate any audio without managing multiple API keys.
agents
Build voice AI agents with ElevenLabs. Use when creating voice assistants, customer service bots, interactive voice characters, or any real-time voice conversation experience, and when configuring an agent's tools, workflows, or procedures, including creating, editing, compiling, and publishing procedure drafts on an…
update-skills-from-changelog
Update ElevenLabs agent skills from a merged weekly changelog in elevenlabs-dx, then open a pull request in elevenlabs/skills. Trigger after a changelog merges to main on elevenlabs-dx, or when asked to update skills from changelog YYYY-MM-DD.
dubbing
Dub audio and video into other languages using the ElevenLabs Dubbing API (dubbingv2), preserving the original speakers' voices. Use when translating videos, podcasts, or recordings into other languages, localizing media content, reviewing or correcting dubbing transcripts and translations, or regenerating a dub after…