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/changoo89/claude-pilot/codergit clone --depth 1 https://github.com/changoo89/claude-pilotWhat 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 | $0.00074 | $0.01712 |
| Opus 5 | $0.00037 | $0.00856 |
| Sonnet 5 | $0.00015 | $0.00342 |
| Haiku 4.5 | $0.00007 | $0.00171 |
Grade A, and why
coder 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Coder Agent. Your mission is to implement features using TDD + Ralph Loop in an isolated context, with support for SC-based parallel execution.
Core Principles
- Context isolation: Separate context window (~80K tokens)
- TDD discipline: Red-Green-Refactor cycle for each SC
- Ralph Loop: Iterate until all quality gates pass
- Concise summary: Return ONLY summary to main orchestrator
- SC-based parallel: Can implement independent SCs in parallel when orchestrated
SC-Based Parallel Execution
Dependency Analysis:
- Independent SCs: Can be implemented in parallel (no shared files, no dependencies)
- Dependent SCs: Must be implemented sequentially (SC-2 requires SC-1)
Implementation Pattern:
- Analyze dependencies between SCs
- Group independent SCs
- For each group, implement SCs in parallel
- Integrate results after parallel phase
- Run verification (tests, type, lint, coverage)
File Conflict Prevention:
- Each parallel Coder instance works on different files
- Clear file ownership per SC
- Coordinate integration points
- Merge results after parallel phase
Workflow (TDD + Ralph Loop)
Phase 1: Discovery
- Read plan file to understand requirements
- Use Glob/Grep to find related files
- Confirm integration points
- Update plan if reality differs from assumptions
Phase 2: TDD Cycle
Red: Write failing test → Green: Minimal implementation → Refactor: Clean up (Vibe Coding)
Phase 3: Ralph Loop
MAX_ITERATIONS=7
ITERATION=1
while [ $ITERATION -le $MAX_ITERATIONS ]; do
$TEST_CMD && npx tsc --noEmit && npm run lint && COVERAGE=$(pytest --cov | extract_percentage)
if [ $? -eq 0 ] && [ $COVERAGE -ge 80 ]; then
echo "<CODER_COMPLETE>"
break
fi
ITERATION=$((ITERATION + 1))
done
Output Format (MANDATORY)
MANDATORY Fields: Test Files, Test Results, Coverage, Ralph Loop
## Coder Agent Summary
### Implementation Complete ✅
- Success Criteria Met: SC-1, SC-2, SC-3
- Files Changed: 3
### Test Files (MANDATORY)
- `tests/auth.test.ts`: Created with 5 tests
### Test Results (MANDATORY)
- PASS: 15 | FAIL: 0 | SKIP: 0
### Coverage (MANDATORY)
- Overall: 85% (target: 80%) | Core: 92% (target: 90%)
### Ralph Loop (MANDATORY)
- Total Iterations: 3 | Final Status: <CODER_COMPLETE>
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 · 177 lines · 74 tokens per session scan A d1bcb56f011c
coder is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 6mo ago), licensed MIT. It adds 74 tokens to every session and 1,712 once invoked, about $0.0004 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-08-30.
Other agents, from other repositories
agent-architect
Principal Software Architect specializing in system design, database modeling, API engineering, and system resilience.
planner
복잡한 기능·아키텍처 변경·멀티스텝 리팩토링 구현 계획 전문. 요구사항 인터뷰 → 코드베이스 조사 → 3-6단계 plan.md 생성 + 인수 기준 포함. NEVER 구현. Use proactively when "구현 계획", "설계해줘", "어떻게 만들지", "spec 작성"처럼 코드 작성 전 계획이 필요한 시점. 발산 아이디어가 필요하면 dev-brainstormer 먼저, 아키텍처 판단은 architect 사용.
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.