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/6529-Collections/6529seize-frontendWrote 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/6529-collections/6529seize-frontend/next-devtools)<a href="https://agentmods.dev/mcp/6529-collections/6529seize-frontend/next-devtools"><img src="https://agentmods.dev/badge/mcp/6529-collections/6529seize-frontend/next-devtools/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/6529-collections/6529seize-frontend/next-devtools"><img src="https://agentmods.dev/badge/mcp/6529-collections/6529seize-frontend/next-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
next-devtools 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 6d 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
100% identical to next-devtools — 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
{
"next-devtools": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}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.
- 6d ago Changed 1876a2cc7cc8
- 2mo ago First seen · 9 lines scan A c81a8ba90c8a
next-devtools is an MCP server published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed yesterday), licensed Apache-2.0. 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 100% identical to next-devtools, differing in 2 lines, and is treated as a copy.
next-devtools compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| next-devtools6529-Collections/6529seize-frontend | MCP server | 10 | yesterday | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcp-serverIgniteUI/igniteui-cli | MCP server | 137 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| storybook-mcpyannbf/mealdrop | MCP server | 248 | 1mo ago | none | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| figma-dev-toolsqq1006492122/figma-dev-tools | MCP server | 1 | 24d ago | none | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| next-devtoolssherpa-sh/Sherpa-Action | MCP server | 22 | 9mo ago | Apache-2.0 | A | — | Claude Code |
| docs-langchainlangchain-ai/langchain | MCP server | 149k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| component-explorermicrosoft/vscode | MCP server | 195k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |