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 skills add G1Joshi/Agent-Skills --skill service-meshgit 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/service-mesh)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/service-mesh"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/service-mesh/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/g1joshi/agent-skills/service-mesh"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/service-mesh.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.00017 | $0.00399 |
| Opus 5 | $0.00009 | $0.00199 |
| Sonnet 5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
service-mesh 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 8d 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
Service Mesh
A Service Mesh is a dedicated infrastructure layer for handling service-to-service communication. It's usually implemented as lightweight network proxies (Sidecars) deployed alongside the application code.
When to Use
- Mature Microservices: You have 20+ services and managing retries, timeouts, and auth in each language is becoming a nightmare.
- Zero Trust Security: You need mTLS (Mutual TLS) between all services.
- Observability: You need uniform metrics (Gold signals) and tracing across a polyglot stack.
Core Concepts
Sidecar Proxy
The mesh injects a proxy (e.g., Envoy) next to your app container. Your app talks to localhost, the proxy handles the network magic.
Control Plane
The brain that configures the proxies (e.g., Istio Control Plane).
Data Plane
The set of proxies that actually route the traffic.
Features
- Traffic Management: Canary deployments (1% traffic to v2), Circuit Breaking, Retries.
- Security: mTLS rotation, Authorization policies.
- Observability: Automatic metrics (latency, success rate) without code changes.
Best Practices
Do:
- Assess if the Complexity is worth it. For small clusters, it's overkill.
- Use simpler alternatives (Linkerd) if Istio is too heavy.
- Start with Observability features before enabling strict enforcement/mTLS.
Don't:
- Don't use a Service Mesh to fix bad application code.
- Don't ignore the resource overhead (CPU/RAM) of sidecars at scale.
References
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.
- 8d ago First seen · 54 lines · 17 tokens per session scan A a66a412b4d7c
service-mesh is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 399 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
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…
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"…
tdd-explore-ideas
Systematic codebase exploration, architectural critique, and 5-step Idea Assessment with TDD hypothesis verification for Phase 0.
laravel-expert
Laravel & PHP Development Instructions for GitHub Copilot.
orchestrate
Drive a plan to completion by orchestrating implementer, reviewer, and critic agents across waves of parallel work. Use when the user says "orchestrate", "implement this plan", "execute plan", "drive this", or approves a plan for execution.