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 commands/affaan-m/ecc/securitygit 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)<a href="https://agentmods.dev/commands/affaan-m/ecc/security"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/security.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.00004 | $0.00457 |
| Opus 5 | $0.00002 | $0.00229 |
| Sonnet 5 | $0.00001 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
security 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- security — 100% identical, 0 lines differ
- security — 100% identical, 0 lines differ
- security — 100% identical, 0 lines differ
- security — 100% identical, 0 lines differ
- security — 100% identical, 0 lines differ
- security — 100% identical, 0 lines differ
- security — 98% identical, 2 lines differ
- security — 97% identical, 2 lines differ
What it actually says
Security Review Command
Conduct a comprehensive security review: $ARGUMENTS
Your Task
Analyze the specified code for security vulnerabilities following OWASP guidelines and security best practices.
Security Checklist
OWASP Top 10
-
Injection (SQL, NoSQL, OS command, LDAP)
- Check for parameterized queries
- Verify input sanitization
- Review dynamic query construction
-
Broken Authentication
- Password storage (bcrypt, argon2)
- Session management
- Multi-factor authentication
- Password reset flows
-
Sensitive Data Exposure
- Encryption at rest and in transit
- Proper key management
- PII handling
-
XML External Entities (XXE)
- Disable DTD processing
- Input validation for XML
-
Broken Access Control
- Authorization checks on every endpoint
- Role-based access control
- Resource ownership validation
-
Security Misconfiguration
- Default credentials removed
- Error handling doesn't leak info
- Security headers configured
-
Cross-Site Scripting (XSS)
- Output encoding
- Content Security Policy
- Input sanitization
-
Insecure Deserialization
- Validate serialized data
- Implement integrity checks
-
Using Components with Known Vulnerabilities
- Run
npm audit - Check for outdated dependencies
- Run
-
Insufficient Logging & Monitoring
- Security events logged
- No sensitive data in logs
- Alerting configured
Additional Checks
- Secrets in code (API keys, passwords)
- Environment variable handling
- CORS configuration
- Rate limiting
- CSRF protection
- Secure cookie flags
Report Format
Critical Issues
[Issues that must be fixed immediately]
High Priority
[Issues that should be fixed before release]
Recommendations
[Security improvements to consider]
IMPORTANT: Security issues are blockers. Do not proceed until critical issues are resolved.
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 · 90 lines · 4 tokens per session scan A 90c9b198ec81
security is a command published in the GitHub repository affaan-m/ECC (250,130 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 457 once invoked, about $0.0000 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 commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
test
Generate comprehensive tests.
commit
智能生成 Git 提交信息并提交.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.