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 svngoku/coding-agents-skills --skill microservices-patternsgit clone --depth 1 https://github.com/svngoku/coding-agents-skillsWrote 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/svngoku/coding-agents-skills/microservices-patterns)<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/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/svngoku/coding-agents-skills/microservices-patterns"><img src="https://agentmods.dev/badge/skills/svngoku/coding-agents-skills/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.00121 | $0.03862 |
| Opus 5.5 | $0.00048 | $0.01545 |
| Sonnet 5.5 | $0.00024 | $0.00772 |
| Haiku 4.5 | $0.00012 | $0.00386 |
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 — 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:
- Decide — confirm decomposition is warranted using the decision table below; if not, design a modular monolith instead.
- Find boundaries — map subdomains and bounded contexts; one service per context (or per core subdomain).
- Choose communication — per service relationship, pick async events, messages, or sync request/reply.
- Make data consistent — where a business operation spans services, design a saga; use the outbox pattern for reliable event publishing.
- Harden every call — timeouts, retries, circuit breakers, bulkheads around each dependency.
- Make it observable — structured logs with trace IDs, RED metrics, distributed tracing, health/readiness endpoints.
- Protect the contracts — contract tests (e.g., Pact) between producers and consumers; per-service test strategy.
- Deploy independently — per-service pipelines, feature flags, canary releases.
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.
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 · 268 lines · 121 tokens per session scan A 0d979b8d2b62
microservices-patterns is a skill published in the GitHub repository svngoku/coding-agents-skills (12 stars, last pushed 3d ago), licensed MIT. It adds 121 tokens to every session and 3,862 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-31.
Other skills, from other repositories
feature-workflow
Phased workflow for delivering a Drupal feature or non-trivial change: plan, implement, review, test, finalize. Use when building a new custom module, adding a route/form/plugin, changing entity structure or schema, or any task touching more than a couple of files. Do NOT use for typo fixes, CSS tweaks, or single-line…
drupal-module-development
Use when creating or extending Drupal 11 custom modules, including scaffolding, service architecture, and dependency injection best practices.
wp-abilities-verify
A static and runtime checker for WordPress plugin Abilities API registrations. It compares each ability's declared behavior with what its callback actually does, and checks permissions, input schemas, and audit documents.
fastify-best-practices
A reference guide for building Fastify, a Node.js framework for web servers and REST APIs, with JavaScript or TypeScript. It covers routes, plugins, validation, errors, testing, logging, security, databases, and deployment.
wp-abilities-audit
An audit workflow for a WordPress plugin's REST API, the web interface through which software can read and change plugin data. It produces a structured document proposing Abilities API registrations, including permission checks and data shapes.
api-security
Guideline for designing, implementing, and verifying secure APIs following OWASP API Security Top 10 (2023) best practices. Use when the user wants to: (1) review API code or design for security vulnerabilities, (2) design a secure REST, GraphQL, or gRPC API architecture, (3) implement API authentication and…