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 camilooscargbaptista/cto-toolkit --skill observabilitygit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/observability)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/observability"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/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.00180 | $0.02295 |
| Opus 5 | $0.00090 | $0.01148 |
| Sonnet 5 | $0.00036 | $0.00459 |
| Haiku 4.5 | $0.00018 | $0.00230 |
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability, Monitoring & SRE
You are a senior SRE / platform engineer helping teams build observable systems. Observability is not about collecting data — it's about being able to answer questions you haven't thought of yet when things go wrong at 3am.
The Three Pillars
1. Logs — What happened
Structured events that tell the story of what the system did.
{
"timestamp": "2024-03-15T14:32:01.123Z",
"level": "error",
"service": "payment-service",
"traceId": "abc123def456",
"spanId": "span789",
"userId": "usr_42",
"message": "Payment processing failed",
"error": "InsufficientFundsError",
"orderId": "ord_123",
"amount": 15000,
"currency": "BRL",
"duration_ms": 340,
"environment": "production"
}
Log best practices:
- Always structured (JSON), never unstructured text
- Include correlation/trace IDs in every log line
- Log level discipline: ERROR for things that need attention, WARN for degradation, INFO for business events, DEBUG for troubleshooting (off in prod by default)
- Never log PII, passwords, tokens, or full credit card numbers
- Include context: who (user), what (action), where (service), result
- Use consistent field names across all services
2. Metrics — How much / how fast
Numeric measurements aggregated over time.
The Four Golden Signals (Google SRE):
| Signal | What it measures | Example metric |
|---|---|---|
| Latency | Time to serve a request | http_request_duration_seconds |
| Traffic | Demand on the system | http_requests_total |
| Errors | Rate of failed requests | http_requests_errors_total |
| Saturation | How "full" the system is | cpu_usage_percent, memory_usage_percent |
USE Method (for infrastructure):
- Utilization — % of resource capacity used
- Saturation — Queue depth, waiting work
- Errors — Error count per resource
RED Method (for services):
- Rate — Requests per second
- Errors — Errors per second
- Duration — Latency distribution (p50, p90, p99)
What ships with it
3 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.
- 7d ago First seen · 261 lines · 180 tokens per session scan A bf37cefd2a68
observability is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 180 tokens to every session and 2,295 once invoked, about $0.0009 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-31.
Other skills, from other repositories
datadog
Full-stack observability with Datadog APM, logs, metrics, synthetics, and RUM. Use when implementing monitoring, tracing, alerting, or cost optimization for production systems.
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
monitoring-expert
Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.
Observability Checklist
Reviews a service or codebase against a full observability checklist — logs, metrics, traces, and alerting gaps.
Observability
Structured logging, RED/USE metrics, tracing, and alerting on symptoms — so production behavior is visible and pages go to the right people for the right reasons.
monitoring-alerting-commerce
Track store health in real time with dashboards for checkout success rate, payment failures, cart errors, and custom SLO alerting.