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 mickeyyaya/refactoring-skills --skill observability-patternsgit clone --depth 1 https://github.com/mickeyyaya/refactoring-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/skills/mickeyyaya/refactoring-skills/observability-patterns)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/observability-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/observability-patterns.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.00065 | $0.02228 |
| Opus 5 | $0.00032 | $0.01114 |
| Sonnet 5 | $0.00013 | $0.00446 |
| Haiku 4.5 | $0.00006 | $0.00223 |
Grade A, and why
observability-patterns 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
try { return await fetch(inventoryUrl, { headers }); } How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Patterns for Code Review
Overview
Unobservable systems fail silently. Use this guide during code review to catch observability hazards: missing correlation IDs, cardinality explosions, phantom health checks, and more.
When to use: Reviewing services with external calls, background jobs, or HTTP/gRPC APIs; evaluating logging, metrics, tracing; code touching distributed async flows or admin operations.
Quick Reference
| Pattern | Core Idea | Primary Red Flag |
|---|---|---|
| Structured Logging | JSON with consistent context fields | console.log() with string concat, no correlation ID |
| Log Levels | DEBUG/INFO/WARN/ERROR by severity | Everything at INFO, ERROR for non-errors |
| Distributed Tracing | Trace ID across service boundaries | Missing trace context in headers, no spans on external calls |
| Metrics | Counters/gauges/histograms on critical paths | No metrics on critical paths, cardinality explosion |
| Health Checks | Liveness vs. Readiness probes | Always returns 200, dependency check in liveness |
| Alerting | Symptom-based (SLO breach), not cause-based | Alert on every error, no SLO alert |
| Correlation IDs | Request ID through all async hops | Context lost at async boundary, no requestId in errors |
| Audit Trails | Immutable who/what/when record | No audit for admin ops, mutable audit records |
Patterns in Detail
1. Structured Logging
Red Flags: Unstructured console.log with string concat; PII in fields; no requestId; log-and-throw causing duplicates.
// BEFORE — unstructured, no context
console.log("Failed to process order for user " + userId + ": " + err.message);
// AFTER — structured JSON, context-rich
logger.error("order.process.failed", {
requestId: ctx.requestId, userId, orderId: order.id,
durationMs: Date.now() - startMs,
error: { message: err.message, code: err.code },
});
// Go — zap (zero allocation)
logger.Error("order.process.failed",
zap.String("requestId", ctx.RequestID), zap.String("userId", userID),
zap.Error(err), zap.Duration("duration", time.Since(start)))
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 · 233 lines · 65 tokens per session scan A bdf51a49c46b
observability-patterns is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 2,228 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…