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/kyopark2014/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/kyopark2014/agent-plugins/frontend-design)<a href="https://agentmods.dev/plugins/kyopark2014/agent-plugins/frontend-design"><img src="https://agentmods.dev/badge/plugins/kyopark2014/agent-plugins/frontend-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/kyopark2014/agent-plugins/frontend-design"><img src="https://agentmods.dev/badge/plugins/kyopark2014/agent-plugins/frontend-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
frontend-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 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.
This is a copy
100% identical to frontend-design — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "frontend-design",
"description": "Frontend design skill for UI/UX implementation",
"author": {
"name": "Anthropic",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 43 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 · 9 lines scan A fd9a7db11f5d
frontend-design is a plugin published in the GitHub repository kyopark2014/agent-plugins (4 stars, last pushed 12d 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. It is 100% identical to frontend-design, differing in 0 lines, and is treated as a copy.
Other plugins, from other repositories
proplasma
See what taking each candidate direction means for your purpose and on what ground, then settle the one you take — /preview (πρόπλασμα: a preliminary clay model).
spacing-skill
Anti-cramped spacing skill for AI-generated UI — three dials, one spacing scale, vertical rhythm, optical alignment, accessibility floors, and density discipline.
spacing-skill
Anti-cramped spacing skill for AI-generated UI — one spacing scale, vertical rhythm, optical alignment, and density discipline.
zilliz
Manage Zilliz Cloud clusters and Milvus vector databases from Claude Code using the zilliz-cli.
show-me
Visual context sharing between AI and users - display files/URLs/commands with 'show-me', observe screen context with 'look-at'.
travel-planner
A travel-planning plugin that researches trip information, keeps sources traceable, applies 16 scheduling rules, and checks the final output.