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 skills add mnzralee/claude-multi-agent-architecture --skill backendgit clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architectureWrote 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/skills/mnzralee/claude-multi-agent-architecture/backend)<a href="https://agentmods.dev/skills/mnzralee/claude-multi-agent-architecture/backend"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/backend/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/skills/mnzralee/claude-multi-agent-architecture/backend"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/backend.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.00033 | $0.07301 |
| Opus 5.5 | $0.00013 | $0.02920 |
| Sonnet 5.5 | $0.00007 | $0.01460 |
| Haiku 4.5 | $0.00003 | $0.00730 |
Grade A, and why
backend 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 — 786 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Development Skill
You are an expert backend developer. This skill provides comprehensive patterns for building enterprise-grade microservices following Clean Architecture principles.
The concrete examples below assume a TypeScript / Node.js / Express stack with Zod for validation and an ORM for persistence, because concrete code is easier to learn from than abstract description. The discipline itself is stack-agnostic: the layering, the dependency direction, the outbox pattern, the validation contract, and the testing strategy translate directly to any language and framework. Where you see a TypeScript idiom, read it as the general principle expressed in one concrete dialect.
Architecture Overview
A typical monorepo layout for this style of system:
backend/ # Monorepo (e.g. Turborepo, Nx, pnpm workspaces)
├── apps/ # Microservices
│ ├── svc-admin/ # Admin / back-office operations
│ ├── svc-auth/ # Authentication
│ ├── svc-account/ # Account management
│ ├── svc-billing/ # Billing, balances, transfers
│ ├── svc-catalog/ # Domain entity catalog
│ ├── svc-notification/ # Notifications, messaging
│ └── svc-<name>/ # Additional domain services
├── workers/ # Background workers
│ ├── projector/ # Event projection into read models
│ └── outbox-submitter/ # CQRS command submission
├── packages/ # Shared libraries
│ ├── core-http/ # HTTP middleware, validation helpers
│ ├── core-db/ # ORM client
│ ├── core-config/ # Env-var schema validation
│ ├── core-logger/ # Structured logging
│ ├── core-errors/ # Standardized error classes
│ ├── core-events/ # Event schema registry
│ ├── core-storage/ # Document storage, file handling
│ ├── core-openapi/ # OpenAPI validation
│ └── test-utils/ # Test containers, data factories
└── db/ # The schema and migrations
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -78 lines 3fad2a51c27a
- 1mo ago First seen · 864 lines · 33 tokens per session scan A fc5e1b12b9bd
backend is a skill published in the GitHub repository mnzralee/claude-multi-agent-architecture (8 stars, last pushed 26d ago), licensed MIT. It adds 33 tokens to every session and 7,301 once invoked, about $0.0001 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 skills, from other repositories
backend-developer
Backend Developer (/be, alias: James, /james) - Senior Backend Developer with 10+ years experience. Covers Java/Spring Boot (default), Kotlin, Python/FastAPI, PHP/Laravel, Quarkus, and Kafka/messaging - detects the project's stack and loads the matching reference. Use when implementing server features, REST APIs…
backend-tester
Senior QA Engineer with 10+ years Java testing experience. Use when writing unit tests with JUnit, creating integration tests with Testcontainers, implementing API tests, following TDD methodology, or testing reactive code with StepVerifier.
test-integration
Test how components work together. Test database + API, auth + user service, etc. Use when testing multi-component flows or after unit tests pass.
business-api-context
What the API of the system under test MEANS to the business: every endpoint group, who calls it and why, what it changes, which auth level and role it needs, the business flows that cross several endpoints, error semantics and the external integrations behind them. Load it whenever a task touches an API test, a…
pdlc-api-mock
A command that reads API design documents and creates realistic sample responses and configuration for a mock service. A mock service imitates an API so frontend code can be tested before the real backend is ready.
testing
Test generation, coverage analysis, and test strategy.