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 vignesh2027/AI-AGENT-SKILLS --skill microservices-designgit clone --depth 1 https://github.com/vignesh2027/AI-AGENT-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/vignesh2027/ai-agent-skills/microservices-design)<a href="https://agentmods.dev/skills/vignesh2027/ai-agent-skills/microservices-design"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/microservices-design/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/vignesh2027/ai-agent-skills/microservices-design"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/microservices-design.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.00016 | $0.00520 |
| Opus 5 | $0.00008 | $0.00260 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
microservices-design 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 10d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Microservices solve a people problem (independent team deployments) while creating a technical problem (distributed systems complexity). This skill only adds microservices when they solve a real problem, and designs them to be independently deployable, failure-isolated, and observable.
When to Use
- Before splitting a monolith into services
- When designing a new service in an existing distributed system
- When services are tightly coupled in ways that prevent independent deployment
Process
Step 1: Justify the split
A service split is justified when: teams are blocked on each other's deployments, scaling requirements differ dramatically, or technology requirements differ. Don't split for "separation of concerns" alone — a module achieves that at lower cost.
Step 2: Define service boundaries by business capability
Services should own a business capability end-to-end. Don't split by technical layer (don't make a "user data service" that stores data for 10 other services).
Step 3: Design the interface contract
Services communicate via explicit contracts. Define the contract before implementation. Version it from day one.
Step 4: Choose communication style
- Sync (HTTP/gRPC): Use when caller needs the result immediately
- Async (messaging): Use when caller does not need immediate result; decouples availability
Async is better for resilience; sync is simpler to reason about. Choose based on the requirement.
Step 5: Design for failure isolation
Service A must not fail because Service B is slow or unavailable:
- Timeouts on all outbound calls
- Circuit breakers for repeated failures
- Fallback responses or graceful degradation
- Bulkhead pattern: don't let one failing downstream exhaust connection pools
Step 6: Distributed data
Each service owns its data store. No shared databases. Services that need data from another service: use the API, or replicate via events. Cross-service joins are a design smell.
Step 7: Distributed tracing
All services propagate trace IDs. You must be able to trace a request across all services it touches.
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.
- 10d ago First seen · 56 lines · 16 tokens per session scan A 09f1689bcf5e
microservices-design is a skill published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 12d ago), licensed MIT. It adds 16 tokens to every session and 520 once invoked, about $0.0001 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
telegram
Owner-only Telegram text bridge and Mini App gateway for the existing Ouroboros interface.
api-verification
An API verification workflow that creates both an .http request file and a .cjs JavaScript file, then runs an automation script to test them. An API is an interface through which software exchanges requests and responses.
api-contract-architecture
An architecture guide for public APIs, including HTTP services, software-development kits, command-line tools, schemas, types, errors, pagination, filtering, and compatibility.
backend-domain-architecture
A review guide for backend and business-domain design. It examines business rules, workflows, permissions, APIs, transactions, consistency, repeated requests, compatibility, data boundaries, and service responsibilities.
distributed-systems-architecture
An architecture guide for distributed systems—software split across services that communicate over networks.
external-integration-architecture
A guide for designing connections to outside services such as web APIs, webhooks, and OAuth sign-ins. It focuses on keeping those connections separate and planning for failures.