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/ruchernchong/claude-kitWrote 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/ruchernchong/claude-kit/next-devtools)<a href="https://agentmods.dev/mcp/ruchernchong/claude-kit/next-devtools"><img src="https://agentmods.dev/badge/mcp/ruchernchong/claude-kit/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/ruchernchong/claude-kit/next-devtools"><img src="https://agentmods.dev/badge/mcp/ruchernchong/claude-kit/next-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 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.
This is a copy
100% identical to next-devtools — 0 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": "bunx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. 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.
- 1mo ago First seen · 9 lines scan A c1e8f646cdfe
next-devtools is an MCP server published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 5mo 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. It is 100% identical to next-devtools, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
open-design
MCP stdio server bridging coding agents to Open Design daemon (BYOK flow with full systemPrompt fidelity). Runs locally from the open-design-mcp npm package. Needs 1 environment variable to run.
engram
Your local, private memory layer. Index your notes and files, then recall anything with citations and temporal reasoning — 100% on your machine. Runs locally from the @jnmetacode/engram npm package.
job-seeker
An utility downloader for a job search at seek.com.au. Runs locally from the job-seeker Python package.
capsule
Compact, source-linked context packs that reduce token waste for coding agents. Runs locally from the capsulectx npm package.
memorylane
Agent-native memory layer — persistent context, semantic recall, session history, SDK, CLI, API, and MCP for AI agents and developers. Runs locally from the @talocode/memorylane npm package.
cognis-toolguard
MCP server "cognis-toolguard" as configured in cognis-digital/toolguard. Runs locally from the cognis-toolguard Python package.