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 thiientv/godmode --skill observability-and-instrumentationgit clone --depth 1 https://github.com/thiientv/godmodeWrote 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/thiientv/godmode/observability-and-instrumentation)<a href="https://agentmods.dev/skills/thiientv/godmode/observability-and-instrumentation"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/observability-and-instrumentation/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/thiientv/godmode/observability-and-instrumentation"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/observability-and-instrumentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.00478 |
| Opus 5 | $0.00037 | $0.00239 |
| Sonnet 5 | $0.00015 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
observability-and-instrumentation 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
Start from the question an operator must answer, then emit the smallest safe signal that answers it.
Design sequence
- Name the user or business signal, SLO/error budget, failure mode, and responder.
- Map the request or job across boundaries and choose correlation/trace IDs, cardinality, sampling, and clock conventions.
- Define structured logs for state transitions and failures, metrics for rates/latency/saturation, and traces for cross-service causality.
- Include useful dimensions without high-cardinality or secret data. Redact tokens, PII, payloads, and credentials by default.
- Add alerts with actionable thresholds, runbook links, ownership, deduping, and a recovery path. Avoid alerts that merely report expected retries.
- Verify the signal in a safe environment and test the failure path that should emit it.
Prepare operational baselines
For release and incident use, record the pre-change baseline, freshness, expected variance, promotion or paging threshold, and recovery signal. Include one user or business outcome alongside technical health where possible. A dashboard without a decision owner and action threshold is reference material, not a guardrail.
Preserve a correlation path from release identifier to request, job, dependency, and user-visible outcome. Ensure incident responders can distinguish absent traffic, stale telemetry, collector failure, and healthy zero values.
Read signal-design.md. Instrumentation must not change correctness or become the only source of truth for business data.
Completion condition
An operator can detect the important failure, correlate it across boundaries,
understand the likely cause, and follow a bounded response without exposing
sensitive data. release-engineering can consume the baseline as a promotion
gate; incident-response can consume it as live evidence.
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.
- 10d ago First seen · 53 lines · 75 tokens per session scan A 9a96d63a19d9
observability-and-instrumentation is a skill published in the GitHub repository thiientv/godmode (94 stars, last pushed 14d ago), licensed MIT. It adds 75 tokens to every session and 478 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
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
investigate
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug…
anti-entropy-governance
Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.
agent-debug-fixer
A Chinese-language debugging and repair workflow for software problems. It investigates errors, failed tests, broken pages, or behavior that does not match expectations, then makes a minimal fix.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.