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 tjboudreaux/cc-plugin-engineering-excellence --skill eng-observabilitygit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-engineering-excellenceWrote 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/tjboudreaux/cc-plugin-engineering-excellence/eng-observability)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-observability"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-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/tjboudreaux/cc-plugin-engineering-excellence/eng-observability"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-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.00031 | $0.00347 |
| Opus 5 | $0.00015 | $0.00173 |
| Sonnet 5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
eng-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 9d 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 Debugging Discipline
Intent
- Make it trivial to answer “what is happening” and “why” without attaching a debugger in production.
- Ensure logs, metrics, events, and traces capture user intent, environment, and failure context while protecting sensitive data.
Guiding Principles
- Prefer structured logs + correlation IDs over ad-hoc strings.
- Emit signals at every boundary (client, API, worker, contract invocation).
- Include context (user/session/network/chain) necessary to reproduce issues.
- Keep signal cost reasonable—throttle chatty paths, sample intelligently.
- Build fast local debugging loops (trace replay, state inspectors, dev wallets).
Workflow
- Identify critical paths affected and define success/error signals per path.
- Add/extend tracing spans or log blocks with consistent field names.
- Validate observability locally by simulating successes, errors, and timeouts; ensure signals reach the sink (console, APM, analytics, chain explorer).
- Document dashboards, queries, or CLI commands useful for post-deploy verification.
- For on-chain logic, emit events with canonical schema so downstream indexers can consume them.
Verification
- Run the code with verbose logging/tracing enabled; inspect outputs for clarity and privacy.
- Confirm metrics/counters appear where expected (APM, telemetry pipeline, analytics, chain explorer).
- Dry-run incident response: can you locate a test failure or simulated outage using only emitted signals? If not, iterate.
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.
- 9d ago First seen · 30 lines · 31 tokens per session scan A 311fd3b16991
eng-observability is a skill published in the GitHub repository tjboudreaux/cc-plugin-engineering-excellence (4 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 347 once invoked, about $0.0002 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
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.