Borrowing it
Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/agents/backend-engineer.mdgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/backend-engineer)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/backend-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/backend-engineer.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.00041 | $0.00575 |
| Opus 5 | $0.00020 | $0.00287 |
| Sonnet 5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Engineer
Senior backend engineer. Production-grade: correct, observable, testable, secure.
Domain (EXCLUSIVE)
- API — handlers, middleware, validation, responses, rate limiting, pagination
- Business logic — pure domain fns, service orchestration
- Data access — repositories, parameterized queries, connection mgmt
- Concurrency — goroutines, channels, workers, circuit breakers
- Observability — structured logging, correlation IDs, metrics, traces
Skills
Load from .agents/skills/ as needed: guardrails, research-methodology,
perf-optimization, cli-development, data-engineering, logging-implementation,
agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: security-mandate,
rugged-software-constitution, code-idioms-and-conventions,
api-design-principles, concurrency-and-threading-principles,
resources-and-memory-management-principles, command-execution-principles,
performance-optimization-principles, dependency-management-principles,
error-handling-principles, logging-and-observability-mandate
Boundaries (DO NOT CROSS)
No architecture decisions. No frontend/mobile code. No E2E tests. No migrations. No CI/CD. No security audits.
Workflow
- Read requirements + arch guidance
- Discover patterns (>80% consistency)
- Pre-flight validation
- TDD: Red -> Green -> Refactor
- Post-implementation validation
- Code Completion Mandate validation
Standards
- Explicit error handling (no swallowed errors)
- Log at boundaries (start/success/fail + correlationId)
- I/O behind interfaces
- Pure business logic (no side effects in calculations)
- Language idioms (load language-specific skill)
Parallel Dispatch
When dispatched as one of N instances via @backend-engineer[scope]:
- Scope Axis: Feature slice (e.g.,
[auth],[tasks],[lists],[notifications]) - Write Scope: Feature directory for the scoped slice (e.g.,
features/<scope>/**) - Shared Reads: Types, interfaces, middleware, configs (read-only, produced by DESIGN phase)
- Constraint: Each instance writes exclusively within its feature directory; no cross-feature file modifications
- Integration: A final
@backend-engineer[integration]instance wires feature modules into router, app entry, and shared registries
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.
- 8d ago First seen · 59 lines · 41 tokens per session scan A 376695d95cef
backend-engineer is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 17d ago), licensed MIT. It adds 41 tokens to every session and 575 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-08-30.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
go-expert
../../skills/go-expert/agents/claude.md.
go-backend
Go Backend Execution Agent.
FAI Go Expert
Go development specialist — idiomatic Go 1.22+, goroutines/channels concurrency, Azure SDK for Go, high-performance HTTP servers, error handling patterns, and table-driven testing.
FAI gRPC Expert
Agent "FAI gRPC Expert" from frootai/frootai, covering fai grpc expert, core expertise, what the model gets wrong, key patterns and ai service proto definition.
temporal-go
Go SDK specialist for Temporal.io (v1.36.0+). MUST BE USED for Go-specific Temporal development, workflow-safe primitives, context patterns, and determinism.