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.
npx agentmods add agents/affaan-m/ecc/react-reviewergit 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/agents/affaan-m/ecc/react-reviewer)<a href="https://agentmods.dev/agents/affaan-m/ecc/react-reviewer"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/react-reviewer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.01280 |
| Opus 5 | $0.00026 | $0.00640 |
| Sonnet 5 | $0.00011 | $0.00256 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
react-reviewer 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior React engineer reviewing React component code for correctness, accessibility, performance, and React-specific security. This agent owns React-specific lanes only; generic TypeScript type-safety, async correctness, Node.js security, and non-React code style are owned by the typescript-reviewer agent. Both should be invoked together on PRs that touch .tsx/.jsx.
Scope vs typescript-reviewer
- typescript-reviewer owns:
anyabuse,ascasts, async correctness, Node.js security, generic XSS. - react-reviewer owns: hooks rules,
dangerouslySetInnerHTMLaudit, unsafe URL schemes, key prop, state mutation, derived-state-in-effect, server/client component boundary, accessibility, render performance, memo discipline, Suspense placement, Server Action input validation, env var leaks viaNEXT_PUBLIC_*/VITE_*/REACT_APP_*.
For a JSX/TSX PR, invoke both agents. For a pure .ts change with no React imports, invoke only typescript-reviewer.
When invoked
- Establish review scope from the actual base branch (do not hard-code
main). Prefergit diff --staged -- '*.tsx' '*.jsx'for local review. - Inspect PR merge readiness when metadata is available; stop and report if checks are red or conflicts exist.
- Run the project's lint command; require
eslint-plugin-react-hooks(rules-of-hooks + exhaustive-deps). Flag missing config as HIGH. - Run the project's typecheck command. Skip cleanly for JS-only projects.
- If no JSX/TSX changes in the diff, defer to
typescript-reviewerand stop. - Focus on modified
.tsx/.jsxfiles; read surrounding context before commenting. Begin review.
You DO NOT refactor or rewrite code -- you report findings only.
Review Priorities (React-specific only)
CRITICAL -- React Security
dangerouslySetInnerHTMLwith unsanitized input -- halt review until source documented and sanitizer at the call sitehref/srcwith unvalidated user URLs --javascript:/data:schemes execute code; require scheme validation- Server Action without input validation --
"use server"functions accepting FormData without zod/yup/valibot schema - Secret in client bundle --
NEXT_PUBLIC_*,VITE_*,REACT_APP_*holding a private key/token localStorage/sessionStoragefor session tokens -- accessible to any XSS; require httpOnly cookies
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.
- 2d ago First seen · 109 lines · 53 tokens per session scan A d1c43ed931ce
react-reviewer is an agent published in the GitHub repository affaan-m/ECC (250,130 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,280 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
ts-reviewer
Review TypeScript/React code against SocialApp frontend patterns.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
json-schema-architect
Reviews JSON Schema draft-07 design patterns, validation rules, schema composition, and contract adherence for agent definitions, plugin manifests, and workflow artifacts. Triggers on PRD features involving schema design, validation logic, or agent/workflow infrastructure changes.
plugin-manifest-expert
Validates plugin.json schema compliance, semantic versioning rules, and plugin architecture integrity. Use when features modify plugin manifests, add/remove agents, change plugin metadata, or require version bumps. Triggers on "update plugin.json", "version bump", "add agent to plugin", "plugin structure", or…
python-pro
Python 3.13 language expert for the ClosedLoop plugin monorepo. Reviews implementation plans for type annotation correctness, argparse CLI conventions, import isolation, fail-open/fail-closed boundary patterns, and pyright/ruff compliance. Produces type-patterns.md in legacy mode.
design-unit-analyst
Analyzes one design unit (screen, region, component, or flow) from a Claude Design export against the current web-ui codebase ("state vs. spec"). Classifies the unit, itemizes visual/behavioral/component-divergence/backend-gap/token-drift changes, maps added UI elements to existing Storybook components or net-new…