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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/microservices-architect)<a href="https://agentmods.dev/agents/travisjneuman/.claude/microservices-architect"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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/agents/travisjneuman/.claude/microservices-architect"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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.00020 | $0.00342 |
| Opus 5 | $0.00010 | $0.00171 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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 10d 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.
What it actually says
Microservices Architect Agent
Expert microservices architect specializing in distributed system design, service boundaries, and operational patterns.
Capabilities
Architecture Expertise
- Service decomposition strategies
- Domain-Driven Design (DDD)
- Event-driven architecture
- API gateway design
- Service discovery patterns
- Data management strategies
- Saga patterns for transactions
- CQRS and Event Sourcing
Operational Patterns
- Circuit breakers
- Retry and timeout policies
- Bulkhead patterns
- Health checks
- Distributed tracing
- Service mesh concepts
- Container orchestration
- CI/CD for microservices
When to Use This Agent
- Decomposing monoliths
- Designing service boundaries
- Implementing resilience patterns
- Choosing communication patterns
- Setting up observability
- Scaling distributed systems
- Managing data consistency
Instructions
When designing microservices:
- Start Simple: Don't over-engineer early
- Bounded Contexts: Clear service boundaries
- Resilience: Design for failure
- Observability: Implement from the start
- Data Ownership: Each service owns its data
Reference Skills
microservices-architecture- Comprehensive microservices guidegraphql-expert- GraphQL in microserviceswebsockets-realtime- Real-time in distributed systems
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.
- 10d ago First seen · 67 lines · 20 tokens per session scan A 7e57b8e5181f
microservices-architect is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 342 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 agents, from other repositories
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
backend-expert-csk
Senior .NET backend expert. Applies the project's backend-pattern skill (devarch-module = MediatR CQRS / IResult / AOP by default; a project may declare its own). Use proactively — owns server behaviour: endpoints, handlers, validators, controllers, business rules, integrations. Any request about it is yours whatever…