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 TheBeardedBearSAS/claude-craft --skill observabilitygit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/observability)<a href="https://agentmods.dev/skills/thebeardedbearsas/claude-craft/observability"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/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/thebeardedbearsas/claude-craft/observability"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/observability.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.00000 | $0.00609 |
| Opus 5.5 | $0.00000 | $0.00244 |
| Sonnet 5.5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
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 1mo 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 — OpenTelemetry & Distributed Tracing
Instrumentation moderne avec OpenTelemetry pour métriques, traces et logs structurés.
Piliers de l'Observabilité
| Pilier | Technologies | Métriques clés |
|---|---|---|
| Metrics | Prometheus, Grafana, Datadog | RED (Rate, Errors, Duration), USE (Utilization, Saturation, Errors) |
| Traces | OpenTelemetry, Jaeger, Tempo | P95 latency, span duration, error rate |
| Logs | Loki, ElasticSearch, Datadog | Structured JSON, correlation IDs |
OpenTelemetry (OTel) Stack
// Node.js — Auto-instrumentation
const { NodeSDK } = require('@opentelemetry/sdk-node');
const { getNodeAutoInstrumentations } = require('@opentelemetry/auto-instrumentations-node');
const sdk = new NodeSDK({
traceExporter: new OTLPTraceExporter(),
instrumentations: [getNodeAutoInstrumentations()],
});
sdk.start();
Golden Signals (Google SRE)
| Signal | Description | Seuil typique |
|---|---|---|
| Latency | P50, P95, P99 response time | P95 < 200ms |
| Traffic | Requests per second | Baseline + alerting |
| Errors | Error rate (5xx, exceptions) | < 0.1% |
| Saturation | CPU, Memory, Disk | < 80% sustained |
Structured Logging (JSON)
{
"timestamp": "2026-04-17T10:30:00Z",
"level": "error",
"message": "Payment processing failed",
"trace_id": "4bf92f3577b34da6a3ce929d0e0e4736",
"span_id": "00f067aa0ba902b7",
"service.name": "payment-api",
"error.type": "PaymentGatewayTimeout"
}
SLI / SLO / SLA
| Concept | Exemple |
|---|---|
| SLI (Indicator) | 99.5% requests < 200ms |
| SLO (Objective) | 99.9% uptime mensuel |
| SLA (Agreement) | 99.95% uptime + pénalités |
Pour instrumentation détaillée par stack : invoquer @observability-engineer
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.
- 1mo ago First seen · 69 lines · 0 tokens per session scan A b140584d2d77
observability is a skill published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 609 tokens. 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-09-03.
Other skills, from other repositories
monitoring-observability
OpenTelemetry, structured logging, distributed tracing, alerting, and dashboards. Use when instrumenting services, designing logs/traces/metrics, defining SLOs and alerts, or debugging production behavior from telemetry.
extracting-code-structure
Use when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
analyzing-code-structure
Use when editing code structure with text matching ambiguity, handling "oldstring not unique" problems, or performing formatting-independent pattern matching across function signatures, method calls, and class structures.
audit-dead-code
Read-only hunt for dead and unused code across four labeled lanes (Knip for TS/JS, vulture for Python, gopls for Go, grep for shell and files no lane owns), each candidate adjudicated dead, uncertain or alive. Use when asked to 'find dead code', to find what is unused in a repository (exports, functions, orphaned…
agent-cpp-expert
Specialist subagent: C and C++ development, modern C++ (C++17/20/23), CMake, systems programming, and memory management specialist. Use when writing C/C++ code, debugging memory issues, or building systems-level software. Trigger phrases: C++, C language, CMake, modern C++, systems programming, memory management…