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 bugrabilge/bilge-development-kit --skill monitoring-observabilitygit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/monitoring-observability)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/monitoring-observability"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/monitoring-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.00052 | $0.03449 |
| Opus 5 | $0.00026 | $0.01724 |
| Sonnet 5 | $0.00010 | $0.00690 |
| Haiku 4.5 | $0.00005 | $0.00345 |
Grade A, and why
monitoring-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 5d 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 — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitoring & Observability Skill
Patterns and best practices for making production systems observable and debuggable.
Three Pillars of Observability
| Pillar | Purpose | Tools |
|---|---|---|
| Logs | What happened (events) | Pino, Winston, Python logging |
| Metrics | How much/how fast (numbers) | Prometheus, Datadog, CloudWatch |
| Traces | Request flow across services | OpenTelemetry, Jaeger, Zipkin |
Structured Logging
Principles
| Principle | Rule |
|---|---|
| Always structured | JSON format, never plain text in production |
| Always contextual | Include requestId, userId, service name |
| Never sensitive | No passwords, tokens, PII in logs |
| Appropriate levels | ERROR=broken, WARN=degraded, INFO=business events, DEBUG=dev only |
Log Levels
| Level | When to Use | Example |
|---|---|---|
| ERROR | Something is broken, needs attention | DB connection failed, unhandled exception |
| WARN | Degraded but functional | Retry succeeded, cache miss, slow query |
| INFO | Business-significant events | User registered, order placed, deploy complete |
| DEBUG | Development troubleshooting | Function input/output, state changes |
What to Log
| Always Log | Never Log |
|---|---|
| Request start/end with duration | Passwords or tokens |
| Error with stack trace | Full credit card numbers |
| Business events (signup, purchase) | PII without anonymization |
| External API calls with latency | Health check successes (too noisy) |
| Deployment events | Debug logs in production |
Structured Log Format
{
"timestamp": "2025-03-05T10:30:00.000Z",
"level": "error",
"service": "api",
"requestId": "req_abc123",
"userId": "usr_456",
"message": "Payment processing failed",
"error": {
"name": "PaymentError",
"message": "Card declined",
"code": "CARD_DECLINED"
},
"duration_ms": 1250,
"metadata": {
"provider": "stripe",
"amount": 9900
}
}
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.
- 5d ago First seen · 453 lines · 52 tokens per session scan A 914b2fafe546
monitoring-observability is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 3,449 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.