ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.
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/affaan-m/ECCWrote 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/affaan-m/ecc/chrome-devtools)<a href="https://agentmods.dev/mcp/affaan-m/ecc/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/affaan-m/ecc/chrome-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/affaan-m/ecc/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/affaan-m/ecc/chrome-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
chrome-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.
Copies of this mod
8 near-identical copies found in the catalogue:
- chrome-devtools — 100% identical, 0 lines differ
- chrome-devtools — 100% identical, 0 lines differ
- chrome-devtools — 100% identical, 0 lines differ
- chrome-devtools — 100% identical, 0 lines differ
- chrome-devtools — 100% identical, 0 lines differ
- chrome-devtools — 100% identical, 0 lines differ
- chrome-devtools — 100% identical, 1 lines differ
- chrome-devtools — 100% identical, 0 lines differ
What it actually says
{
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}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 4f096813cf17
chrome-devtools is an MCP server published in the GitHub repository affaan-m/ECC (284,130 stars, last pushed today), 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-09-03.
Other mcp servers, from other repositories
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
mintlify-docs
MCP server "mintlify-docs", hosted remotely at www.mintlify.com, as configured in nottelabs/notte.
notte-docs
MCP server "notte-docs", hosted remotely at docs.notte.cc, as configured in nottelabs/notte.
devharness
MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions. Runs locally from the devharness npm package.
webfetch
MCP server "webfetch" as configured in firish/webfetch. Runs locally from the webfetch-llm@latest Python package.