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/yojahny55/claude-wp-builderWrote 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/yojahny55/claude-wp-builder/wp-design-library)<a href="https://agentmods.dev/mcp/yojahny55/claude-wp-builder/wp-design-library"><img src="https://agentmods.dev/badge/mcp/yojahny55/claude-wp-builder/wp-design-library/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/mcp/yojahny55/claude-wp-builder/wp-design-library"><img src="https://agentmods.dev/badge/mcp/yojahny55/claude-wp-builder/wp-design-library.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wp-design-library 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 13d 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
{
"wp-design-library": {
"command": "npx",
"args": [
"-y",
"--allow-scripts=better-sqlite3",
"@yojahny/wp-design-library@^1.0.0",
"serve"
]
}
}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.
- 13d ago Changed · +1 lines c4fcb31da5e8
- 1mo ago Changed 4189fd9fb039
- 1mo ago First seen · 10 lines scan A ef7a0af441a2
wp-design-library is an MCP server published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), 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-09-16.
Other mcp servers, from other repositories
ui-ux-suite
UI/UX design audit tool for Claude Code. Scores projects across 12 dimensions: color contrast, typography, accessibility, layout, and more. WCAG 2.2, APCA, and OKLCH color science. Zero dependencies. Runs locally from the ui-ux-suite npm package.
ds4ai
DS4AI MCP server: serves the Design Suite for AI as callable tools, audit a surface across the invisible-correctness axes, and generate head metadata, delivery markup, and palettes, plus the family manifest, agent-instruction, and standard as resources. Runs locally from the @polymathie/ds4ai npm package.
shadcn
Add components to your apps. Runs locally from the shadcn npm package.
accessibility
MCP server "accessibility" as configured in deepakkamboj/claude-marketplace. Runs ${CLAUDE_PLUGIN_ROOT}/mcp-server/dist/index.js with node.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.