service-mesh-observability

service-mesh-observability is a skill for Claude Code, Codex from NOMARJ/sigil. It costs 43 tokens per session (2,571 once invoked), scanned A, a copy of service-mesh-observability, Apache-2.0.

Service-mesh observability tracks communication between services using metrics, traces, and logs. A service mesh is infrastructure that manages service-to-service traffic in a distributed application.

In plain words
What is it for?
Use it to monitor Istio or Linkerd, trace service calls, create mesh dashboards, troubleshoot connectivity, and define service-level objectives.
Why use it?
It helps reveal slow requests, broken connections, dependency problems, and error patterns that are difficult to see from one service alone.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to monitor Istio or Linkerd, trace service calls, create mesh dashboards, troubleshoot connectivity, and define service-level objectives.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nomarj/sigil/service-mesh-observability
Install

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.

Any agent
npx skills add NOMARJ/sigil --skill service-mesh-observability
Clone the repo
git clone --depth 1 https://github.com/NOMARJ/sigil

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for service-mesh-observability

README.md
[![agentmods](https://agentmods.dev/badge/skills/nomarj/sigil/service-mesh-observability/github.svg)](https://agentmods.dev/skills/nomarj/sigil/service-mesh-observability)
Your own site
<a href="https://agentmods.dev/skills/nomarj/sigil/service-mesh-observability"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/service-mesh-observability/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.

agentmods 80×15 button for service-mesh-observability

Your own site · 80×15
<a href="https://agentmods.dev/skills/nomarj/sigil/service-mesh-observability"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/service-mesh-observability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,571 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.02571
Opus 5 $0.00022 $0.01286
Sonnet 5 $0.00009 $0.00514
Haiku 4.5 $0.00004 $0.00257

Measured 7d ago against content hash 13cd4fef15b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

service-mesh-observability 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 7d 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.

Origin

This is a copy

86% identical to service-mesh-observability — 325 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

packs/infra/skills/cloud/service-mesh-observability/SKILL.md · 386 lines

How it starts

The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Service Mesh Observability

Complete guide to observability patterns for Istio, Linkerd, and service mesh deployments.

When to Use This Skill

  • Setting up distributed tracing across services
  • Implementing service mesh metrics and dashboards
  • Debugging latency and error issues
  • Defining SLOs for service communication
  • Visualizing service dependencies
  • Troubleshooting mesh connectivity

Core Concepts

1. Three Pillars of Observability

┌─────────────────────────────────────────────────────┐
│                  Observability                       │
├─────────────────┬─────────────────┬─────────────────┤
│     Metrics     │     Traces      │      Logs       │
│                 │                 │                 │
│ • Request rate  │ • Span context  │ • Access logs   │
│ • Error rate    │ • Latency       │ • Error details │
│ • Latency P50   │ • Dependencies  │ • Debug info    │
│ • Saturation    │ • Bottlenecks   │ • Audit trail   │
└─────────────────┴─────────────────┴─────────────────┘

2. Golden Signals for Mesh

Signal Description Alert Threshold
Latency Request duration P50, P99 P99 > 500ms
Traffic Requests per second Anomaly detection
Errors 5xx error rate > 1%
Saturation Resource utilization > 80%

Templates

Template 1: Istio with Prometheus & Grafana

# Install Prometheus
apiVersion: v1
kind: ConfigMap
metadata:
  name: prometheus
  namespace: istio-system
data:
  prometheus.yml: |
    global:
      scrape_interval: 15s
    scrape_configs:
      - job_name: 'istio-mesh'
        kubernetes_sd_configs:
          - role: endpoints
            namespaces:
              names:
                - istio-system
        relabel_configs:
          - source_labels: [__meta_kubernetes_service_name]
            action: keep
            regex: istio-telemetry
---
# ServiceMonitor for Prometheus Operator
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: istio-mesh
  namespace: istio-system
spec:
  selector:
    matchLabels:
      app: istiod
  endpoints:
    - port: http-monitoring
      interval: 15s

Read the full file on GitHub · 386 lines

Changes

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.

  1. 7d ago First seen · 386 lines · 43 tokens per session scan A 13cd4fef15b0

Subscribe to this mod's changes

service-mesh-observability is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,571 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to service-mesh-observability, differing in 325 lines, and is treated as a copy.

Related

Other skills, from other repositories

d3k

Use when the user asks to use d3k, run/dev/test/debug a web project with d3k, or reproduce a browser issue. Own the runtime: reuse or background-start d3k non-interactively, wait for readiness, use its project-stable managed Chrome profile, and inspect unified browser/server evidence.

vercel-labs/dev3000 · 68 tokens

devtools-bidirectional

Two-way event patterns between devtools panel and application. App-to-devtools observation, devtools-to-app commands, time-travel debugging with snapshots and revert. structuredClone for snapshot safety, distinct event suffixes for observation vs commands, serializable payloads only.

TanStack/devtools · 59 tokens

net

A toolkit for diagnosing network connections and traffic in embedded systems. A packet capture is a recorded sample of network traffic, and this tool can create or analyze captures in formats such as pcap and pcapng.

zhinkgit/embeddedskills · 234 tokens

serial

A tool for communicating with devices over serial ports, such as USB-to-UART connections. It can find ports, watch incoming data, send messages, save logs, and display raw bytes in hexadecimal form.

zhinkgit/embeddedskills · 137 tokens

devtools-instrumentation

Analyze library codebase for critical architecture and debugging points, add strategic event emissions. Identify middleware boundaries, state transitions, lifecycle hooks. Consolidate events (1 not 15), debounce high-frequency updates, DRY shared payload fields, guard emit() for production. Transparent server/client…

TanStack/devtools · 64 tokens

can

A debugging tool for CAN and CAN-FD, communication systems used by vehicles and embedded devices. It can find interfaces, monitor and send messages, record logs, decode DBC database files, and report bus statistics.

zhinkgit/embeddedskills · 168 tokens