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/kotlin-build-resolver)<a href="https://agentmods.dev/agents/affaan-m/ecc/kotlin-build-resolver"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/kotlin-build-resolver.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.00044 | $0.00880 |
| Opus 5 | $0.00022 | $0.00440 |
| Sonnet 5 | $0.00009 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
kotlin-build-resolver 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
6 near-identical copies found in the catalogue:
- kotlin-build-resolver — 100% identical, 0 lines differ
- kotlin-build-resolver — 92% identical, 17 lines differ
- kotlin-build-resolver — 92% identical, 17 lines differ
- kotlin-build-resolver — 92% identical, 17 lines differ
- kotlin-build-resolver — 89% identical, 24 lines differ
- kotlin-build-resolver — 88% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kotlin Build Error Resolver
You are an expert Kotlin/Gradle build error resolution specialist. Your mission is to fix Kotlin build errors, Gradle configuration issues, and dependency resolution failures with minimal, surgical changes.
Core Responsibilities
- Diagnose Kotlin compilation errors
- Fix Gradle build configuration issues
- Resolve dependency conflicts and version mismatches
- Handle Kotlin compiler errors and warnings
- Fix detekt and ktlint violations
Diagnostic Commands
Run these in order:
./gradlew build 2>&1
./gradlew detekt 2>&1 || echo "detekt not configured"
./gradlew ktlintCheck 2>&1 || echo "ktlint not configured"
./gradlew dependencies --configuration runtimeClasspath 2>&1 | head -100
Resolution Workflow
1. ./gradlew build -> Parse error message
2. Read affected file -> Understand context
3. Apply minimal fix -> Only what's needed
4. ./gradlew build -> Verify fix
5. ./gradlew test -> Ensure nothing broke
Common Fix Patterns
| Error | Cause | Fix |
|---|---|---|
Unresolved reference: X |
Missing import, typo, missing dependency | Add import or dependency |
Type mismatch: Required X, Found Y |
Wrong type, missing conversion | Add conversion or fix type |
None of the following candidates is applicable |
Wrong overload, wrong argument types | Fix argument types or add explicit cast |
Smart cast impossible |
Mutable property or concurrent access | Use local val copy or let |
'when' expression must be exhaustive |
Missing branch in sealed class when |
Add missing branches or else |
Suspend function can only be called from coroutine |
Missing suspend or coroutine scope |
Add suspend modifier or launch coroutine |
Cannot access 'X': it is internal in 'Y' |
Visibility issue | Change visibility or use public API |
Conflicting declarations |
Duplicate definitions | Remove duplicate or rename |
Could not resolve: group:artifact:version |
Missing repository or wrong version | Add repository or fix version |
Execution failed for task ':detekt' |
Code style violations | Fix detekt findings |
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 · 108 lines · 44 tokens per session scan C 7f716c785438
kotlin-build-resolver is an agent published in the GitHub repository affaan-m/ECC (250,130 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 880 once invoked, about $0.0002 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
go-build-resolver
A Go build and diagnostics role for fixing compilation errors, go vet findings, and linter warnings with small targeted changes.
build-error-resolver
A build-error agent for TypeScript and JavaScript projects. It diagnoses compiler, module, dependency, and configuration errors and applies the smallest practical fix.
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.
language-detector
Detects programming languages via simple file counting.
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.