Borrowing it
Nothing to install: this file belongs to multiplex-ai/muggle-ai-works. 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/multiplex-ai/muggle-ai-works/master/.claude/skills/mrelease/SKILL.mdgit clone --depth 1 https://github.com/multiplex-ai/muggle-ai-worksWrote 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/multiplex-ai/muggle-ai-works/mrelease)<a href="https://agentmods.dev/skills/multiplex-ai/muggle-ai-works/mrelease"><img src="https://agentmods.dev/badge/skills/multiplex-ai/muggle-ai-works/mrelease.svg" alt="Measured on agentmods" 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.00045 | $0.00090 |
| Opus 5 | $0.00023 | $0.00045 |
| Sonnet 5 | $0.00009 | $0.00018 |
| Haiku 4.5 | $0.00005 | $0.00009 |
Grade A, and why
mrelease 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 8d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 9 lines · 45 tokens per session scan A 708e4eb7b471
mrelease is a skill published in the GitHub repository multiplex-ai/muggle-ai-works (17 stars, last pushed yesterday), with no licence file. It adds 45 tokens to every session and 90 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
release-testing-workflow
Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
AI Release Guardian
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
upgrade
Use this when you receive an [Upgrade Event: x.y.z→a.b.c] lick — fired on boot whenever the bundled SLICC version differs from the previous run. The lick renders a binary action card: lickconfirm to Update workspace files (three-way merge of bundled vfs-root files against the user's local edits) or lickdismiss to…
versioning-by-impact
Use when completing a task and deciding whether repository changes require a semantic version bump and changelog entry before commit/push.
release-readiness
Validate release readiness with evidence-based go/no-go decisions. Covers go/no-go checklists, smoke test suite design, staged rollout validation, rollback criteria and procedures, and post-deployment verification. Ensures release confidence comes from data, not feelings. Use when: "release ready," "go/no-go," "smoke…