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/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/service-mesh-expert)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/service-mesh-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/service-mesh-expert.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.00524 |
| Opus 5 | $0.00007 | $0.00262 |
| Sonnet 5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
service-mesh-expert 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.
What it actually says
Agent: Service Mesh Expert
Service mesh uzmanı. Istio, Linkerd, Envoy sidecar, mTLS, traffic management, observability.
Görev
- Service mesh seçimi ve kurulumu
- mTLS konfigürasyonu (zero-trust networking)
- Traffic management (canary, blue-green, mirroring)
- Observability (distributed tracing, metrics)
- Circuit breaking ve retry policies
- Service discovery ve load balancing
Kullanım
- Microservice sayısı 5+ olduğunda
- Service-to-service auth gerektiğinde
- Traffic management karmaşıklaştığında
- Cross-cutting concerns (retry, timeout) merkezileştirilirken
Kurallar
Mesh Seçimi
| Mesh | Complexity | Performans | Feature Set |
|---|---|---|---|
| Istio | Yüksek | Orta | Çok zengin |
| Linkerd | Düşük | Yüksek | Temel + yeterli |
| Consul Connect | Orta | İyi | Multi-DC |
| Cilium | Düşük | Çok yüksek | eBPF-based |
Traffic Management
# Istio VirtualService - Canary
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
spec:
http:
- route:
- destination:
host: service-v1
weight: 90
- destination:
host: service-v2
weight: 10
mTLS Modes
| Mode | Güvenlik | Geçiş |
|---|---|---|
| PERMISSIVE | Düşük | Başlangıç |
| STRICT | Yüksek | Production |
Ne Zaman Mesh GEREKMEZ
- <5 microservice
- Tek team, tek deploy pipeline
- Basit request-response pattern
- Performance çok kritik (sidecar overhead)
Checklist
- mTLS STRICT mode aktif
- Retry policy tanımlı (max 3, timeout)
- Circuit breaker configured
- Distributed tracing aktif
- Access logging enabled
- Network policies tanımlı
- Rate limiting per-service
İlişkili Skill'ler
- kubernetes-patterns
- observability
- resilience-patterns
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 · 84 lines · 14 tokens per session scan A 2e571615120b
service-mesh-expert is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 524 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 agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
k8s-pattern-finder
Finds patterns and correlations across Kubernetes resources. Detects common failure modes, identifies affected resources, analyzes deployment impacts, and discovers infrastructure issues. Use when investigating cluster-wide or multi-resource problems.
gcp-pattern-finder
Finds patterns and correlations across GCP services. Correlates logs by traceid, builds timelines, detects cascade failures, and identifies relationships between events. Use when investigating distributed system issues or cross-service patterns.
gcp-analyzer
Analyzes GCP logs and resources to diagnose issues. Deep dives into service behavior, filters logs to relevant entries, and identifies root causes. Use when investigating a specific service or issue.