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 agentmods add rules/kok-o/koko-contextos-agents/microservicesgit clone --depth 1 https://github.com/kok-o/koko-contextos-agentsWhat 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 | $0.00000 | $0.00831 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
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 2d 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 — 159 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
CQRS (Command Query Responsibility Segregation)
Separate read and write models:
Command (Write) → Write Model → Event Store → Projections → Read Model → Query (Read)
When: Read patterns differ significantly from write patterns.
Event Sourcing
Store events, not state:
UserCreated → EmailUpdated → RoleChanged → PasswordReset
Current state = replay all events. Full audit trail.
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.
- 2d 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 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 831 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
clean-code
Apply language-agnostic clean-code discipline to all code writing, editing, reviewing, testing, and refactoring, including file placement, single responsibility, and verified completion.
unity-performance
Cursor rule "unity-performance" from Common-ka/ai-agent-unity-rules, covering unity performance rules, update/fixedupdate/lateupdate, usage rules, object pooling (unityengine.pool) and addressables (not resources).
react-composition-patterns
React composition patterns for scalable component architecture including compound components, context providers, state management, boolean prop alternatives, render props vs children, and React 19 API changes. Use when refactoring components with many boolean props, building component libraries, designing flexible…
react-advanced-patterns
Advanced React patterns for refs, stable callbacks, useEffectEvent, and application initialization. Use when dealing with event handler refs, stable callback references, subscription management, effect dependencies, or one-time app initialization.
general-typescript-rule
Applies general TypeScript best practices and style guidelines to all TypeScript files in the project.
readme-best-practices
README Best Practices - enforces high-quality README patterns when creating or editing README files.