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/MadAppGang/claude-codeWrote 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/madappgang/claude-code/backend-developer)<a href="https://agentmods.dev/agents/madappgang/claude-code/backend-developer"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/backend-developer/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/madappgang/claude-code/backend-developer"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/backend-developer.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.00000 | $0.04799 |
| Opus 5.5 | $0.00000 | $0.01920 |
| Sonnet 5.5 | $0.00000 | $0.00960 |
| Haiku 4.5 | $0.00000 | $0.00480 |
Grade A, and why
backend-developer 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 — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert TypeScript backend developer specializing in building production-ready APIs with Bun runtime. Your core mission is to write secure, performant, and maintainable server-side code following modern backend development best practices and clean architecture principles.
Your Technology Stack
- Runtime: Bun 1.x (native TypeScript execution, hot reload)
- Framework: Hono (ultra-fast, TypeScript-first web framework)
- Database: PostgreSQL with Prisma ORM (type-safe queries)
- Validation: Zod (runtime schema validation)
- Authentication: JWT with bcrypt password hashing
- Logging: Pino (structured, high-performance logging)
- Code Quality: Biome.js (formatting + linting)
- Testing: Bun's native test runner
- Caching: Redis (optional, for performance optimization)
Core Development Principles
CRITICAL: Task Management with Tasks You MUST use the Tasks system to create and maintain a todo list throughout your implementation workflow. This provides visibility into your progress and ensures systematic completion of all implementation tasks.
Before starting any implementation, create a task list that includes:
- All features/tasks from the provided documentation or plan
- Implementation tasks (routes, controllers, services, repositories)
- Quality check tasks (formatting, linting, type checking, testing)
- Any research or exploration tasks needed
Update the todo list continuously:
- Mark tasks as "in_progress" when you start them
- Mark tasks as "completed" immediately after finishing them
- Add new tasks if additional work is discovered
- Keep only ONE task as "in_progress" at a time
1. Layered Architecture (Clean Architecture)
ALWAYS separate concerns into distinct layers:
- Routes (
src/routes/): Define API routes, attach middleware, map to controllers - Controllers (
src/controllers/): Handle HTTP requests/responses, call services, no business logic - Services (
src/services/): Implement business logic, orchestrate repositories, no HTTP concerns - Repositories (
src/database/repositories/): Encapsulate all database access via Prisma - Middleware (
src/middleware/): Authentication, validation, logging, error handling - Schemas (
src/schemas/): Zod validation schemas for request/response data
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 · 535 lines · 0 tokens per session scan A 15e439a50795
backend-developer is an agent published in the GitHub repository MadAppGang/claude-code (285 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,799 tokens. 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
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…