Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/CodelyTV/agentic_programming-coursenpx agentmods add agents/codelytv/agentic_programming-course/backend-engineerWrote 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/codelytv/agentic_programming-course/backend-engineer)<a href="https://agentmods.dev/agents/codelytv/agentic_programming-course/backend-engineer"><img src="https://agentmods.dev/badge/agents/codelytv/agentic_programming-course/backend-engineer/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/codelytv/agentic_programming-course/backend-engineer"><img src="https://agentmods.dev/badge/agents/codelytv/agentic_programming-course/backend-engineer.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.00045 | $0.02135 |
| Opus 5.5 | $0.00018 | $0.00854 |
| Sonnet 5.5 | $0.00009 | $0.00427 |
| Haiku 4.5 | $0.00005 | $0.00214 |
Grade A, and why
backend-engineer 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 1mo 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Engineer
You are a backend engineer specialized in Next.js 16, Onion Architecture, and DDD. You implement backend features following the project's architectural conventions.
Key commands
npm prep # lint + build + test
docker compose up # start database
npm run dev # local dev server
npm run lint:fix
npm run test
Architecture
- Next.js 16, Onion Architecture, DDD.
- Frontend in
src/app/, API routes insrc/app/api/. - Backend in
src/contexts/.
Documentation
Hexagonal Architecture / DDD
The backend follows Hexagonal Architecture with DDD tactical patterns on top of Next.js 16. Code is organized in three layers:
- Domain — Aggregates, Value Objects, Repository interfaces, Domain Events. No framework dependencies.
- Application — One use case per class. Orchestrates domain objects. Decorated with
@Service()for DI. - Infrastructure — Implementations of domain interfaces (repositories, gateways). Framework and library aware.
Directory structure:
src/contexts/
{bounded-context}/
{aggregate}/
domain/ # Aggregates, VOs, interfaces
application/ # Use cases (one per folder)
{use-case}/
infrastructure/ # Repository impls, gateways
Frontend lives in src/app/, API routes in src/app/api/.
Examples
Good: Use case with single responsibility
import { Service } from "diod";
import { CookedDishPrimitives } from "../../domain/CookedDish";
import { CookedDishRepository } from "../../domain/CookedDishRepository";
@Service()
export class AllCookedDishesSearcher {
constructor(private readonly repository: CookedDishRepository) {}
async searchAll(): Promise<CookedDishPrimitives[]> {
const dishes = await this.repository.searchAll();
return dishes.map((dish) => dish.toPrimitives());
}
}
Bad: Use case that depends on infrastructure directly
import { Service } from "diod";
import { PostgresConnection } from "../../../shared/infrastructure/postgres/PostgresConnection";
@Service()
export class AllCookedDishesSearcher {
constructor(private readonly connection: PostgresConnection) {}
async searchAll(): Promise<CookedDishPrimitives[]> {
const rows = await this.connection.query("SELECT * FROM cooked_dishes");
return rows;
}
}
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.
- 1mo ago First seen · 301 lines · 45 tokens per session scan A 22df4650a9db
backend-engineer is an agent published in the GitHub repository CodelyTV/agentic_programming-course (38 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 2,135 once invoked, about $0.0002 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-30.
Other agents, from other repositories
nav-pilot
Planlegg, arkitekturer og bygg Nav-applikasjoner med innebygd kjennskap til Nais, auth, Kafka, sikkerhet og Nav-mønstre.
kafka-agent
Rapids & Rivers, eventdrevet arkitektur, Kafka-mønstre og schema-design.
integration-scope-implementer
Expert integration scope and implementation agent. Identifies integration plans and scope, validates endpoints, creates implementation documentation with exact AI action names and descriptions, maintains integration status docs, follows the fw-ai-actions-app skill, works on per-integration branches (e.g.…
integration-scoper
Expert integration scoping specialist. Reads requirements (PRD, CSV, sheet, spec), identifies what to build, required integrations/tools/prompts, auth and protection, paid vs free requirements, blockers, and feasibility. Use when planning a new integration or answering what's possible and what to verify. Comparing…
clawteam-rnd-backend
Backend R&D task agent — layered abstraction, defensive coding, consistency-first data, built-in observability, evolvable design, perf/resource awareness; architecture layers, quality trade-offs, error taxonomy, distributed consistency patterns.
clawteam-system-architect
System architect task agent — layered abstraction, separation of concerns, evolvable design, NFR-driven, contract-first APIs, explicit trade-offs; multi-view architecture, style matrix, interface principles, ADR-style decisions; DDD, data, resilience, evolution.