microservices-patterns

microservices-patterns is a skill for Claude Code, Codex from svngoku/coding-agents-skills. It costs 121 tokens per session (3,862 once invoked), scanned A, original, MIT.

A guide to splitting a large application into microservices, which are separately deployable services that each own part of the system and its data.

In plain words
What is it for?
Choosing between microservices and a modular monolith, defining service boundaries, and designing workflows, communication, retries, monitoring, testing, and deployment.
Why use it?
It helps teams decide whether splitting is appropriate and address problems such as failed network calls, inconsistent data, and services drifting apart.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/svngoku/coding-agents-skills/microservices-patterns
Any agent
npx skills add svngoku/coding-agents-skills --skill microservices-patterns
Clone the repo
git clone --depth 1 https://github.com/svngoku/coding-agents-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for microservices-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/svngoku/coding-agents-skills/microservices-patterns.svg)](https://agentmods.dev/skills/svngoku/coding-agents-skills/microservices-patterns)
Your own site
<a href="https://agentmods.dev/skills/svngoku/coding-agents-skills/microservices-patterns"><img src="https://agentmods.dev/badge/skills/svngoku/coding-agents-skills/microservices-patterns.svg" alt="Measured on agentmods" height="20"></a>
Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,862 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00121 $0.03862
Opus 5 $0.00060 $0.01931
Sonnet 5 $0.00024 $0.00772
Haiku 4.5 $0.00012 $0.00386

Measured 4d ago against content hash 0d979b8d2b62, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 4d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (graders/check.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/microservices-patterns/SKILL.md · 268 lines

How it starts

The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Microservices Patterns

Microservices split a system into small, independently deployable services, each owned by one team and owning its own data. The value is organizational: independent deploys, independent scaling, and a contained blast radius — but every one of those wins comes with a distributed-systems tax: cross-service consistency, partial failure, and contract drift. This skill is the playbook for paying that tax deliberately: deciding whether decomposition is warranted, finding the boundaries, and applying the canonical patterns for communication, consistency, resilience, observability, testing, and deployment.

Quick Reference

Topic Reference
Sagas, compensating actions, and the outbox pattern saga-outbox.md
Timeouts, retries, circuit breakers, bulkheads, load shedding resilience-patterns.md
Structured logs, RED metrics, OpenTelemetry tracing, health probes observability-tracing.md

Core Workflow

Use this sequence whenever you are architecting or re-architecting toward microservices:

  1. Decide — confirm decomposition is warranted using the decision table below; if not, design a modular monolith instead.
  2. Find boundaries — map subdomains and bounded contexts; one service per context (or per core subdomain).
  3. Choose communication — per service relationship, pick async events, messages, or sync request/reply.
  4. Make data consistent — where a business operation spans services, design a saga; use the outbox pattern for reliable event publishing.
  5. Harden every call — timeouts, retries, circuit breakers, bulkheads around each dependency.
  6. Make it observable — structured logs with trace IDs, RED metrics, distributed tracing, health/readiness endpoints.
  7. Protect the contracts — contract tests (e.g., Pact) between producers and consumers; per-service test strategy.
  8. Deploy independently — per-service pipelines, feature flags, canary releases.

Read the full file on GitHub · 268 lines

Files

What ships with it

8 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.

Changes

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.

  1. 4d ago First seen · 268 lines · 121 tokens per session scan A 0d979b8d2b62

Subscribe to this mod's changes

microservices-patterns is a skill published in the GitHub repository svngoku/coding-agents-skills (9 stars, last pushed 21d ago), licensed MIT. It adds 121 tokens to every session and 3,862 once invoked, about $0.0006 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.