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/nv-minh/UI-perfectWrote 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/nv-minh/ui-perfect/specgate)<a href="https://agentmods.dev/mcp/nv-minh/ui-perfect/specgate"><img src="https://agentmods.dev/badge/mcp/nv-minh/ui-perfect/specgate/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/nv-minh/ui-perfect/specgate"><img src="https://agentmods.dev/badge/mcp/nv-minh/ui-perfect/specgate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
specgate 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.
What it actually says
{
"specgate": {
"type": "stdio",
"command": "npx",
"args": [
"tsx",
"packages/cli/src/cli.ts",
"mcp"
]
}
}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 · 11 lines scan A 51eefc94f614
specgate is an MCP server published in the GitHub repository nv-minh/UI-perfect (0 stars, last pushed 2mo 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
figwright
MCP server "figwright" as configured in awdr74100/figwright. Runs packages/mcp/dist/index.mjs with node.
playwright
MCP server "playwright" as configured in PMDevSolutions/Aurelius. Launched with cmd /c npx @playwright/mcp@latest --headless.
figma-desktop
MCP server "figma-desktop", hosted remotely at 127.0.0.1, as configured in PMDevSolutions/Aurelius.
figma
MCP server "figma", hosted remotely at mcp.figma.com, as configured in PMDevSolutions/Aurelius.
tidy-core
MCP server "tidy-core" as configured in rominak/tidy-core. Runs locally from the tidy-core npm package.
figma-desktop
MCP server "figma-desktop", hosted remotely at 127.0.0.1, as configured in naver/design-to-ui.