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/nguyenthienthanh/aura-frog/figmagit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/nguyenthienthanh/aura-frog/figma)<a href="https://agentmods.dev/mcp/nguyenthienthanh/aura-frog/figma"><img src="https://agentmods.dev/badge/mcp/nguyenthienthanh/aura-frog/figma.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
figma 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 5d 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.
This is a copy
86% identical to figma — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"figma": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp",
"--stdio"
],
"env": {
"FIGMA_API_KEY": "${FIGMA_API_TOKEN}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 5d ago First seen · 13 lines scan A 6034843152c2
figma is an MCP server published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed yesterday), 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. It is 86% identical to figma, differing in 2 lines, and is treated as a copy.
Other mcp servers, from other repositories
rigour
Quality gates for AI agents. Lint, test, build checks with memory persistence. Runs locally from the @rigour-labs/mcp npm package.
memory-journal-mcp
MCP server "memory-journal-mcp" as configured in neverinfamous/memory-journal-mcp. Runs in Docker (docker.io/writenotenow/memory-journal-mcp:v1.1.3).
neverinfamous-memory-journal-mcp
A MCP server built for developers enabling Git based project management with project and personal… Remote server at server.smithery.ai.
athena-protocol
AI tech lead for coding agents with validation and impact analysis. Runs locally from the @n0zer0d4y/athena-protocol npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.