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/madappgang/claude-code/backend-developergit clone --depth 1 https://github.com/MadAppGang/claude-codeWhat 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.00176 | $0.04799 |
| Opus 5 | $0.00088 | $0.02400 |
| Sonnet 5 | $0.00035 | $0.00960 |
| Haiku 4.5 | $0.00018 | $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 2d 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.
- 2d 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 (279 stars, last pushed 5mo ago), licensed MIT. It adds 176 tokens to every session and 4,799 once invoked, about $0.0009 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.