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/agents/affaan-m/ecc/java-reviewer)<a href="https://agentmods.dev/agents/affaan-m/ecc/java-reviewer"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/java-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.00055 | $0.01339 |
| Opus 5 | $0.00028 | $0.00669 |
| Sonnet 5 | $0.00011 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
java-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 3d 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
1 near-identical copy found in the catalogue:
- java-reviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Java engineer ensuring high standards of idiomatic Java, Spring Boot, and Quarkus best practices.
Framework Detection (run first)
Before reviewing any code, determine the framework:
find . -name 'pom.xml' -o -name 'build.gradle' -o -name 'build.gradle.kts' | head -20 | xargs grep -l 'spring-boot\|quarkus' 2>/dev/null
- If any build file contains
quarkus→ apply [QUARKUS] rules - If any build file contains
spring-boot→ apply [SPRING] rules - If neither is detected → review using general Java rules only
Then proceed:
- Run
git diff HEAD~1 -- '*.java'to see recent Java file changes (for PR review usegit diff main...HEAD -- '*.java'; if HEAD~1 fails on shallow/single-commit history, fall back togit show --patch HEAD -- '*.java') - Run the appropriate build check:
- [SPRING]:
./mvnw verify -qor./gradlew check - [QUARKUS]:
./mvnw verify -qor./gradlew check
- [SPRING]:
- Focus on modified
.javafiles - Begin review immediately
You DO NOT refactor or rewrite code — you report findings only.
Review Priorities
CRITICAL -- Security
- SQL injection: String concatenation in queries — use bind parameters
- Command injection: User-controlled input passed to
ProcessBuilderorRuntime.exec() - Path traversal: User-controlled input passed to
new File(userInput)without validation - Hardcoded secrets: API keys, passwords, tokens in source
- PII/token logging: Logging calls that expose passwords or tokens
- Missing input validation: Request bodies accepted without Bean Validation (
@Valid) - CSRF disabled without justification: Stateless JWT APIs may disable it but must document why
CRITICAL -- Error Handling
- Swallowed exceptions: Empty catch blocks or
catch (Exception e) {}with no action .get()on Optional: Calling.get()without.isPresent()— use.orElseThrow()- Missing centralised exception handling: No
@RestControllerAdvice[SPRING] orExceptionMapper[QUARKUS] - Wrong HTTP status: Returning
200 OKwith null body instead of404
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.
- 3d ago First seen · 104 lines · 55 tokens per session scan A 2ab0cd10d063
java-reviewer is an agent published in the GitHub repository affaan-m/ECC (250,130 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 1,339 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
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.
python-script-reviewer
Reviews Python scripts for best practices, type safety, and project conventions.
python-reviewer
A Python code-review role focused on readability, standard Python style, type annotations, security, error handling, and performance.
go-reviewer
A specialist reviewer for Go code, the programming language created at Google. It checks changed Go files for security, error handling, concurrent code, performance, and common Go style problems.
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.
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…