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/css-plugin)<a href="https://agentmods.dev/plugins/laurigates/claude-plugins/css-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/css-plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
css-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 2d 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": "css-plugin",
"version": "1.2.3",
"description": "CSS tooling - Lightning CSS transpilation/minification, UnoCSS atomic utility generation",
"author": {
"name": "Lauri Gates"
},
"license": "MIT",
"keywords": [
"css",
"lightning-css",
"unocss",
"atomic-css",
"minification",
"transpilation",
"vite"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 81 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.
- 2d ago First seen · 20 lines scan A 10e6fec666aa
css-plugin is a plugin published in the GitHub repository laurigates/claude-plugins (58 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-06.
Other plugins, from other repositories
frontend-developer
Frontend component development with accessibility and responsive design.
color-contrast
Color contrast checking and accessible color suggestions.
css-cleaner
Find unused CSS and consolidate stylesheets.
playgrounds
One-step access to Anthropic's first-party playground plugin: declares the cross-marketplace dependency, routes playground-shaped requests to the upstream skill when it is installed, emits the install commands when it is not, and carries field-tested prompt recipes, cloud-session delivery guidance, and consumer…
motion
Animation work in three modes: audit motion against Disney's 12 principles, add purposeful micro-interactions, or fix animation performance (compositor properties, layout thrashing).
frontend-design
Frontend design skill for UI/UX implementation.