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/Xe/agent-pluginsWrote 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/xe/agent-plugins/xe-design)<a href="https://agentmods.dev/plugins/xe/agent-plugins/xe-design"><img src="https://agentmods.dev/badge/plugins/xe/agent-plugins/xe-design/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/xe/agent-plugins/xe-design"><img src="https://agentmods.dev/badge/plugins/xe/agent-plugins/xe-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
xe-design 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 2mo 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
{
"name": "xe-design",
"description": "Xe's Gruvbox-rooted design system derived from xeiaso.net.",
"author": {
"name": "Xe Iaso",
"email": "[email protected]"
},
"homepage": "https://github.com/Xe/agent-plugins",
"repository": "https://github.com/Xe/agent-plugins",
"license": "MIT",
"keywords": ["design", "ui", "css"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 0 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.
- 2mo ago First seen · 13 lines scan A ff31a963f2ca
xe-design is a plugin published in the GitHub repository Xe/agent-plugins (2 stars, last pushed 3mo 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-31.
Other plugins, from other repositories
frontend-design
Frontend design skill for UI/UX implementation.
aio-visual-diff
Verify AI-built UI against design via measurement-driven diff — extracts computed CSS and bounding boxes through Chrome DevTools MCP, diffs against Figma reference or a frozen baseline, and feeds numerical deltas back to the agent. No screenshot eyeballing.
frontend-design
Astro, frontend design, and web design guidelines skills.
liquid-glass
Apple-style liquid glass: frosted, refracting surfaces for web UI, with the rules that keep them from reading as gray boxes.
shadcn
UI component and design system framework. Search registries, install components as source code, and audit your project.
layout
Serve and enforce your design system in any agent. Bundles the Layout MCP server (design tokens, component specs, compliance checks) and the layout-md skill for writing on-brand UI code.