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 skills/g1joshi/agent-skills/microservicesnpx skills add G1Joshi/Agent-Skills --skill microservicesgit clone --depth 1 https://github.com/G1Joshi/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/g1joshi/agent-skills/microservices)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/microservices"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/microservices.svg" alt="Measured on agentmods" 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.00014 | $0.00715 |
| Opus 5 | $0.00007 | $0.00358 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00072 |
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 5d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microservices
Microservices architecture structures an application as a collection of loosely coupled, independently deployable services. Ideally, each service corresponds to a Bounded Context (DDD).
When to Use
- Large teams (50+ devs) where coordination on a monolith slows down deployment.
- Modules have conflicting resource requirements (e.g., one needs huge RAM, another needs GPU).
- Need to scale specific parts of the system independently.
- 2025 Reality check: Don't start with Microservices. Start with a Modular Monolith.
Quick Start
# docker-compose.yml (Simulated Microservices)
services:
order-service:
build: ./services/order
ports: ["3001:3000"]
environment:
- DB_HOST=order-db
inventory-service:
build: ./services/inventory
ports: ["3002:3000"]
api-gateway:
image: nginx
ports: ["80:80"]
depends_on:
- order-service
- inventory-service
Core Concepts
Independence
Each service owns its own data. Service A cannot query Service B's database directly; it must ask Service B via API.
Inter-Service Communication
- Synchronous: HTTP/REST or gRPC (Request/Response). Tightly coupled in time.
- Asynchronous: Message Queues (RabbitMQ, Kafka, SQS). Decoupled in time.
Database per Service
Ensures loose coupling. If a service needs data from another, use data replication (Events) or API composition.
Common Patterns
API Gateway
A single entry point for all clients. Handles routing, auth, rate limiting, and aggregation.
Circuit Breaker
Detects failures and prevents the application from trying to perform the action that is doomed to fail (e.g., external service down), protecting the system.
Saga Pattern
Managing distributed transactions. Since you can't have ACID across services, use Sagas (sequence of local transactions) with compensating actions for rollbacks.
Best Practices
Do:
- Automate CI/CD and Infrastructure as Code (Terraform/K8s). You can't manage 50 services manually.
- Implement Distributed Tracing (OpenTelemetry) immediately.
- Define clear Service Boundaries (use DDD).
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.
- 5d ago First seen · 95 lines · 14 tokens per session scan A cbcc484ae9c9
microservices is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 715 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-30.
Other skills, from other repositories
image-describe
Describe the contents of an image file or URL in structured detail.
pake
Package any website or local web build into a lightweight desktop app using Pake (Tauri/Rust). Use when the user wants to: wrap a URL as a native app, build a desktop app from a website or a local dist/ folder, use Pake CLI to package a page, set up proxy for a packaged app, customize app icons or bundle IDs, or…
ux
LobeHub product design values / principles / checklists. Use whenever the work touches user-interface features or implementation — designing or building any user-facing flow — to get better UX results.
agent-work
Agent Work registry (works / workversions): how agent outputs — github/linear entities, files, documents, tasks — get registered, deduped, and rendered as cards, and how to extend it with a new skill provider, a new shell CLI scanner, or a new Work type.
skills-audit
Audit .agents/skills SKILL.md files. Use for recurring checks of duplicate, overlapping, stale, inconsistent, or broken skills and merge/delete candidates.
ponytail-lazy-senior-dev
Applies the "lazy senior developer" mindset. Use this skill whenever generating, modifying, reviewing code, or fixing bugs to prioritize code reuse, minimalism, YAGNI principles, and root-cause fixes. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni"…