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 int2t05/engineering-skills --skill observabilitygit clone --depth 1 https://github.com/int2t05/engineering-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/int2t05/engineering-skills/observability)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/observability"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/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.
<a href="https://agentmods.dev/skills/int2t05/engineering-skills/observability"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/observability.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00370 |
| Opus 5.5 | $0.00010 | $0.00148 |
| Sonnet 5.5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
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 10d 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.
What it actually says
Observability and Instrumentation
When to use
- Instrument service behavior and verify operators can diagnose it.
Not for: incident-response for active incidents.
Steps
-
Identify operational questions, critical flows and service objectives.
-
Add redacted structured logs, bounded metric labels and meaningful correlated spans using existing tooling.
-
Configure actionable symptom alerts with measured or requirement-based thresholds and a runbook: meaning, first query, recovery and escalation.
-
Generate controlled traffic and failures, confirm actual signals and alert behavior and restore temporary settings.
Verify
- Telemetry traces real success and failure without secrets; unavailable signal or delivery checks are explicit.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- references/observability-checklist.md — at-a-glance instrumentation checklist + pre-launch gate
- references/slo-methodology.md — SLI definition, error budgets, burn-rate alerting, SLO-based release gating
- references/cost-observability.md — FinOps: cost attribution, per-request cost, anomaly detection, optimization levers
- runbook-template.md — runbook authoring structure (write when you create the alert, not during the incident)
- references/slo-implementation.md — Prometheus recording/alerting rules, multi-window burn-rate alerts, error-budget queries, dashboards, review cadence
What ships with it
5 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.
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.
- 10d ago Changed · -65 lines · -39 tokens per session cdb05a6b9ed4
- 1mo ago First seen · 101 lines · 63 tokens per session scan A 4d37100d40d9
observability is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 370 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
sonarqube
Levantar SonarQube con Docker, analizar el código y proponer mejoras. También: análisis estático, deuda técnica, code smells, cobertura, calidad automatizada.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.
shipyard-debugging
Investigates root cause systematically before any fix is proposed. Use when encountering any bug, test failure, unexpected behavior, or error message. Also use for tracebacks, exceptions, "not working" complaints, build failures, performance problems, or integration issues, and whenever the next step would be to…
codebase-hygiene
Two-mode skill: (1) find semantic duplicates — functions doing the same thing under different names, invisible to copy-paste detectors; (2) deepen shallow modules — thin wrappers and pass-through layers that spread complexity. Advisory and read-only; changes route through BUILD with full gates.