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.
git clone --depth 1 https://github.com/kok-o/koko-contextos-agentsWrote 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/rules/kok-o/koko-contextos-agents/microservices)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/microservices"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/microservices/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/rules/kok-o/koko-contextos-agents/microservices"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/microservices.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.00000 | $0.00999 |
| Opus 5.5 | $0.00000 | $0.00400 |
| Sonnet 5.5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
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 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Microservices
Microservices
Overview
A brief summary of what the skill does and its core philosophy.
When to Use
Context for when this skill is applicable.
Rules & Patterns
Microservices — Architecture Guide
When to Use Microservices
Use when:
- Team > 10 engineers working on the same product
- Independent deployment of components is critical
- Different components have different scaling needs
- Different components need different tech stacks
Don't use when:
- Small team (< 5 engineers)
- MVP or prototype
- No operational expertise (monitoring, tracing, deployment)
- Tight coupling between components
Core Principles
1. Single Responsibility
Each service does ONE thing well.
2. Own Your Data
Each service has its own database. No shared databases.
3. API Contracts
Services communicate through well-defined APIs. Internal implementation is hidden.
4. Autonomous Deployment
Each service can be deployed independently.
Communication Patterns
Synchronous (REST/gRPC)
- When: Request needs immediate response
- Tools: REST (HTTP), gRPC (high-performance)
- Risk: Cascading failures, latency accumulation
Asynchronous (Events/Messages)
- When: Eventual consistency is acceptable
- Tools: Kafka, RabbitMQ, Redis Streams, AWS SQS
- Benefit: Loose coupling, resilience
Saga Pattern (Distributed Transactions)
Order Service → Payment Service → Inventory Service → Shipping Service
↓ (failure)
Compensating transactions reverse each step
- Choreography (Event-Driven): Each service emits events, downstream services listen and react. Best for simple flows (≤ 3 steps) where a central coordinator adds unnecessary coupling.
- Orchestration (State Machine): A dedicated Saga Orchestrator controls the flow and explicitly triggers compensating transactions on failure (e.g.,
RefundPayment,ReleaseInventoryReservation). Mandatory for complex multi-step workflows.
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 Changed · +9 lines f4704b260859
- 1mo ago First seen · 159 lines · 0 tokens per session scan A 820b2fdc7179
microservices is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 999 tokens. 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 cursor rules, from other repositories
validate-contracts
Assert data shape consistency across system boundaries — live API responses against JSON Schema, key-set comparison across layers, data shape validation for migrations and exports. Catches silent data corruption before deploy.
hatch3r-resilience-patterns
Resilience patterns in user code — circuit breakers, retry with decorrelated jitter, timeouts with deadline propagation, idempotency keys, bulkheads, hedged requests.
hatch3r-contract-testing
Consumer-driven and spec-driven contract testing between services — Pact, Schemathesis, Dredd, pact-broker can-i-deploy gate.
hatch3r-api-design
REST, GraphQL, and gRPC contract patterns covering versioning, auth, CORS, pagination, webhooks, rate limiting, and security headers.
hatch3r-auth-patterns
Authentication and authorization patterns for end-user apps — OAuth 2.1, OIDC, DPoP, JWT rotation, cookie security, RBAC vs ABAC vs ReBAC rubric.
hatch3r-enhancability
CQ9 Enhancability Quality measurement rule — feature-flag adoption on user-visible behavior, config externalization, API versioning + deprecation policy, forward-compat patterns, extension-point definition.