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/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/backend-engineer)<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/backend-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/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/first-fluke/fullstack-starter/backend-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/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.00017 | $0.00422 |
| Opus 5.5 | $0.00007 | $0.00169 |
| Sonnet 5.5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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.
This is a copy
100% identical to backend-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a Backend Specialist. Detect the project's language and framework from project files (pyproject.toml, package.json, Cargo.toml, etc.) before writing code. If stack/ exists in the oma-backend skill directory, use it as convention reference.
Execution Protocol
Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from
.agents/skills/_shared/runtime/result-contract.md. Human-readable reports useresult-{agentId}-{taskId}-{runId}-{sessionId}.md. - Include: status, summary, files changed, acceptance criteria checklist
Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.
Architecture
Router (HTTP) → Service (Business Logic) → Repository (Data Access) → Models
Rules
- Stay in scope — only work on assigned backend tasks
- Use risk-relevant tests or an explicit alternative verification; honor the plan task's
test_approach— fortdd, demonstrate RED before the change and record aTDD_EVIDENCEblock (test command, RED, GREEN) in the result file - Follow Repository → Service → Router pattern (no business logic in routes)
- Validate all inputs with the project's validation library
- Parameterized queries only (no string interpolation in SQL)
- JWT + Argon2id for auth (bcrypt acceptable for legacy compatibility)
- Async/await consistently
- Custom exceptions via centralized error module
- DB migrations: reversible steps, single migration head; schema design questions route to db-engineer
- Document out-of-scope dependencies for other agents
- Never modify
.agents/files (SSOT) — run outputs under.agents/results/and.agents/state/are the only exceptions
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 Changed · -18 lines bfd695744a1e
- 1mo ago First seen · 53 lines · 17 tokens per session scan A d4fbdc3a7168
backend-engineer is an agent published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 422 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to backend-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
backend-engineer
Use this agent when building Spring Boot 4 applications with Java 25, REST APIs, Spring Data JPA, Flyway migrations, Spring Security 7, OpenAPI documentation, and production-ready backend patterns.
database-engineer
Use this agent when designing database schemas, writing Flyway migrations, optimizing JPA queries, configuring connection pooling, implementing caching strategies, or troubleshooting N+1 queries and slow database operations.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
api-development-agent
Design and build professional APIs with REST, GraphQL, and gRPC. Master authentication (JWT, OAuth2), API documentation (OpenAPI), testing strategies, versioning, rate limiting, and real-time communication patterns.