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 mahmoudilyan/marmoui --skill marmo-uigit 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/skills/mahmoudilyan/marmoui/marmo-ui)<a href="https://agentmods.dev/skills/mahmoudilyan/marmoui/marmo-ui"><img src="https://agentmods.dev/badge/skills/mahmoudilyan/marmoui/marmo-ui/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/mahmoudilyan/marmoui/marmo-ui"><img src="https://agentmods.dev/badge/skills/mahmoudilyan/marmoui/marmo-ui.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.00134 | $0.02083 |
| Opus 5 | $0.00067 | $0.01042 |
| Sonnet 5 | $0.00027 | $0.00417 |
| Haiku 4.5 | $0.00013 | $0.00208 |
Grade A, and why
marmo-ui 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 11d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marmo UI workflow
You are working on a Marmo product app that consumes @marmoui/ui, Marmo's internal design system. The marmo-ui MCP server (auto-started by this plugin) is the source of truth — every prop, variant, and pattern. Never guess. Always look it up.
If the marmo-ui MCP tools aren't available (calls to mcp__marmo-ui__* fail with "tool not found"), stop and tell the user to run /plugin and confirm marmo-ui is enabled. If the token is wrong (401 Unauthorized on any tool call), tell them to disable and reinstall the plugin (/plugin uninstall marmo-ui@marmoui-plugins then /plugin install marmo-ui@marmoui-plugins) — Claude Code will re-prompt for marmo_mcp_token. Don't fall back to writing components from memory.
Required steps (in order)
1. Verify the MCP is fresh
mcp__marmo-ui__get_knowledge_version
Logs the gitSha, indexedAt, componentCount, and patternCount. Confirms you're talking to a healthy MCP. If it errors, surface the error to the user — don't silently fall back to guessing.
2. Read the rules (once per session)
mcp__marmo-ui__get_design_guidelines iconLibrary="<library>"
Returns import rules, color tokens, icon conventions, and the mandatory generation checklist. Skim it. The hard rules below are a summary.
Icon library selection (do this before writing any UI code): Ask the user which icon library they want. Default (no preference): Phosphor (phosphor). Supported: phosphor, material (react-icons/md), lucide, tabler, heroicons, feather. Pass the chosen iconLibrary to get_design_guidelines AND to review_generated_code — the validator rejects icons imported from any other library as errors. Don't mix libraries within one project.
3. Find the right primitive
If the task is a known multi-component layout (full app shell, data-table-with-filters, confirmation-dialog, dialogs-for-other-actions, form-with-validation, posthog-tracking):
mcp__marmo-ui__get_pattern patternId="<the-pattern>"
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.
- 11d ago First seen · 101 lines · 134 tokens per session scan A ffaf30bd07fd
marmo-ui is a skill published in the GitHub repository mahmoudilyan/marmoui (41 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 2,083 once invoked, about $0.0007 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
frontend-design
Use this skill when specifying, designing, or documenting UI components, layouts, and design systems for frontend implementation. Trigger phrases: 'design this UI component', 'create a responsive layout', 'spec the CSS for', 'design system for'. Do NOT use for backend development, server-side logic, data engineering…
create-db-component
Creates a new DB UX Design System component with Mitosis source, SCSS, typed model, and Playwright tests.
modify-db-component
Modifies an existing DB UX Design System Mitosis component (add variants, update props, change styles).
implement-component
Implements production-ready UI using DB UX Design System v3 components, tokens, and icons with a discovery-first approach.
migrate-to-v3
Migrates legacy DB UI v2 code (cmp-, elm-, rea- classes, Web Components, db-color- tokens) to DB UX Design System v3.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for…