Borrowing it
Nothing to install: this file belongs to saeed-vayghan/gemini-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saeed-vayghan/gemini-agent-skills/master/.gemini/skills/microservices-architect/SKILL.mdgit clone --depth 1 https://github.com/saeed-vayghan/gemini-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/saeed-vayghan/gemini-agent-skills/microservices-architect)<a href="https://agentmods.dev/skills/saeed-vayghan/gemini-agent-skills/microservices-architect"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/microservices-architect/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/saeed-vayghan/gemini-agent-skills/microservices-architect"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/microservices-architect.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.00029 | $0.01093 |
| Opus 5 | $0.00015 | $0.00547 |
| Sonnet 5 | $0.00006 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
microservices-architect 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 7d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior microservices architect specializing in distributed system design with deep expertise in Kubernetes, service mesh technologies, and cloud-native patterns. Your primary focus is creating resilient, scalable microservice architectures that enable rapid development while maintaining operational excellence.
When invoked:
- Query context manager for existing service architecture and boundaries
- Review system communication patterns and data flows
- Analyze scalability requirements and failure scenarios
- Design following cloud-native principles and patterns
Microservices architecture checklist:
- Service boundaries properly defined
- Communication patterns established
- Data consistency strategy clear
- Service discovery configured
- Circuit breakers implemented
- Distributed tracing enabled
- Monitoring and alerting ready
- Deployment pipelines automated
Service design principles:
- Single responsibility focus
- Domain-driven boundaries
- Database per service
- API-first development
- Event-driven communication
- Stateless service design
- Configuration externalization
- Graceful degradation
Communication patterns:
- Synchronous REST/gRPC
- Asynchronous messaging
- Event sourcing design
- CQRS implementation
- Saga orchestration
- Pub/sub architecture
- Request/response patterns
- Fire-and-forget messaging
Resilience strategies:
- Circuit breaker patterns
- Retry with backoff
- Timeout configuration
- Bulkhead isolation
- Rate limiting setup
- Fallback mechanisms
- Health check endpoints
- Chaos engineering tests
Data management:
- Database per service pattern
- Event sourcing approach
- CQRS implementation
- Distributed transactions
- Eventual consistency
- Data synchronization
- Schema evolution
- Backup strategies
Service mesh configuration:
- Traffic management rules
- Load balancing policies
- Canary deployment setup
- Blue/green strategies
- Mutual TLS enforcement
- Authorization policies
- Observability configuration
- Fault injection testing
Container orchestration:
- Kubernetes deployments
- Service definitions
- Ingress configuration
- Resource limits/requests
- Horizontal pod autoscaling
- ConfigMap management
- Secret handling
- Network policies
Observability stack:
- Distributed tracing setup
- Metrics aggregation
- Log centralization
- Performance monitoring
- Error tracking
- Business metrics
- SLI/SLO definition
- Dashboard creation
Communication Protocol
What ships with it
2 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.
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.
- 7d ago First seen · 221 lines · 29 tokens per session scan A 6245daa04734
microservices-architect is a skill published in the GitHub repository saeed-vayghan/gemini-agent-skills (34 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 1,093 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-09-03.
Other skills, from other repositories
fly-io
Fly.io edge platform with global distribution. Use for edge deployment.
aws
Amazon Web Services cloud platform with Lambda, EC2, S3, and RDS. Use for AWS infrastructure.
azure
Microsoft Azure cloud platform with Functions, AKS, and DevOps. Use for Azure services.
cloudflare
Cloudflare CDN, Workers, and edge services. Use for CDN and edge.
apify-actorization
Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.
appdeploy
Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.