MFLUX is a native MLX implementation of generative image models that runs locally on Mac computers. It is for generating images with supported models through command-line tools or a Python API. The catalogue skills and instruction support workflows built around these image-generation models.
Borrowing it
Nothing to install: this file belongs to mflux-community/mflux. 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/mflux-community/mflux/main/.cursor/skills/mflux-release/SKILL.mdgit clone --depth 1 https://github.com/mflux-community/mfluxWrote 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/mflux-community/mflux/mflux-release)<a href="https://agentmods.dev/skills/mflux-community/mflux/mflux-release"><img src="https://agentmods.dev/badge/skills/mflux-community/mflux/mflux-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/mflux-community/mflux/mflux-release"><img src="https://agentmods.dev/badge/skills/mflux-community/mflux/mflux-release.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.00043 | $0.00363 |
| Opus 5 | $0.00022 | $0.00181 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
mflux-release 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.
What it actually says
mflux release prep
Releases are prepared in-repo; tagging/publishing is handled by GitHub Actions
(release.yml, dispatched from main with the publish confirmation).
How notes work now (#685)
- Every PR carries a fenced
```release-noteblock in its body (CI enforces it;noneopts a PR out). That block is the only source of release notes. - On dispatch, the ungated
draft-notesjob harvests the blocks for every PR whose squash commit is inprevious-tag..HEADand fills a DRAFT GitHub release, grouped by label. - Whoever approves the
pypideployment reads and edits that draft (fixing any[needs edit]lines, adding contributor thanks if wanted); the gated job publishes it exactly as edited. A re-dispatch never overwrites an existing draft; delete the draft to re-harvest. - There is no
CHANGELOG.md: the notes live in GitHub Releases (https://github.com/mflux-community/mflux/releases).
Release-prep PR checklist
- Bump version in
pyproject.toml - Update lockfile:
uv lock - Release-note block of the prep PR itself:
none - Prefer one commit named
release: prepare <version> - Sanity checks (optional unless requested):
just test-fast,just build - Do not tag releases locally unless explicitly requested (normally handled by CI)
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 Changed · -10 lines · +6 tokens per session 2f6781850b92
- 10d ago First seen · 41 lines · 37 tokens per session scan A 2a79dcfc54f7
mflux-release is a skill published in the GitHub repository mflux-community/mflux (2,316 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 363 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
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
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.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.