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 skills/booklib-ai/booklib/microservices-patternsnpx skills add booklib-ai/booklib --skill microservices-patternsgit clone --depth 1 https://github.com/booklib-ai/booklibWhat 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.00131 | $0.04120 |
| Opus 5 | $0.00066 | $0.02060 |
| Sonnet 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 3d 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.
- 3d 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 (38 stars, last pushed 4mo ago), licensed MIT. It adds 131 tokens to every session and 4,120 once invoked, about $0.0007 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 skills, from other repositories
project-spine-kickoff
Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs spine init → edits brief → spine compile → reviews outputs. For stale files use…
project-spine
Use when the user mentions AGENTS.md, CLAUDE.md, copilot-instructions, Cursor rules, project brief, context for coding agents, agency kickoff, onboarding a new project, or asks "how do I set up Project Spine". This is the orientation skill — reach for it FIRST when the user's intent involves Project Spine, then chain…
project-spine-drift
Use when the user mentions drift, says AGENTS.md / CLAUDE.md / copilot-instructions / Cursor rules are "stale" or "out of date", asks about CI catching docs drift, or says "check if my spine is still current". Runs spine drift check, interprets each drift category, and guides resolution. For initial setup use…
project-spine-template
Use when the user wants to apply a bundled, user-local, or project-local template to a new project, or save the current project as a reusable template. Phrases like "use our agency starter", "save this as a template for future clients", "apply the shared saas-marketing starter".
project-spine-rationale
Use when the user wants to review, polish, or share the generated Project Spine rationale file locally. Phrases like "show the project rationale", "send the client a project summary", "review rationale.md", or "make the client-facing overview safer".
project-spine-workspace
Use when the user asks about Project Spine hosted workspaces, team sync, shared workspace templates, invites, or commands such as spine login, spine workspace, spine publish, or spine drift check --push.