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 skills add tofunori/atelier-studio --skill muxy-extensiongit clone --depth 1 https://github.com/tofunori/atelier-studioWrote 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/tofunori/atelier-studio/muxy-extension)<a href="https://agentmods.dev/skills/tofunori/atelier-studio/muxy-extension"><img src="https://agentmods.dev/badge/skills/tofunori/atelier-studio/muxy-extension/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/tofunori/atelier-studio/muxy-extension"><img src="https://agentmods.dev/badge/skills/tofunori/atelier-studio/muxy-extension.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.00077 | $0.05887 |
| Opus 5 | $0.00039 | $0.02943 |
| Sonnet 5 | $0.00015 | $0.01177 |
| Haiku 4.5 | $0.00008 | $0.00589 |
Grade A, and why
muxy-extension 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 10d 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.
- **Use `muxy.http.fetch` to call external APIs from a tab/panel/popover** instead of the webview's `fetch()` — the request goes out via native code, so it is **not CORS-blocked**, and a panel needs no `background.js` (n How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Muxy Extension Guide
A Muxy extension is an npm + Vite project: source under src/, an entry HTML that vite build emits into dist/, and Muxy reads dist/ when present (otherwise the project folder). The manifest is the "muxy" object in package.json. There is no fixed folder layout — every entry/background/icon path is an arbitrary relative path inside the build output (the vanilla starter kit emits its panel to panel/index.html); package.json and dist/ are the only names Muxy fixes. During development you don't copy into the config folder — Load Unpacked in the Extensions modal points Muxy at any folder (your git checkout is the install).
The build script must copy package.json into dist/. The publish pipeline ships only dist/, and the app reads the manifest from the install root — so the manifest has to be inside the build output. vite build alone emits your entry/asset paths but not the manifest, so use "build": "vite build && node scripts/copy-manifest.mjs" where copy-manifest.mjs copies package.json into dist/. Easy to miss because Load Unpacked falls back to the root package.json in dev, so it loads locally but fails validation/install when published. The vanilla starter kit already wires this up.
This skill is the guidance layer — how an extension should look and behave. For the API and manifest mechanics (every field, the permission strings, the full window.muxy surface, events, scripts), read the reference docs. Start from the LLM-friendly index, which lists every page and links to its raw Markdown source:
Append /plain to any docs URL for the raw Markdown of that page (e.g. https://muxy.app/docs/extensions/manifest/plain).
The goal of everything below: an extension should be indistinguishable from a native Muxy surface. Match the theme and match the scale, and it will be.
Pick the right surface
- Showing something to the user → a UI page (tab, panel, or popover). Page scripts get the full
window.muxyAPI. - A persistent, full-height navigation or control surface that replaces the built-in left sidebar → a
sidebar(one per extension; the user selects it in Settings → Sidebar). It fills the entire region — the project list and the footer — so own your own navigation. Samewindow.muxyAPI and theme variables as a panel. - Reacting durably to events, coordinating multiple webviews, or running shell commands headlessly → a
background.jsscript. It can also callmuxy.tabs.opento show a result in the active workspace. Most extensions don't need one. - One-shot logic from the palette → a
runScriptcommand, not a hidden tab. Itsmuxy.*calls are synchronous (return values directly — noawait). It hastabs/panes/projects/worktrees/browser/agents/files/git/exec/dialog/modal/topbar/statusbar/notifications, but nothttp,events,remote,panels, orpopover. It can open a modal and act on the choice inline — no page or background listener needed.
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.
- 10d ago First seen · 124 lines · 77 tokens per session scan A c4ad9c5e03c2
muxy-extension is a skill published in the GitHub repository tofunori/atelier-studio (2 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 5,887 once invoked, about $0.0004 per session on Opus 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-08-31.
Other skills, from other repositories
frame-liquid-bg-hero
A design template for a fluid, colorful background with large overlaid text, suitable for a video opening, website landing-page hero, or poster. It offers CSS, canvas, or WebGL approaches, with a static fallback for reduced motion or simpler use.
frame-flowchart-sticky
A single-file HTML template for showing a process or system as a whiteboard with coloured sticky notes, curved arrows, and optional mouse interactions.
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
motion-frames
A collection of looping CSS animation patterns for a webpage hero section, the prominent visual area at the top of a page. It combines rotating text, an animated globe or geometric shape, a timer, and floating labels.
saas-landing
A single-page SaaS landing page for a software product, with sections such as the hero, features, customer proof, pricing, FAQs, and a call to action. SaaS means software delivered online, usually by subscription.
waitlist-page
A simple waitlist page for collecting email addresses from people interested in a new product or early-access release.