Borrowing it
Nothing to install: this file belongs to webern/mx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/webern/mx/main/.agents/skills/mx-open-issue/SKILL.mdgit clone --depth 1 https://github.com/webern/mxWrote 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/webern/mx/mx-open-issue)<a href="https://agentmods.dev/skills/webern/mx/mx-open-issue"><img src="https://agentmods.dev/badge/skills/webern/mx/mx-open-issue/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/webern/mx/mx-open-issue"><img src="https://agentmods.dev/badge/skills/webern/mx/mx-open-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00361 |
| Opus 5.5 | $0.00012 | $0.00144 |
| Sonnet 5.5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
mx-open-issue 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.
What it actually says
/mx-open-issue
Use <prompt> to understand what the issue 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 it would duplicate. If it would fully or exactly duplicate an issue, then suggest editing or commenting on the existing issue instead of creating a new one.
Identify related issues and a potential parent/tracking issue.
When writing the issue, the title should be lowercase, e.g. fix missing flerbinator in mx::impl.
Look at the labels on GitHub, choose the ones that match the issue best.
Write an issue body. Keep it tight and human-readable, but with enough information to understand what needs to be done.
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 issue and note the issue number. Make sure the issue body contains references to related issues and/or PRs (if any are related). If it is a child of another issue, edit the tracking issue body to add it to the list of tracked issues and also make it a sub-issue of the tracker.
No self-attribution in the issue body; add the ai label instead.
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 · 38 lines · 30 tokens per session scan A 24902508390d
mx-open-issue is a skill published in the GitHub repository webern/mx (93 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 361 once invoked, about $0.0001 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.
Other skills, from other repositories
team-lead
Orchestrates large bodies of work (features, refactors, milestones, backlog tasks) using sub-agents as a team. Use this skill when the user explicitly asks you to "take responsibility", "orchestrate", "lead", or "team-lead" a set of tasks or a milestone. This is a manual-trigger skill — only activate when the user…
sfcc-business-manager
Configure Salesforce Commerce Cloud via Business Manager — manage catalogs, promotions, site preferences, and run XML import/export jobs.
score-composer
Compose original piano, chamber, and orchestral works as a score canon (compact DSL, MusicXML, MIDI, ABC, piano sheets, guitar tabs), then route to preview audio, Lyria 3, Suno, or live playing. Use for compose, sheet music, tabs, orchestra, piano works, notation, MusicXML.
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…