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-open-prnpx skills add webern/mx --skill mx-open-prgit 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.00032 | $0.00540 |
| Opus 5 | $0.00016 | $0.00270 |
| Sonnet 5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
mx-open-pr 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.
What it actually says
/mx-open-pr
Use <prompt> and your context to understand what the PR is about. Check to see if there is
documentation on the issue available in docs/ai/api-feature-audit.md (which might be the case if
it was previously documented by an api-feature-audit).
Use gh for GitHub interactions.
Search the open issues for one that this PR would close or that it is related to. Make a list of issues that it closes and issues that is related to. It might also be related to other PRs.
When writing the PR, the title should be lowercase and start with one keyword, e.g.
- build: add cache to make fmt for ci
- chore: clean up stale code comments
- docs: add a new ai skill
- feat: add coda to mx::api support
Look at the labels on GitHub, choose the ones that match the pr best.
Write a PR body. Keep it tight and human-readable, but with enough information to understand what was done and why.
Determine from the original prompt whether the user wanted you to YOLO and open or whether the user wanted to see a draft first.
When ready, create the pr and note the pr number. Make sure the PR body contains references to issues closed and issues/PRs related (if any).
No self-attribution in the PR body; add the ai label instead.
Do not use excessive bold and italics in the PR body. Go easy on the keywords since they will add a lot of backtick formatting as well.
Template/sample:
## Human Summary
TODO: human writes here
## Summary
`accidentalMap` in `Converter.cpp` was missing the entry for `sharpSharp`. Added a single item to the map so that the
double sharps are now fully supported in `mx::api`.
## Testing
- [x] `SharpSharp_PitchData` fails before the fix, passes after
- [x] All PitchData tests pass (`*_PitchData`: 37 assertions in 8 test cases)
- [x] Full test suite passes (3917 assertions in 219 test cases)
## References
- Closes #123
- Progresses #456
- Fixes a bug introduced in #789
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.
- 2d ago First seen · 65 lines · 32 tokens per session scan A ef2874e8e9e3
mx-open-pr is a skill published in the GitHub repository webern/mx (93 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 540 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…