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/soulcodex/agentic/microservices-architecturenpx skills add soulcodex/agentic --skill microservices-architecturegit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/microservices-architecture)<a href="https://agentmods.dev/skills/soulcodex/agentic/microservices-architecture"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/microservices-architecture.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.00061 | $0.01185 |
| Opus 5 | $0.00030 | $0.00593 |
| Sonnet 5 | $0.00012 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
microservices-architecture 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microservices Architecture Skill
This skill complements (does not replace) the
microservices.mdfragment. Load the fragment for general principles; use this skill for design decisions.
Step 1 — Service Boundary Analysis
Use Domain-Driven Design bounded contexts to identify service boundaries:
- List the core business domains (e.g., Orders, Inventory, Payments, Notifications).
- For each domain, identify:
- The aggregate root (the entity other entities reference through).
- The invariants that must hold within the domain.
- The external events the domain publishes when its state changes.
- A service boundary aligns with a bounded context. Services should not share a database.
Red flags for a bad boundary:
- Two services always change together → consider merging them.
- A service has no domain logic (only CRUD) → it may not need to be a separate service.
- A service synchronously calls another service on every request → tight coupling.
Step 2 — Communication Pattern Decision
For each service-to-service interaction, choose:
| Scenario | Pattern | Trade-off |
|---|---|---|
| Read-your-own-writes, low latency | Synchronous REST/gRPC | Temporal coupling; caller waits |
| Background processing, at-least-once | Async messaging (SQS, RabbitMQ) | Eventual consistency; harder to debug |
| Event fan-out (multiple consumers) | Pub/sub (EventBridge, Kafka) | Loose coupling; no direct contract |
| Streaming / time-series data | Kafka / Kinesis | High throughput; complex ops |
Rule: prefer async messaging for writes across service boundaries. Use sync calls only for reads where the caller genuinely needs the response before proceeding.
Step 3 — Data Consistency Design
You cannot have distributed transactions without accepting trade-offs. Choose:
Saga (choreography or orchestration):
- Each service publishes an event after its local transaction commits.
- On failure, compensating transactions undo previous steps.
- Use the outbox pattern to guarantee event publication.
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 · 133 lines · 61 tokens per session scan A 5aed8cce2fb8
microservices-architecture is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 1,185 once invoked, about $0.0003 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-31.
Other skills, from other repositories
express-microservices-architecture
Complete guide for building scalable microservices with Express.js including middleware patterns, routing strategies, error handling, production architecture, and deployment best practices.
design-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
design-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
localization-design
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use ux-writing (designer-toolkit).