microservices

microservices is a skill for Claude Code from krzysztofsurdy/code-virtuoso. It costs 90 tokens per session (1,671 once invoked), scanned A, original, MIT.

Guidance for microservices and distributed systems, where an application is split into independently deployable services. It covers service boundaries, communication, reliability, gateways, and data consistency.

In plain words
What is it for?
Use it to decide between a monolith and microservices, split a system into services, design sagas or event-driven workflows, apply CQRS, add circuit breakers, or plan API gateways.
Why use it?
It helps teams judge when separate services are justified and manage the added complexity when they are used.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the knowledge-virtuoso plugin — 15 skills shipped together

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/krzysztofsurdy/code-virtuoso/microservices
Any agent
npx skills add krzysztofsurdy/code-virtuoso --skill microservices
Clone the repo
git clone --depth 1 https://github.com/krzysztofsurdy/code-virtuoso

Made for: Claude Code.

Or install knowledge-virtuoso, the plugin that ships this one along with the rest of its 15 skills.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/microservices.svg)](https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/microservices)
Your own site
<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/microservices"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/microservices.svg" alt="Measured on agentmods" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,671 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.1 $0.00090 $0.01671
Opus 5 $0.00045 $0.00835
Sonnet 5 $0.00018 $0.00334
Haiku 4.5 $0.00009 $0.00167

Measured 6d ago against content hash 61e5dff635bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

microservices 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 6d 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.

skills/knowledge/microservices/SKILL.md · 132 lines

How it starts

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

Microservices and Distributed Systems

Microservices architecture splits a system into independently deployable services, each owning a specific business capability. This approach trades the simplicity of a monolith for flexibility in scaling, deployment, and technology choice - but only when the organizational and technical complexity is justified.

When to Use Microservices vs Monolith

There is no universal answer. The decision depends on team size, domain complexity, and operational maturity.

Factor Monolith Favored Microservices Favored
Team size Small team (fewer than 10 developers) Multiple autonomous teams that need independent release cycles
Domain complexity Simple or poorly understood domain Well-understood domain with clear bounded contexts
Deployment cadence Infrequent releases are acceptable Different parts of the system need to ship at different speeds
Scaling needs Uniform load across the application Specific components need independent scaling
Operational maturity Limited infrastructure automation Mature CI/CD, monitoring, and container orchestration
Data isolation Shared database is manageable Services need independent data stores and schemas

Start monolithic unless you have a clear reason not to. A well-structured modular monolith can be decomposed later. A premature microservices architecture adds distributed systems complexity without proportional benefit.


Service Decomposition Strategies

Deciding where to draw service boundaries is the hardest part. Get it wrong and you end up with a distributed monolith - all the costs of distribution with none of the benefits.

By Business Capability

Align services to what the organization does rather than how the software is structured. Each service maps to a business function: order management, inventory, billing, notifications. Services change when the business capability they represent changes.

Read the full file on GitHub · 132 lines

Files

What ships with it

3 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. 6d ago First seen · 132 lines · 90 tokens per session scan A 61e5dff635bb

Subscribe to this mod's changes

microservices is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (20 stars, last pushed 3mo ago), licensed MIT. It adds 90 tokens to every session and 1,671 once invoked, about $0.0005 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.