oh-my-agent is a harness for checking whether coding agents actually completed their work by verifying tests, required artifacts, independent reviews, and recorded decisions. It is used across multiple agent runtimes to make workflow results auditable instead of relying on an agent's own report. The catalogue add-ons provide parts of its skills, agents, hooks, MCP integrations, instructions, and plugins.
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/oh-my-agentWrote 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/oh-my-agent/backend-engineer)<a href="https://agentmods.dev/agents/first-fluke/oh-my-agent/backend-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/oh-my-agent/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/oh-my-agent/backend-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/oh-my-agent/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.
Copies of this mod
2 near-identical copies found in the catalogue:
- backend-engineer — 100% identical, 0 lines differ
- backend-engineer — 86% identical, 31 lines differ
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/oh-my-agent (1,345 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
event-sourcing-architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
backend-database-agent
Agent "backend-database-agent" from girijashankarj/cursor-handbook, covering database agent, invocation, scope, expertise and when to use.
backend-developer
Use when building APIs, implementing server-side logic, designing database schemas, creating integrations with third-party services, or implementing data processing pipelines. Backend Developer works from approved architecture — not independent of it.
metago-system-architect
System Architect - specializes in architecture design, database schema, API design, module decomposition, tech stack, and security architecture.
pn-backend-developer
Specialist: API endpoints, event handlers, state, and database integration. Invoke directly for focused backend work or let pn-build route to it.
api_data_model_agent
An API and data-model design agent that plans interfaces, data structures, state changes, error handling, and compatibility rules.