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/commands/affaan-m/ecc/security-review)<a href="https://agentmods.dev/commands/affaan-m/ecc/security-review"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/security-review/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/commands/affaan-m/ecc/security-review"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/security-review.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00531 |
| Opus 5.5 | $0.00008 | $0.00212 |
| Sonnet 5.5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
security-review 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
Perform a thorough security analysis of the selected code or current branch changes.
Checklist
Secrets & Configuration
- No hardcoded API keys, tokens, passwords, or private keys anywhere in source
- All secrets loaded from environment variables or a secret manager
- Required env vars validated at startup (fail fast if missing)
-
.envfiles excluded from version control
Input Validation & Injection
- All user inputs validated and sanitized before use
- Parameterized queries for every database operation (no string interpolation)
- HTML output escaped or sanitized (XSS prevention)
- File path inputs sanitized (path traversal prevention)
- Command inputs sanitized (command injection prevention)
Authentication & Authorization
- Auth checks enforced server-side — never trust client-supplied user IDs or roles
- Session tokens are sufficiently random and expire appropriately
- Sensitive operations protected by authz checks, not just authn
- CSRF protection enabled for state-changing endpoints
Data Exposure
- Error responses scrubbed of stack traces, internal paths, and sensitive data
- Logs do not contain PII, tokens, or passwords
- Sensitive fields excluded from API responses (no over-fetching)
- Appropriate HTTP security headers set
Dependencies
- No known vulnerable packages (run
npm audit/pip-audit/cargo audit) - Dependency versions pinned or locked
- No unused dependencies that increase attack surface
Infrastructure (if applicable)
- Rate limiting on all public endpoints
- HTTPS enforced; no HTTP fallback in production
- Principle of least privilege for service accounts and IAM roles
Response Protocol
If a CRITICAL issue is found:
- Stop and report immediately.
- Do not ship until fixed.
- Rotate any exposed secrets.
- Scan the rest of the codebase for similar patterns.
Output Format
## Findings
**[CRITICAL|HIGH|MEDIUM|LOW]** — [category]
Location: [file:line if known]
Issue: [what is wrong and why it is dangerous]
Fix: [concrete remediation]
## Summary
- Critical: N
- High: N
- Medium: N
- Safe to ship: yes / no
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 · 71 lines · 19 tokens per session scan A cad3b7159a3d
security-review is a command published in the GitHub repository affaan-m/ECC (290,905 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 531 once invoked, about $0.0001 per session on Opus 5.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-07.
Other commands, from other repositories
caveman-review
Caveman-style code review — one-line findings with severity.
code-review
Code review a pull request.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
review
Review the current diff against project memory.
refactor
Analyze code for SOLID violations and suggest targeted improvements.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.