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 m-binimran/dev-pack --skill observabilitygit clone --depth 1 https://github.com/m-binimran/dev-packWrote 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/m-binimran/dev-pack/observability)<a href="https://agentmods.dev/skills/m-binimran/dev-pack/observability"><img src="https://agentmods.dev/badge/skills/m-binimran/dev-pack/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/m-binimran/dev-pack/observability"><img src="https://agentmods.dev/badge/skills/m-binimran/dev-pack/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.00046 | $0.00381 |
| Opus 5.5 | $0.00018 | $0.00152 |
| Sonnet 5.5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
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
You can't fix what you can't see. Capture errors with context; don't capture secrets.
Error monitoring
- Sentry (or equivalent) on client, server, and edge. Source maps uploaded so stack traces are readable.
- Capture in
error.tsxboundaries and in route handler/action catch blocks — re-throw or report, don't swallow. - Attach context: route, user id (not email/PII), request id. Scrub tokens, passwords, card data, full emails.
Logging
- Structured (JSON) logs with a level (
info/warn/error) and a request/correlation id, not bareconsole.logstrings. Log decisions and failures, not noise. - Log server-side only; never log secrets, full request bodies with credentials, or PII.
- One line per meaningful event; include enough to reproduce, nothing more.
What to watch
- Error rate + new error types after a deploy, slow routes/queries (pair with
query-optimizer), failed webhooks/payments, auth failures spiking.
Output
- The Sentry init (client/server/edge), the logging helper, and the PII-scrubbing rules applied.
Guardrails
- Monitoring must not become a leak: no secrets/PII in events or logs (the
secret-scanhook guards code, but you must scrub runtime values too). - Don't ship
console.logdebugging to production (thecode-qualityrule forbids it) — use the logger.
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 · 32 lines · 46 tokens per session scan A 4603e5395fab
observability is a skill published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 381 once invoked, about $0.0002 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
guardrails-developer-guide
Routes NVIDIA NeMo Guardrails library product-usage questions to the canonical documentation. Use when users ask how to install, configure, integrate, evaluate, observe, deploy, troubleshoot, or use the NVIDIA NeMo Guardrails library. Trigger keywords - install guardrails, configure rails, guardrail catalog, Colang…
thumbgate-doctor
Health-check whether ThumbGate is actually wired into this agent — PreToolUse/SessionStart hooks installed, MCP server reachable, lesson store present, statusline, and overall agent-readiness — then report exactly what to fix. Runs the existing npx thumbgate doctor audit and the checkoperationalintegrity MCP tool. Use…
prevention-rules
Generate and review prevention rules auto-promoted from repeated failure patterns.
forge-troubleshoot
Diagnose and resolve Plan Forge issues — failed runs, broken validation gates, misconfigured environments, stalled slices, and orchestrator errors. Use when a plan run fails or the forge behaves unexpectedly.
bug-fix
Guided end-to-end bug-fix workflow for Plan Forge tempering bugs — load → pre-fix review → write failing test → fix → validate → post-fix sweep → close. Composes /code-review, /clean-code-review, /forge-quench, and /test-sweep around the forgebug tool surface so a fix never closes without a regression check.
health-check
Run a full Plan Forge health diagnostic — environment, setup validation, and completeness scan. Use to verify your forge is properly configured and code is clean.