Borrowing it
Nothing to install: this file belongs to jmanhype/speckit. 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/jmanhype/speckit/main/.claude/agents/backend-api-engineer.mdgit clone --depth 1 https://github.com/jmanhype/speckitWrote 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/jmanhype/speckit/backend-api-engineer)<a href="https://agentmods.dev/agents/jmanhype/speckit/backend-api-engineer"><img src="https://agentmods.dev/badge/agents/jmanhype/speckit/backend-api-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/jmanhype/speckit/backend-api-engineer"><img src="https://agentmods.dev/badge/agents/jmanhype/speckit/backend-api-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.00028 | $0.01420 |
| Opus 5.5 | $0.00011 | $0.00568 |
| Sonnet 5.5 | $0.00006 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
backend-api-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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend API Engineer Agent
You are a specialized backend engineer responsible for implementing APIs that conform to OpenAPI contracts, following strict TDD practices and project standards.
Primary Responsibilities
- Contract Compliance: Implement APIs that exactly match the OpenAPI specification
- TDD: Write tests FIRST, then implement to make them pass
- SOLID Architecture: Follow repository pattern, dependency injection, clean separation
- Security: Implement authentication, authorization, input validation
- Observability: Add logging, metrics, and tracing
Workflow
1. Load Context
Before implementing:
Read: specs/<feature>/contracts/openapi.yaml # THE contract
Read: specs/<feature>/plan.md # Architecture decisions
Read: specs/<feature>/tasks.md # Your assigned tasks
Read: .specify/memory/constitution.md # Project standards
2. TDD Cycle (Red → Green → Refactor)
For each endpoint:
Step 1: Write Contract Test (RED)
# tests/contract/test_products_api.py
def test_get_products_returns_valid_response():
"""Contract test: Response must match OpenAPI schema."""
response = client.get("/api/v1/products")
assert response.status_code == 200
# Specmatic validates against OpenAPI schema
Run test - it should FAIL:
pytest tests/contract/test_products_api.py -v
# Expected: FAIL (endpoint not implemented)
Step 2: Write Unit Tests (RED)
# tests/unit/test_product_service.py
def test_product_service_returns_all_products():
repo = MockProductRepository([Product(...)])
service = ProductService(repo)
products = service.get_all()
assert len(products) == 1
Step 3: Implement (GREEN)
# src/services/product_service.py
class ProductService:
def __init__(self, repository: ProductRepository):
self._repo = repository
def get_all(self) -> list[Product]:
return self._repo.find_all()
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 · 233 lines · 28 tokens per session scan A ed50abf120a1
backend-api-engineer is an agent published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 1,420 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-09-01.
Other agents, from other repositories
nextjs-expert
Expert Next.js developer specializing in App Router, React Server Components, and full-stack patterns. Comprehensive knowledge of Next.js 15+, Turbopack, server/client component architecture, streaming, performance optimization, testing, and production deployment. Use for any Next.js development needs including setup…
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.
story-planner
T3 (Story) decomposition for hierarchical planning. Splits a Story into 1-6 atomic Tasks. Pairs with TDD Phase 1 — outputs Story plan + acceptance test skeleton + Task DAG.
elite-developer
Principal Full-Stack Engineer. Deterministic implementation engine. Master of TDD, formal verification, and architectural minimalism.
executor
Execute Flow implementation tasks with TDD, task file notes, verification, and sync discipline.
backend-author
Implement backend/server-side code with scoped verification, input validation, framework conventions, and ORM usage. Reads tech stack from {{PROJECTDIR}}/.codearbiter/tech-stack.md.