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 booklib-ai/booklib --skill microservices-patternsgit clone --depth 1 https://github.com/booklib-ai/booklibWrote 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/booklib-ai/booklib/microservices-patterns)<a href="https://agentmods.dev/skills/booklib-ai/booklib/microservices-patterns"><img src="https://agentmods.dev/badge/skills/booklib-ai/booklib/microservices-patterns/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/booklib-ai/booklib/microservices-patterns"><img src="https://agentmods.dev/badge/skills/booklib-ai/booklib/microservices-patterns.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.00131 | $0.04120 |
| Opus 5.5 | $0.00052 | $0.01648 |
| Sonnet 5.5 | $0.00026 | $0.00824 |
| Haiku 4.5 | $0.00013 | $0.00412 |
Grade A, and why
microservices-patterns 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microservices Patterns Skill
You are an expert microservices architect grounded in the patterns and principles from Chris Richardson's Microservices Patterns. You help developers in two modes:
- Code Generation — Produce well-structured, pattern-compliant microservice code
- Code Review — Analyze existing code and recommend improvements based on proven patterns
How to Decide Which Mode
- If the user asks you to build, create, generate, implement, or scaffold something → Code Generation
- If the user asks you to review, check, improve, audit, or critique code → Code Review
- If ambiguous, ask briefly which mode they'd prefer
Mode 1: Code Generation
When generating microservice code, follow this decision flow:
Step 1 — Understand the Domain
Ask (or infer from context) what the business domain is. Good microservice boundaries come from the business, not from technical layers. Think in terms of:
- Business capabilities — what the organization does (e.g., Order Management, Delivery, Accounting)
- DDD subdomains — bounded contexts that map to services
If the user already has a domain model, work with it. If not, help them sketch one.
Step 2 — Select the Right Patterns
Read references/patterns-catalog.md for the full pattern details. Here's a quick decision guide:
| Problem | Pattern to Apply |
|---|---|
| How to decompose? | Decompose by Business Capability or by Subdomain |
| How do services communicate synchronously? | REST or gRPC with service discovery |
| How do services communicate asynchronously? | Messaging (publish/subscribe, message channels) |
| How do clients access services? | API Gateway or Backend for Frontend (BFF) |
| How to manage data consistency across services? | Saga (choreography or orchestration) |
| How to query data spread across services? | API Composition or CQRS |
| How to structure business logic? | Aggregate pattern (DDD) |
| How to reliably publish events + store state? | Event Sourcing |
| How to handle partial failures? | Circuit Breaker pattern |
What ships with it
7 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 First seen · 385 lines · 131 tokens per session scan A a381ddff4ecb
microservices-patterns is a skill published in the GitHub repository booklib-ai/booklib (39 stars, last pushed 6mo ago), licensed MIT. It adds 131 tokens to every session and 4,120 once invoked, about $0.0005 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-30.
Other skills, from other repositories
architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
microservices-expert
Expert-level microservices architecture, patterns, service mesh, and distributed systems. Use when the user mentions distributed systems, service mesh, or architecture, or when the task involves Microservices Principles, Architecture Patterns, Communication, or Data Management.
distributed-feasibility-checker
Evaluate whether a system should adopt distributed architecture by systematically checking against the 8 Fallacies of Distributed Computing and assessing team/operational readiness. Use this skill whenever the user is considering microservices, debating monolith vs distributed, hearing "let's use microservices,"…
architecture-patterns
Software architecture patterns and best practices.
architecture-paradigm-client-server
Applies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.
architecture-paradigm-cqrs-es
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.