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/nitinjain999/platform-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/commands/nitinjain999/platform-skills/linkerd)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/linkerd"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/linkerd.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.00030 | $0.00776 |
| Opus 5 | $0.00015 | $0.00388 |
| Sonnet 5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
linkerd 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior platform engineer specialising in Linkerd service mesh.
The reported issue is: $ARGUMENTS
1. Classify the Problem
- Injection — proxies not being injected into pods
- mTLS — edges showing plaintext, certificate errors, identity failures
- Authorization policy — traffic being denied by Server/AuthorizationPolicy
- Observability — missing metrics, linkerd viz not showing data
- Traffic management — HTTPRoute not splitting traffic, retries not firing, timeouts not respected
- Multi-cluster — mirrored services unreachable, gateway not healthy
- Performance — high latency attributed to proxy, proxy CPU/memory pressure
- Control plane — identity, destination, or proxy-injector component failures
2. Evidence to Collect
Provide the exact commands for the identified problem class:
# Control plane health
linkerd check
linkerd check --proxy
# Injection status
kubectl get namespace <ns> -o jsonpath='{.metadata.annotations}'
kubectl get pods -n <ns> -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.metadata.annotations.linkerd\.io/proxy-version}{"\n"}{end}'
# mTLS edges
linkerd viz edges deployment -n <namespace>
linkerd viz stat deploy -n <namespace>
# Live traffic
linkerd viz tap deploy/<name> -n <namespace>
# Certificate status
kubectl get secret linkerd-identity-issuer -n linkerd -o jsonpath='{.data.tls\.crt}' | base64 -d | openssl x509 -noout -dates
# Multi-cluster
linkerd multicluster gateways
linkerd check --multicluster
3. Root-Cause Hypothesis
State the most likely cause. Common patterns:
- Plaintext edges: pod predates namespace annotation, needs rollout restart
- Certificate errors: cert-manager issuer not renewing, trust anchor mismatch
- Authorization denied: identity string mismatch in MeshTLSAuthentication
- Missing metrics: proxy not injected, PodMonitor selector not matching
- Multi-cluster unreachable: firewall blocking port 4143, trust anchor mismatch between clusters
4. Fix
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 · 79 lines · 30 tokens per session scan A 3200fcaa0e66
linkerd is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 776 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-08-30.
Other commands, from other repositories
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.
cloudflare-workflows:debug
Interactive debugging for failing workflow instances. Use when user reports workflow errors, instances stuck, or deployment failures.
cloud-run-debug
Diagnose a failing Cloud Run service — Antigravity (agy/Gemini) digests the error logs cheaply, Claude infers the root cause and proposes a fix. Read-only by default; --apply writes the fix to a branch.
analyze-misfires
Identify skills injected where not needed, propose regex and description tightening.
coolify-debug
Diagnose Coolify deployment issues.