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.
git clone --depth 1 https://github.com/mahmoudilyan/marmouiWrote 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/commands/mahmoudilyan/marmoui/override)<a href="https://agentmods.dev/commands/mahmoudilyan/marmoui/override"><img src="https://agentmods.dev/badge/commands/mahmoudilyan/marmoui/override/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/commands/mahmoudilyan/marmoui/override"><img src="https://agentmods.dev/badge/commands/mahmoudilyan/marmoui/override.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.00056 | $0.01251 |
| Opus 5 | $0.00028 | $0.00626 |
| Sonnet 5 | $0.00011 | $0.00250 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
override 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/marmo-ui:override
Let this app customize the design system without forking it. All app code imports UI from a local wrapper folder (src/ui/, aliased as @/ui) that re-exports everything from @marmoui/ui; overriding a component means dropping a file in that folder and shadowing the package export. New app-specific components live in the same folder.
Two modes, inferred from the request:
/marmo-ui:override DataTable— override an existing@marmoui/uicomponent./marmo-ui:override new InvoiceCard(or any request that names a component the MCP doesn't know) — create a new custom component in the ui folder.
Follow the marmo-ui skill's MCP workflow throughout — get_knowledge_version + get_design_guidelines once per session, get_component_info for every @marmoui/ui primitive you touch, review_generated_code on the final output.
Step 1 — Ensure the wrapper exists (first run only)
Check for src/ui/index.ts (also accept src/components/ui/index.ts or an existing uiImportPath in DESIGN.md). If missing:
-
Resolve the import alias from
tsconfig.jsoncompilerOptions.paths(usually@/*→./src/*). If no alias exists, add"@/*": ["./src/*"]. -
Create
src/ui/index.ts:// App UI entry point. Import all UI from '@/ui', never from '@marmoui/ui' directly. export * from '@marmoui/ui'; // Local overrides — explicit exports below shadow the package's star export. // export { DataTable } from './data-table'; -
Record the path in
DESIGN.mdfrontmatter so every agent knows the convention:uiImportPath: "@/ui". Create a minimalDESIGN.mdvia/marmo-ui:initfirst if none exists and the user agrees; otherwise just add the key. -
Offer (don't do silently) to migrate existing imports: replace
from '@marmoui/ui'withfrom '@/ui'acrosssrc/(excludingsrc/ui/itself, which is the only place allowed to import the package).
ESM guarantees the shadowing: an explicit named export always wins over a name arriving via export *, so re-exporting DataTable from ./data-table overrides the package's version everywhere the app imports @/ui.
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 · 71 lines · 56 tokens per session scan A a34cd3c8e02d
override is a command published in the GitHub repository mahmoudilyan/marmoui (41 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,251 once invoked, about $0.0003 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 commands, from other repositories
design-screen
Design a complete screen layout from a description or requirements.
responsive-audit
Audit a design's responsive behaviour across breakpoints — layout, touch targets, and content reflow.
seed-create-component
A command for creating a new SEED Design component, including its source specification, recipes, React implementation, documentation, examples, and optional headless layer.
ux-copy
Microcopy review and rewrite against the voice rubric. Produces a before/after table with severity per string and a clean rewrite block. Triggers on "review the copy", "fix the microcopy", "the error messages are bad", or "rewrite this". Use when reviewing or rewriting microcopy, fixing error messages that sound like…
ux-fix
Opt-in fix loop. Reads the latest report from .ux/, validates working tree, and applies findings as atomic commits via the right sub-agents. Triggers on "fix the findings", "apply the fixes", or "run the fix loop". Use when applying findings from a previous audit / copy / a11y / motion / polish report, the user says…
ux-motion
Animation and motion rubric. Checks timing, easing, meaning, reduced-motion compliance, and performance for every animation on a surface. Triggers on "motion check", "are the animations good", or "fix the motion". Use when auditing motion or animations, checking durations / easing / reduced-motion / performance, is…