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 sawrus/agent-guides --skill service-meshgit clone --depth 1 https://github.com/sawrus/agent-guidesWrote 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/sawrus/agent-guides/service-mesh)<a href="https://agentmods.dev/skills/sawrus/agent-guides/service-mesh"><img src="https://agentmods.dev/badge/skills/sawrus/agent-guides/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/sawrus/agent-guides/service-mesh"><img src="https://agentmods.dev/badge/skills/sawrus/agent-guides/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.00027 | $0.01226 |
| Opus 5 | $0.00014 | $0.00613 |
| Sonnet 5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade C, and why
service-mesh scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl --proto '=https' --tlsv1.2 -sSfL https://run.linkerd.io/install | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --proto '=https' --tlsv1.2 -sSfL https://run.linkerd.io/install | sh How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Service Mesh
Expertise: Istio and Linkerd installation, mTLS enforcement, traffic shifting, circuit breakers, retry policies, observability.
When to load
When implementing service-to-service mTLS, traffic shifting for canary deploys, circuit breakers, or setting up mesh-level observability.
Linkerd (lightweight — recommended for bare-metal K8s)
# Install Linkerd CLI
curl --proto '=https' --tlsv1.2 -sSfL https://run.linkerd.io/install | sh
# Pre-flight check
linkerd check --pre
# Install Linkerd (cert-manager manages control plane certs)
linkerd install --crds | kubectl apply -f -
linkerd install \
--set identity.externalCA=true \
--set identity.issuer.scheme=kubernetes.io/tls \
| kubectl apply -f -
# Install observability extension (Prometheus + Grafana)
linkerd viz install | kubectl apply -f -
# Verify
linkerd check
Linkerd: Inject Sidecar
# Namespace-level injection (all pods in namespace get sidecar)
metadata:
annotations:
linkerd.io/inject: enabled
# Per-deployment injection
spec:
template:
metadata:
annotations:
linkerd.io/inject: enabled
# Skip injection for a specific pod (e.g., database, cronjob)
metadata:
annotations:
linkerd.io/inject: disabled
Linkerd: Traffic Policies
# Retry policy (retry on 5xx up to 3 times)
apiVersion: policy.linkerd.io/v1beta3
kind: HTTPRoute
metadata:
name: order-service-retries
namespace: production
spec:
parentRefs:
- name: order-service
kind: Service
group: core
port: 8080
rules:
- filters:
- type: RequestRedirect # or RequestMirror, URLRewrite
backendRefs:
- name: order-service
port: 8080
---
# Timeout policy
apiVersion: policy.linkerd.io/v1alpha1
kind: ServiceProfile
metadata:
name: order-service.production.svc.cluster.local
namespace: production
spec:
routes:
- name: POST /orders
condition:
method: POST
pathRegex: /orders
timeout: 5s
retryBudget:
retryRatio: 0.2 # retry up to 20% of requests
minRetriesPerSecond: 10
ttl: 10s
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 · 207 lines · 27 tokens per session scan C a6f3e77e9e44
service-mesh is a skill published in the GitHub repository sawrus/agent-guides (17 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 1,226 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
apify-actor-development
Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
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.
fly-io
Fly.io edge platform with global distribution. Use for edge deployment.
nomad
HashiCorp Nomad workload orchestration. Use for job scheduling.
traefik
Traefik cloud-native reverse proxy. Use for container networking.