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/alexmmatos/arthur-mcpWrote 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/agents/alexmmatos/arthur-mcp/microservices-architect)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/microservices-architect"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/microservices-architect.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.00031 | $0.01222 |
| Opus 5 | $0.00015 | $0.00611 |
| Sonnet 5 | $0.00006 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
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 4d 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 — 239 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 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.
- 4d ago First seen · 239 lines · 31 tokens per session scan A abd12f9568ed
microservices-architect is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,222 once invoked, about $0.0002 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 agents, from other repositories
FAI Azure APIM Expert
Azure API Management specialist — AI Gateway patterns, semantic caching, token metering, multi-backend load balancing, circuit breaker, rate limiting, and FinOps for LLM API layers.
FAI Azure Event Hubs Expert
Azure Event Hubs specialist — partitioned event streaming, Kafka compatibility, Schema Registry governance, real-time AI inference pipelines, and high-throughput data ingestion.
FAI Azure Functions Expert
Azure Functions specialist — event-driven AI processing, Durable Functions for long-running agent orchestration, timer triggers for batch inference, and cold start optimization.
FAI Azure Service Bus Expert
Azure Service Bus specialist — queues, topics/subscriptions, dead-letter handling, session-based ordered messaging, saga patterns, and agent-to-agent communication for AI workflows.
timps_service_mesh_configurator
Generate production-grade service-mesh config (Istio / Linkerd / Consul) — mTLS, traffic policies, retries, circuit-breakers, observability, multi-cluster, and a migration plan. Use the timpsservicemeshconfigurator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.