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 agentmods add skills/melodic-software/claude-code-plugins/observabilitynpx skills add melodic-software/claude-code-plugins --skill observabilitygit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWhat 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 | $0.00082 | $0.02014 |
| Opus 5 | $0.00041 | $0.01007 |
| Sonnet 5 | $0.00016 | $0.00403 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
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 2d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
Current branch: !git branch --show-current 2>/dev/null || echo "unknown"
Repo slug: !git rev-parse --show-toplevel >/dev/null 2>&1 && git rev-parse --show-toplevel 2>/dev/null | sed 's|.*/||' || echo "(git toplevel unavailable)"
ccusage availability: !command -v npx >/dev/null 2>&1 && echo "npx present" || echo "npx MISSING"
Hook event log: !bash "${CLAUDE_PLUGIN_ROOT}/skills/observability/scripts/probe-observability-state.sh" --hook-events 2>/dev/null || echo "unknown"
OTEL collector :4318: !bash -c 'source "${CLAUDE_PLUGIN_ROOT}/skills/observability/otel/net-probe.sh" && port_status 4318' 2>/dev/null || echo unknown
OTEL store: !bash "${CLAUDE_PLUGIN_ROOT}/skills/observability/scripts/probe-observability-state.sh" --otel-store 2>/dev/null || echo "unknown"
Purpose
Single place to read Claude Code observability, where to read telemetry, how the
collector/dashboard/store fit together, and cross-session trend reports. CC shorthand =
Claude Code CLI. See context/operator-setup.md "Naming".
Progressive disclosure lives in context/ (read on demand. Do not recap inline).
Read-only, never writes user-visible state except a report file under
${CLAUDE_PLUGIN_DATA}/reports/ (when --write is passed). Honors
context/privacy.md.
Not /claude-ops:known-issues. That skill tracks Anthropic product bugs and GitHub issues.
This skill reads your captured telemetry and ops signals.
Context ladder (read on demand)
| File | When |
|---|---|
| context/read-routing.md | Ad-hoc "which source for this question?" |
| context/otel-pipeline.md | Collector/dashboard down, store empty, service health |
| context/otel-queries.md | DuckDB SQL, Aspire CLI, views |
| context/operator-setup.md | Install, env profile, retention scripts |
| context/operator-setup-collector-daemon.md | Collector/Aspire service down or unhealthy, lifecycle repair |
| context/operator-setup-retention.md | Prune mechanics, retention knobs, scheduled prune task |
| context/operator-setup-emission-privacy.md | Emission tiers, content-capture keys, privacy toggle |
| context/data-sources.md | JSONL + ccusage jq (batch reports) |
| context/output-format.md | Rendering scope reports |
| context/privacy.md | Before any user-visible output |
What ships with it
23 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- claude-observability.test.sh 15 KB runs code
- context/data-sources.md 10 KB
- context/operator-setup-collector-daemon.md 2.6 KB
- context/operator-setup-emission-privacy.md 3.8 KB
- context/operator-setup-retention.md 7.6 KB
- context/operator-setup.md 2.3 KB
- context/otel-pipeline.md 2.7 KB
- context/otel-queries.md 5.6 KB
- context/output-format.md 5.2 KB
- context/privacy.md 3.8 KB
- context/read-routing.md 4.5 KB
- evals/evals.json 3.6 KB
- otel/cc-otel.sql 16 KB
- otel/net-probe.sh 2.3 KB runs code
- otel/net-probe.test.sh 3.1 KB runs code
- otel/prune-collector-lifecycle.sh 4.0 KB runs code
- otel/prune-compact.sh 8.2 KB runs code
- otel/prune-filter.awk 1.4 KB
- otel/prune-otel-store.sh 16 KB runs code
- otel/prune-otel-store.test.sh 39 KB runs code
- scripts/clean.sh 13 KB runs code
- scripts/probe-observability-state.sh 3.4 KB runs code
- scripts/probe-observability-state.test.sh 8.2 KB runs code
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.
- 2d ago First seen · 149 lines · 82 tokens per session scan A 77cfb8a50685
observability is a skill published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 2,014 once invoked, about $0.0004 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 skills, from other repositories
deep-research
Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…
error-ux
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.
adversarial-patterns
Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.
documentation-testing
Provides heuristics for identifying incomplete or broken documentation. Use when validating README setup instructions, testing onboarding flows, or auditing documentation quality. Triggers: docs, readme, onboarding, setup validation, documentation audit.
adversarial-analysis
Analyze code to identify explicit contracts, implicit usage patterns, and realistic boundary conditions. Contains concrete formulas for calculating input realism limits. Use before generating adversarial tests.
propagate-then-search
For constraint problems: eliminate impossibilities before guessing, reduce search space through inference, fail fast on contradictions.