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 paultyng/skill-issue --skill review-observabilitygit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/review-observability)<a href="https://agentmods.dev/skills/paultyng/skill-issue/review-observability"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/review-observability.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.00071 | $0.01905 |
| Opus 5 | $0.00036 | $0.00953 |
| Sonnet 5 | $0.00014 | $0.00381 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
review-observability scanned grade A with 1 finding 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Findings must cite probed evidence (`path:line`, grep output, command result), not pattern-matched suspicion. Per `~/.claude/rules/probe-not-assume.md`. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Review
Structured review of logging, metrics, and tracing sufficiency. Producing actionable, prioritized findings with code-level references.
Out of scope (defer to siblings):
- Health/readiness probes, gRPC health, retry/timeout semantics →
review-reliability - Log injection, PII leakage, log-as-attack-channel →
review-security(but flag obvious secret-in-log here as well) - Dashboard / alert authoring (where to set thresholds) → typically out of scope; observability review covers signal availability, not alert tuning
Workflow
1. Scope and explore
- Confirm scope with the user: full codebase, specific packages/directories, changed files only (PR or branch diff), or specific concern.
- Resolve scope to a file/package list. Based on what the user requested:
- Changed files (PR or branch): Run
git diff --name-only --diff-filter=d <base>...HEAD. If the user references a PR number, usegh pr diff <number> --name-only. Filter to source files (.go,.ts,.tsx,.js,.py, etc.) and configs (prometheus.yml,otel-collector-config.yaml). - Explicit paths/packages: Include all files under given directories.
- Full codebase: No filtering.
- Changed files (PR or branch): Run
- If invoked from review-all: receive
file_list,package_paths,has_changes,base_ref,REVIEW_DIR, andpr_urlfrom the orchestrator. Skip your own scope confirmation. - Pass the resolved scope to all exploration and investigation subagents.
2. System overview
Produce a brief telemetry summary covering:
- Logging library/sink: structured (
slog,zap,zerolog,logrus) vs. unstructured (fmt.Println,log.Printf). Output sink (stdout, file, syslog, log aggregator). - Metrics library/exporter: Prometheus client, OTel metrics, statsd. Where scraping happens.
- Tracing library/exporter: OTel tracer, vendor-specific (Datadog, Honeycomb, Jaeger). Sampling strategy.
- Correlation: are trace IDs threaded through logs (e.g.
slog.With("trace_id", ...))? Are span context propagated across RPC boundaries (otelgrpc,otelhttp)? - Collector / pipeline: is there an OTel Collector in the path? What processors and exporters?
What ships with it
1 file 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.
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.
- 7d ago First seen · 159 lines · 71 tokens per session scan A f900aa7f472c
review-observability is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 27d ago), licensed MIT. It adds 71 tokens to every session and 1,905 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…
assistant
Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; use agent-toolkit CLI when needed.
design-improvement
WHAT - Browser-grounded iterative design improvement. Consumes design-assessment findings, defines direction, prioritizes safe vs ambiguous changes, implements within existing design system, runs app, captures rendered evidence via browser, reviews and iterates. Reuses evidence model — no new scoring framework.
codeql
CodeQL operational workflow — discover/config, run/inspect, triage SARIF findings (rule/query ID, source→sink, evidence), remediate, re-validate. Distinguishes broad MegaLinter linting from semantic security analysis.