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/laurigates/claude-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/laurigates/claude-plugins/component-patterns-plugin)<a href="https://agentmods.dev/plugins/laurigates/claude-plugins/component-patterns-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/component-patterns-plugin/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/laurigates/claude-plugins/component-patterns-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/component-patterns-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
component-patterns-plugin 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 9d 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": "component-patterns-plugin",
"version": "1.5.1",
"description": "Reusable UI component patterns for implementing common features across different frameworks and tech stacks",
"author": {
"name": "Lauri Gates"
},
"repository": "https://github.com/laurigates/claude-plugins",
"license": "MIT",
"keywords": [
"components",
"ui-patterns",
"version-badge",
"tooltips",
"framework-agnostic",
"react",
"vue",
"svelte",
"nextjs",
"nuxt"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 94 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.
- 9d ago Changed b64f67454c89
- 1mo ago First seen · 24 lines scan A c34ad90cccd1
component-patterns-plugin is a plugin published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), 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-09-03.
Other plugins, from other repositories
dx-devextreme
DevExtreme skills: DataGrid, Scheduler, Form, Chat, Button, SelectBox, DateBox, CheckBox, NumberBox, TextBox, TextArea, DataSource, and Theming for Angular, React, Vue, jQuery, and ASP.NET Core Controls.
component-template-generator
Generates starter component code using design tokens. Creates React/Vue/Svelte components with proper token usage, variants, and accessibility built in.
frontend
Frontend development specialists for React, Vue, Next.js, CSS, HTML, and UI/UX design. Comprehensive coverage of modern frontend technologies.
storefront-next-figma
Figma design-kit skills for Storefront Next verticals — duplicate the kit, sync brand variables, and publish Code Connect. Requires the Figma MCP server.
figma-to-sfnext-pagedesigner
Convert a Figma frame into live Storefront Next Page Designer blocks — React components with decorator metadata, brand-token reconciliation, and product data loaders. Requires the Figma MCP server.
frontend-review
Full frontend review in one pass, combining a design/UX dimension driven by the impeccable, ui-ux-pro-max, and frontend-design upstream skills as hard prerequisites with stop-and-install, with auto-detected code dimensions (React performance, TypeScript type safety, PWA architecture, platform compliance) spawned from…