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/hoangatg/ai-agent-toolkit/microservices-patternsnpx skills add hoangatg/ai-agent-toolkit --skill microservices-patternsgit clone --depth 1 https://github.com/hoangatg/ai-agent-toolkitWrote 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/hoangatg/ai-agent-toolkit/microservices-patterns)<a href="https://agentmods.dev/skills/hoangatg/ai-agent-toolkit/microservices-patterns"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/microservices-patterns.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00715 |
| Opus 5 | $0.00015 | $0.00358 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
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 today.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microservices Patterns
Break systems apart. Keep them working together.
1. Decomposition Strategies
When to Use Microservices
| Signal | Monolith | Microservices |
|---|---|---|
| Team size | < 10 | 10+ (multiple teams) |
| Deploy frequency | Weekly | Multiple times/day |
| Scaling needs | Uniform | Different per component |
| Tech diversity | One stack | Multiple stacks needed |
Decomposition Approaches
| Approach | Method |
|---|---|
| By business domain | Bounded contexts (DDD) |
| By subdomain | Core, supporting, generic |
| Strangler fig | Gradually extract from monolith |
| By data ownership | Each service owns its data |
2. Communication Patterns
Sync vs Async
| Pattern | Use When | Protocol |
|---|---|---|
| Request/Response | Need immediate answer | HTTP, gRPC |
| Event-driven | Fire-and-forget, decoupling | Kafka, RabbitMQ, SQS |
| Command | Trigger action, need ack | Queue + response |
| Query | Read data, no side effects | HTTP GET, GraphQL |
API Gateway
| Responsibility | Implementation |
|---|---|
| Routing | Path-based routing to services |
| Auth | JWT validation, API keys |
| Rate limiting | Per-client quotas |
| Aggregation | Combine multiple service responses |
3. Data Management
Database per Service
| Principle | Application |
|---|---|
| Own your data | Each service has its own DB |
| No shared databases | Coupling killer |
| Saga pattern | Distributed transactions |
| Event sourcing | Audit trail, temporal queries |
| CQRS | Separate read/write models |
Saga Patterns
| Type | How It Works |
|---|---|
| Choreography | Services react to events |
| Orchestration | Central coordinator manages steps |
4. Resilience Patterns
| Pattern | Purpose |
|---|---|
| Circuit breaker | Stop cascading failures |
| Retry + backoff | Handle transient errors |
| Timeout | Don't wait forever |
| Bulkhead | Isolate failure domains |
| Fallback | Graceful degradation |
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.
- today First seen · 113 lines · 30 tokens per session scan A 83569cb34daf
microservices-patterns is a skill published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 715 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
opencode
Delegate coding tasks to the OpenCode CLI for feature work, refactoring, PR review, and autonomous-style runs. Requires opencode installed where the agent can execute shell commands.
codex
Delegate coding tasks to the OpenAI Codex CLI for features, refactoring, PR reviews, and batch fixes. Requires the codex CLI and typically a git repository.
deepnote
DeepNote knowledge base: persistent interlinked markdown wiki with ingest, query, lint, link graph and history.