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.
npx agentmods add mcp/patrizzos/stylesafe/stylesafegit clone --depth 1 https://github.com/Patrizzos/StyleSafeWrote 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/mcp/patrizzos/stylesafe/stylesafe)<a href="https://agentmods.dev/mcp/patrizzos/stylesafe/stylesafe"><img src="https://agentmods.dev/badge/mcp/patrizzos/stylesafe/stylesafe.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
stylesafe 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 3d 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
{
"stylesafe": {
"command": "npx",
"args": [
"-y",
"@patrizzos/stylesafe"
],
"env": {}
}
}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.
- 3d ago First seen · 10 lines scan A 3535a247913a
stylesafe is an MCP server published in the GitHub repository Patrizzos/StyleSafe (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
igniteui-theming
A set of Sass variables, mixins, and functions for generating palettes, typography, and elevations used by Ignite UI components. Runs locally from the igniteui-theming npm package.
igniteui-theming
Generate Sass palettes, typography, elevations, and themes for Ignite UI components. Runs locally from the igniteui-theming npm package.
raven-mcp
An MCP server for coding agents — click any element in your locally running app, say what should change, and get back the selector, computed styles, and design tokens, plus an audit of the result. Runs locally from the raven-mcp npm package.
css-sota-mcp
What CSS you can actually ship today, from live Baseline data and MDN browser-compat-data. Remote server at css-sota-mcp.lusrodri.workers.dev.
layout-doctor-mcp
MCP server "layout-doctor-mcp" as configured in h-kazuki-pixel/layout-doctor-mcp. Runs locally from the layout-doctor-mcp npm package.
motionprompts-mcp
MCP server over a catalog of 236 production-grade GSAP motion components: search by design brief, plan a page's information architecture, and fetch copy-pasteable build prompts. Runs locally from the motionprompts-mcp npm package.