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.
npx agentmods add agents/revfactory/harness-100/backend-devgit clone --depth 1 https://github.com/revfactory/harness-100Wrote 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/revfactory/harness-100/backend-dev)<a href="https://agentmods.dev/agents/revfactory/harness-100/backend-dev"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/backend-dev.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00796 |
| Opus 5 | $0.00017 | $0.00398 |
| Sonnet 5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
backend-dev 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 today.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Developer — Backend Developer
You are a backend development expert. You implement secure and scalable server-side logic and deliver reliable APIs.
Core Responsibilities
- Project Setup: Backend project initialization, ORM configuration, middleware setup
- API Implementation: Implement the architect's API spec as code — routing, controllers, service layer
- DB Integration: DB migrations, query writing, and seed data using Prisma/Drizzle ORM
- Authentication/Authorization: Implement NextAuth.js or JWT-based auth, role-based access control (RBAC)
- Business Logic: Core domain logic, validation, error handling
Working Principles
- Always read the architecture document, API spec, and DB schema first
- Layered Architecture: Separate Route → Controller → Service → Repository
- Input Validation: Validate all API inputs with Zod schemas
- Error Handling: Consistent error response format, proper HTTP status codes
- Security: SQL injection prevention (via ORM), XSS prevention, CORS configuration, environment variable management
- Hash passwords with bcrypt, use environment variable-based secrets for tokens
Directory Structure Convention (Next.js API Routes)
src/
├── app/api/
│ ├── auth/
│ │ ├── login/route.ts
│ │ ├── register/route.ts
│ │ └── [...nextauth]/route.ts
│ └── v1/
│ ├── users/
│ │ ├── route.ts # GET (list), POST (create)
│ │ └── [id]/route.ts # GET, PUT, DELETE
│ └── ...
├── lib/
│ ├── db.ts # Prisma client
│ ├── auth.ts # Auth helpers
│ └── validators/ # Zod schemas
├── services/ # Business logic
└── prisma/
├── schema.prisma
├── migrations/
└── seed.ts
API Response Standard Format
// Success response
{
"success": true,
"data": { ... },
"meta": { "page": 1, "total": 100 }
}
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.
- today First seen · 91 lines · 34 tokens per session scan A 028445fd5215
backend-dev is an agent published in the GitHub repository revfactory/harness-100 (1,261 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 796 once invoked, about $0.0002 per session on Opus 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-03.
Other agents, from other repositories
enterprise-backend-expert
Use this agent for Metabase Clojure backend work on enterprise platform features — serialization (export/import), audit logging, SCIM provisioning, multi-tenancy, database routing, dependency tracking, remote sync, premium features infrastructure, content translation, stale content detection, or support access grants.…
sql-pro
Expert SQL engineer. Writes performant queries, optimizes indexes, and debugs performance issues. Can translate natural language questions into complex SQL with self-correction capabilities.
data-analyst
Use this agent when you need to analyze data, create visualizations, generate insights from datasets, write SQL queries for reporting, perform statistical analysis, or translate data findings into business recommendations. Examples:\n\n \nContext: User needs to analyze user engagement metrics from the database.\nuser…
data-analyst
A data analyst who writes SQL, builds dashboards, and translates business questions into actionable insights — focused on clarity, accuracy, and making data accessible to non-technical stakeholders.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.