Material UI is a React component library that provides an independent implementation of Google's Material Design system. Developers use it to build interfaces from reusable React components, with additional advanced components available through MUI X. The catalogue add-ons provide project-specific skills and instructions for working with Material UI.
Borrowing it
Nothing to install: this file belongs to mui/material-ui. 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/mui/material-ui/master/.agents/skills/mui-release/SKILL.mdgit clone --depth 1 https://github.com/mui/material-uiWrote 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/mui/material-ui/mui-release)<a href="https://agentmods.dev/skills/mui/material-ui/mui-release"><img src="https://agentmods.dev/badge/skills/mui/material-ui/mui-release/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/mui/material-ui/mui-release"><img src="https://agentmods.dev/badge/skills/mui/material-ui/mui-release.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00724 |
| Opus 5.5 | $0.00012 | $0.00290 |
| Sonnet 5.5 | $0.00006 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
mui-release scanned grade A with 1 finding 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 27d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s <docs-url> | grep "<version>" # or check the Netlify dashboard How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MUI Release
Every MUI repo releases through the same staged pipeline. Each stage depends on the previous one completing — never start a stage before its predecessor is done. This skill describes the shared skeleton; the details vary per repo.
Resumable: the skill can be invoked at any stage — a release often spans multiple sessions (e.g. the PR was created and merged earlier, and the user now wants to trigger the npm publish). In the pipeline diagram below, each arrow out of a stage states the observable evidence that the stage is complete: resume at the first stage whose evidence is missing. Confirm the detected stage with the user before continuing; earlier stages' outputs are inputs, not work to redo.
Source of truth: the target repo's scripts/README.md is the authoritative, evolving runbook. Always read it in the target checkout before releasing; use this skill to know what the stages mean and what to expect. Where the README contradicts this skill, the README wins. Repo-specific steps (docs release pages, hotfix flows, prerelease progressions, docs-only deploys, first-time package publishing) live only there. Repos without that runbook: read their release workflow directly.
The pipeline
Each stage's instructions live in its own file — after detecting and confirming the current stage, read that stage's file:
flowchart TD
S1["Stage 1: Prepare the release PR\n(stage-1-prepare-pr.md)"]
S2["Stage 2: Merge the PR, then publish\n(stage-2-publish-packages.md)"]
S3["Stage 3: Publish the docs\n(stage-3-publish-docs.md)"]
S4["Stage 4: Publish the GitHub release, then announce\n(stage-4-github-release.md)"]
S1 -- "open PR with the release label,\napproved, CI green" --> S2
S2 -- "release PR merged, packages on npm at\nthe new version, draft GitHub release created" --> S3
S3 -- "docs live for the new version" --> S4
S4 -- "published non-draft GitHub release for the\ncurrent root package.json version\n(release done, next one starts at Stage 1)" --> S1
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 27d ago First seen · 50 lines · 31 tokens per session scan A b343671063aa
mui-release is a skill published in the GitHub repository mui/material-ui (99,284 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 724 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.
Other skills, from other repositories
publish-notes
Draft user-facing release notes, store changelogs, and internal publish summaries.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
github-release
Prepare and publish GitHub releases. Sanitizes code for public release (secrets scan, personal artifacts, LICENSE/README validation), creates version tags, and publishes via gh CLI. Trigger with 'release', 'publish', 'open source', 'prepare for release', 'create release', or 'github release'.
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
releasing-weaverse-sdks
Use when releasing @weaverse/ npm packages, bumping SDK versions, publishing to npm, or shipping the Weaverse SDKs. Triggers on "release sdk", "release weaverse", "publish packages", "release core", "release schema", "bump sdk version", "ship sdks".
release-retrospective
Review how a shipped release, migration or deprecation went against its plan: blast radius, comms, migration, timeline, support load, each gap classed. Triggers: release retro, post-mortem, how did the deprecation go. Planning a new deprecation: deprecation-process.