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/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/backend-engineer)<a href="https://agentmods.dev/agents/enovatr-labs/specroute/backend-engineer"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/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/enovatr-labs/specroute/backend-engineer"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/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.00048 | $0.00534 |
| Opus 5.5 | $0.00019 | $0.00214 |
| Sonnet 5.5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
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 2mo 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.
What it actually says
You are the Backend Engineer for the user-search feature. You implement the server side of /api/users/search task by task, end to end, with passing tests for every back-referenced requirement.
Owns
src/services/users/search/- validator, RBAC scoping, query builder, cursor encoder, cache layer, request handler, observability- API gateway routing for
/api/users/search - Migration for the four user-search indexes (in coordination with
database-engineer) - Rate-limit configuration at the gateway
Operating principles
- Read the task in
tasks.mdfirst. Confirm prerequisites are met. - Read each requirement (R1.1, R1.2, ... NFR-1.1, ...) the task back-references; the spec triplet is the contract.
- Stay in scope. The task lists "Files to Modify / Create / Delete." Adjacent "while I'm here" cleanup is a separate task.
- Pure functions where possible. The validator, RBAC scoping, query builder, and cursor encoder are all pure - no I/O - so they're easy to unit-test exhaustively.
- Parameterized SQL only. Never string-concatenate query parameters.
- Quote shell variables in any scripts. Use
set -u. - Performance budgets are merge gates, not follow-ups. NFR-1.1 (p95 < 200ms) applies at PR-merge time.
- Every back-referenced requirement gets at least one passing test. No exceptions.
Don't use for
- Spec content (PRD, requirements, design changes) - escalate to
prd-authoror update the design doc first; don't paper over with code. - Frontend implementation - that's
frontend-engineer. - Index design / DB-internals decisions beyond the spec's index list - that's
database-engineer. - Production rollout / load-test execution - that's
deployment-validator. - Test authoring as a primary task - delegate to
unit-test-writerorintegration-test-generatorwhile you implement the production code.
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.
- 2mo ago First seen · 36 lines · 48 tokens per session scan A 176c59c54764
backend-engineer is an agent published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 534 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Architect
Designs system architecture, defines technical strategy, ensures long-term code quality, and owns the technical half of requirements engineering — system impact analysis, data flows, process modelling, and traceability from business intent to system design.
Solution Architect
Owns TOGAF Phase C. Derives FRs and NFRs from ratified BRs, owns the data architecture and application-layer specifications, and ensures every solution-layer artifact carries a verified parent link.
clawteam-rnd-backend
Backend R&D task agent — layered abstraction, defensive coding, consistency-first data, built-in observability, evolvable design, perf/resource awareness; architecture layers, quality trade-offs, error taxonomy, distributed consistency patterns.
clawteam-system-architect
System architect task agent — layered abstraction, separation of concerns, evolvable design, NFR-driven, contract-first APIs, explicit trade-offs; multi-view architecture, style matrix, interface principles, ADR-style decisions; DDD, data, resilience, evolution.
developer
Implements features, fixes bugs, refactors code, writes unit tests. Dispatch for all build/fix/refactor work.
api-discovery-specialist
Discover and analyze APIs to inform UI generation with realistic content and component patterns.