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 bricerising/enterprise-software-playbook --skill observabilitygit clone --depth 1 https://github.com/bricerising/enterprise-software-playbookWrote 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/bricerising/enterprise-software-playbook/observability)<a href="https://agentmods.dev/skills/bricerising/enterprise-software-playbook/observability"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/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.00070 | $0.01908 |
| Opus 5 | $0.00035 | $0.00954 |
| Sonnet 5 | $0.00014 | $0.00382 |
| Haiku 4.5 | $0.00007 | $0.00191 |
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 8d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability (Instrumentation + Verification)
Overview
Make observability consistent and actionable: every boundary emits traces, metrics, and structured logs that correlate via IDs and stable fields.
This is intentionally opinionated: you should be able to answer “what happened?” with log → trace → metrics within a minute.
Inputs / Outputs
Inputs: Boundary code to instrument; service name; existing instrumentation (if any); correlation IDs in use.
Outputs: Instrumented code (traces, metrics, structured logs); field contract (stable keys); verification commands. Consumed by debug (for triage) and finish (for spot-check).
Workflow
- Name the decision this telemetry will inform (for example: keep current architecture, tune a timeout, roll out a migration).
- Define the unit of work (one trace): HTTP request, gRPC call, job run, queue message, WebSocket action.
- Define the measurement ladder:
- 3 leading indicators (move within days)
- 3 lagging outcomes (move within weeks/months)
- owner + review cadence + trigger for action
- Instrument end-to-end:
- traces: spans around the unit of work + key downstream calls
- metrics: RED for the boundary + a few domain metrics
- logs: structured JSON that includes correlation IDs
- Declare the field contract (stable keys).
- Add guardrails (PII rules, label cardinality rules, sampling/log levels).
- Verify correlation in a failure case (error log includes
traceId; trace contains downstream spans; metrics show error rate). - Define the operating ritual:
- where metrics/logs/traces are reviewed
- who decides and who executes follow-up
- what threshold triggers rollback/escalation
Minimum viable execution
When context or time is constrained, these are the load-bearing steps:
- Name the decision (step 1) — every metric needs a named decision it informs.
- Instrument RED at boundaries (step 4) — request count, error count, duration histogram per boundary.
- Add trace ID correlation to logs (step 4-5) — structured logs must include
traceIdfor log → trace linkage. - Verify correlation in a failure case (step 7) — error log includes traceId, trace shows downstream spans, metrics reflect the error.
What ships with it
2 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.
- 8d ago First seen · 153 lines · 70 tokens per session scan A 6e82e9d85874
observability is a skill published in the GitHub repository bricerising/enterprise-software-playbook (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,908 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-08-31.
Other skills, from other repositories
replit-deck
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident…
hps-true-blueprint
OpenDesign's engineering blueprint: how the sandbox, sidecar, and daemon fit — the system diagram and the invariants. Built as a decision-grade product management deck for engineering org.
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
deck-open-slide-canvas
OpenDesign's architecture review: the local daemon + agent-runtime design, the tradeoffs, and the decision to lock. Built as a decision-grade product management deck for staff eng, tech leads, security.
architecture-aware-init
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…