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/plugins/mahmoudilyan/marmoui/marmo-ui)<a href="https://agentmods.dev/plugins/mahmoudilyan/marmoui/marmo-ui"><img src="https://agentmods.dev/badge/plugins/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/plugins/mahmoudilyan/marmoui/marmo-ui"><img src="https://agentmods.dev/badge/plugins/mahmoudilyan/marmoui/marmo-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "marmo-ui",
"description": "MCP-backed workflow for building UI with @marmoui/ui. Bundles the marmo-ui skill, /marmo-ui:* commands, and the Marmo MCP server so agents read real component props instead of guessing. Works free without a token; add your Pro token for on-brand generation.",
"author": {
"name": "Marmo UI Team",
"email": "[email protected]"
},
"homepage": "https://github.com/mahmoudilyan/marmoui",
"repository": "https://github.com/mahmoudilyan/marmoui",
"license": "MIT",
"keywords": [
"marmo",
"design-system",
"ui",
"mcp"
],
"userConfig": {
"marmo_mcp_token": {
"type": "string",
"title": "Marmo token (optional \u2014 leave empty to start free)",
"description": "Three tiers: EMPTY = anonymous (full component knowledge, ~100 calls/day) \u00b7 FREE account token = no daily limit (marmoui.com/connect, no card) \u00b7 PRO token = your brand drives generation + composition patterns (marmoui.com/pricing). You can also sign in later via /mcp \u2192 marmo-ui \u2192 Authenticate.",
"required": false,
"default": ""
},
"mcp_url": {
"type": "string",
"title": "Marmo MCP URL (leave default)",
"description": "Override the MCP server URL. Leave the default unless running the MCP locally.",
"default": "https://mcp.marmoui.com/mcp"
}
}
}
What it installs
The manifest is a name and a version. 2 skills, 5 commands, 1 hook travel with it, and installing the plugin installs all of them — 441 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 34 lines scan A 21edb9d4c7b7
marmo-ui is a plugin published in the GitHub repository mahmoudilyan/marmoui (39 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
interaction-design
Design meaningful interactions with micro-animations, state machines, gestures, error handling, and feedback patterns.
s2-docs
Spectrum 2 component documentation on-demand. Fetches S2 design guidelines, component options, and usage patterns without loading a persistent MCP server.
saglitzdesign
Design knowledge and a ship-quality gate for coding agents: 96 knowledge documents, 36 tools, 10 of them auditors that publish what they could not see, and 9 workflows.
fluid
6 skills, 108 palettes, 53 styles, 14 layouts, a 29-rule detector, and one house motion language. The opposite of generic AI slop.
uisandbox
Play with your app's design, right in the browser: open a built web app in UISandbox, 1:1 and with its own knobs, from the chat; try a change, verify, export the patch. Bundles the /uisandbox skill and the uisandbox MCP server.
swiftui-native-component-design
A design process and ready-to-adapt Swift templates for building custom SwiftUI components that feel native — initializer shape, data flow, and ButtonStyle-like customization APIs.