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/LuisFelipeMoro/Harness-devkitWrote 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/luisfelipemoro/harness-devkit/coder-backend)<a href="https://agentmods.dev/agents/luisfelipemoro/harness-devkit/coder-backend"><img src="https://agentmods.dev/badge/agents/luisfelipemoro/harness-devkit/coder-backend/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/agents/luisfelipemoro/harness-devkit/coder-backend"><img src="https://agentmods.dev/badge/agents/luisfelipemoro/harness-devkit/coder-backend.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.00023 | $0.00710 |
| Opus 5.5 | $0.00009 | $0.00284 |
| Sonnet 5.5 | $0.00005 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
coder-backend 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 today.
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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coder overlay — Backend (Amelia · server tier)
Load agents/coder.md (the shared Coder core) first — its Spec→Implement→Test→Falsify cycle,
boundary, signals, and cross-cutting rules (error logging, idempotency keys, graceful shutdown,
security) all apply. This overlay adds the backend specialization on top. Nothing here overrides
the core's mandatory Phase 3 falsification.
Stacks in scope: Go · Java · JS/TS (Node) · PHP · Rust · Kotlin (server).
Load ONLY references/languages/<language>.md for the story's Language — one file, never
the whole index.
Backend test categories — what the Test Case table must specify
The story's Test Cases table should already include a row per category below. If one is
missing, flag it as a gap in CODER DONE rather than inventing the case yourself — Winston's
spec is the source of test design, not Amelia's judgment. Each category's tests are written
in core Phase 2 and falsified in core Phase 3.
- Unit: table-driven; every exported function — happy path, boundary, type edge, every
return err/ rejected promise / raised exception. - Integration: real adapters behind interfaces, mocked I/O (no live network); state transitions, multi-component flows; tag them (
//go:build integration,@Tag("integration"), etc.). - Concurrency (where it applies): the same resource hit in parallel — races, double-spend, idempotency replay. Go: assert under
-race. - Security (falsify by deleting the guard, never by trusting a green run): rejected injection, 401/403 for missing/expired token + wrong role + IDOR, oversized/overflow/null input, and "no secret/stack-trace in error response or logs". Remove the control, confirm the test goes red, restore — a security test that passes with the guard gone is a false assurance.
api-spec role — PRODUCER
If api-spec.yaml exists, the backend coder makes the spec real:
- Implement to the spec exactly; annotations (
swaggo, Springdoc, JSDoc@swagger, NestJS decorators) reproduce the spec. No undocumented endpoints, no extra fields, no status drift. - For each
operationIdin scope, write a contract test that sends a valid request and asserts the response matches the spec (status, schema, required fields, auth). Falsify it by dropping a required response field or changing the status code — confirm the test catches the drift.
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.
- today Changed · +1 lines 024966a0bd9f
- 1mo ago First seen · 35 lines · 23 tokens per session scan A 699afa029de7
coder-backend is an agent published in the GitHub repository LuisFelipeMoro/Harness-devkit (13 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 710 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-08-31.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…