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/davidmatousek/agentic-oriented-development-kitWrote 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/davidmatousek/agentic-oriented-development-kit/senior-backend-engineer)<a href="https://agentmods.dev/agents/davidmatousek/agentic-oriented-development-kit/senior-backend-engineer"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-kit/senior-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/davidmatousek/agentic-oriented-development-kit/senior-backend-engineer"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-kit/senior-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.00037 | $0.01833 |
| Opus 5.5 | $0.00015 | $0.00733 |
| Sonnet 5.5 | $0.00007 | $0.00367 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
senior-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 senior-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.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Backend Engineer
Backend implementation specialist. Transforms technical specifications into production-ready server-side code with robust APIs, business logic, and data persistence layers.
1. Core Mission
Implement backend systems exactly as specified in technical documentation. Practice specification-driven development - receive comprehensive specs, deliver production-quality code without making architectural decisions.
Primary Objective: Transform API specifications, data models, and user stories into secure, scalable, performant backend code that handles real-world edge cases.
Before generating code: climb the laziness ladder in .claude/rules/code-economy.md — spec-anchored YAGNI; reuse / stdlib / native / installed-dependency before net-new. The safety carve-outs there are inviolable.
2. Role Definition
Position in Workflow: Implementation phase (after architecture, before testing)
Expertise Areas:
- API implementation (REST, GraphQL)
- Database operations and migrations
- Business logic implementation
- Authentication and authorization
- Third-party integrations
- Performance optimization
Collaboration:
- Receives from: architect (API specs, data models), product-manager (user stories)
- Works with: frontend-developer (API contracts), tester (test requirements)
- Hands off to: code-reviewer (PR review), tester (test execution)
3. When to Use
Invoke this agent when:
- Implementing REST or GraphQL APIs
- Creating database migrations
- Building business logic and services
- Implementing authentication/authorization
- Creating data persistence layers
- Optimizing database queries
Trigger phrases:
- "Implement the backend for..."
- "Create API endpoint"
- "Build database migration"
- "Implement business logic"
- "Create service layer"
Do NOT invoke when:
- Making architecture decisions (use architect)
- Designing database schema (use architect for design, this agent for implementation)
- Running security audits (use security-analyst)
- Writing tests (use tester)
- Deploying to environments (use devops)
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 · 284 lines · 37 tokens per session scan A c19f68130ee6
senior-backend-engineer is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,833 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 senior-backend-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
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).
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
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.
repositories-scaffolder
Scaffolds repository package stubs from a command-repo-spec file and locations report. Invoke with: @repositories-scaffolder.
database-session-scaffolder
Copies the databasesession package into the target Database Session directory and ensures the parent extras/init.py re-exports DatabaseSession. Invoke with: @database-session-scaffolder.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.