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/M00N7682/imugiWrote 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/m00n7682/imugi/imugi-ai)<a href="https://agentmods.dev/mcp/m00n7682/imugi/imugi-ai"><img src="https://agentmods.dev/badge/mcp/m00n7682/imugi/imugi-ai/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/m00n7682/imugi/imugi-ai"><img src="https://agentmods.dev/badge/mcp/m00n7682/imugi/imugi-ai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
imugi-ai 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
{ "imugi-ai": { "command": "npx", "args": [ "-y", "imugi-ai" ] } }
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 · 9 lines scan A 4a890654d4bc
imugi-ai is an MCP server published in the GitHub repository M00N7682/imugi (11 stars, last pushed 7mo 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
threejs-devtools
Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent. Runs locally from the threejs-devtools-mcp npm package. Needs 5 environment variables to run.
plumb-mcp
Figma → code MCP: no rate limits, no metered quotas, verification loop. Works on every Figma plan. Runs locally from the plumb-mcp npm package. Needs 2 environment variables to run.
figbridge
Free, local MCP bridge for Figma — HTML, CSS, Tailwind, tokens, agent handoff bundles. Runs locally from the figbridge-mcp npm package. Needs 1 environment variable to run.
mcp
MCP server for WCAG accessibility and color-contrast audits plus QA issue tracking in Claude Code, Cursor, and Windsurf. Runs locally from the @overlayqa/mcp npm package.
canicode
Analyze Figma designs for dev & AI readiness. 39 rules, scoring, HTML reports. Runs locally from the canicode npm package. Needs 1 environment variable to run.
uxloom
Agent-native UI/UX design validation: journey completeness, state coverage, and WCAG checks. Runs locally from the uxloom npm package. Needs 1 environment variable to run.