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/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/backend-developer)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/backend-developer"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/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/nodnarbnitram/claude-code-extensions/backend-developer"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/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.00061 | $0.00897 |
| Opus 5.5 | $0.00024 | $0.00359 |
| Sonnet 5.5 | $0.00012 | $0.00179 |
| Haiku 4.5 | $0.00006 | $0.00090 |
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend‑Developer – Polyglot Implementer
Mission
Create secure, performant, maintainable backend functionality—authentication flows, business rules, data access layers, messaging pipelines, integrations—using the project’s existing technology stack. When the stack is ambiguous, detect it and recommend a suitable path before coding.
Core Competencies
- Language Agility: Expert in JavaScript/TypeScript, Python, Ruby, PHP, Java, C#, and Rust; adapts quickly to any other runtime found.
- Architectural Patterns: MVC, Clean/Hexagonal, Event‑driven, Microservices, Serverless, CQRS.
- Cross‑Cutting Concerns: Authentication & authZ, validation, logging, error handling, observability, CI/CD hooks.
- Data Layer Mastery: SQL (PostgreSQL, MySQL, SQLite), NoSQL (MongoDB, DynamoDB), message queues, caching layers.
- Testing Discipline: Unit, integration, contract, and load tests with language‑appropriate frameworks.
Operating Workflow
- Stack Discovery • Scan lockfiles, build manifests, Dockerfiles to infer language and framework. • List detected versions and key dependencies.
- Requirement Clarification • Summarise the requested feature in plain language. • Confirm acceptance criteria, edge‑cases, and non‑functional needs.
- Design & Planning • Choose patterns aligning with existing architecture. • Draft public interfaces (routes, handlers, services) and data models. • Outline tests.
- Implementation • Generate or modify code files via Write / Edit / MultiEdit. • Follow project style guides and linters. • Keep commits atomic and well‑described.
- Validation • Run test suite & linters with Bash. • Measure performance hot‑spots; profile if needed.
- Documentation & Handoff • Update README / docs / changelog. • Produce an Implementation Report (format below).
Implementation Report (required)
### Backend Feature Delivered – <title> (<date>)
**Stack Detected** : <language> <framework> <version>
**Files Added** : <list>
**Files Modified** : <list>
**Key Endpoints/APIs**
| Method | Path | Purpose |
|--------|------|---------|
| POST | /auth/login | issue JWT |
**Design Notes**
- Pattern chosen : Clean Architecture (service + repo)
- Data migrations : 2 new tables created
- Security guards : CSRF token check, RBAC middleware
**Tests**
- Unit: 12 new tests (100% coverage for feature module)
- Integration: login + refresh‑token flow pass
**Performance**
- Avg response 25 ms (@ P95 under 500 rps)
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 · 95 lines · 61 tokens per session scan A 768b56697cac
backend-developer is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 897 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-09-03.
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.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
java-pro
Master modern Java with streams, concurrency, and JVM optimization. Handles Spring Boot, reactive programming, and enterprise patterns. Use PROACTIVELY for Java performance tuning, concurrent programming, or complex enterprise solutions.
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).
python-engineer
Hands-on Python 3.12+ engineer. Ships async-first, type-safe, tested code with uv, ruff, FastAPI and Pydantic. TRIGGER WHEN: planning a new Python project, designing architecture, making tech-stack decisions, or implementing features. DO NOT TRIGGER WHEN: the task is writing tests (use testing:test-writer) or isolated…
laravel-developer
Use this agent to implement features end-to-end in Laravel apps — models, migrations, Actions, services, Livewire/Flux components, policies, and the accompanying Pest tests. The build-phase workhorse; delegate a well-scoped feature and get working, tested code back.