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 Nordic-AI/production-readiness-skills --skill observability-auditgit clone --depth 1 https://github.com/Nordic-AI/production-readiness-skillsWrote 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/nordic-ai/production-readiness-skills/observability-audit)<a href="https://agentmods.dev/skills/nordic-ai/production-readiness-skills/observability-audit"><img src="https://agentmods.dev/badge/skills/nordic-ai/production-readiness-skills/observability-audit/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/nordic-ai/production-readiness-skills/observability-audit"><img src="https://agentmods.dev/badge/skills/nordic-ai/production-readiness-skills/observability-audit.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.00106 | $0.03848 |
| Opus 5 | $0.00053 | $0.01924 |
| Sonnet 5 | $0.00021 | $0.00770 |
| Haiku 4.5 | $0.00011 | $0.00385 |
Grade A, and why
observability-audit 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 12d 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Audit
You review whether the running system can be understood from the outside — by an SRE staring at dashboards at 3am, by a developer triaging a bug report, by an auditor tracing a regulatory incident. Observability is not about having logs; it's about being able to answer questions you didn't know you'd ask.
Inputs
From orchestrator: scope_tier, stack_summary, entry points, gitnexus_indexed.
Mode detection
- Plan mode — report observability gaps with concrete additions recommended.
- Edit mode — apply code-level instrumentation. Runbooks and dashboard configs can be scaffolded but require the user to hook them into their actual observability stack.
Thresholds by tier
| Tier | Structured logs | Metrics | Traces | Alerts | Runbooks |
|---|---|---|---|---|---|
| prototype | advisory | optional | optional | advisory | not required |
| team | required — structured + correlation IDs | required — RED per endpoint | recommended | required on critical errors + SLO burn | recommended for critical flows |
| scalable | required — structured + correlation + sampling discipline | required — RED + USE + business KPIs | required — OTel traces across services | required — SLO-based, on-call rotation | required per critical flow |
Review surface
1. Logging
A. Format
- Structured logging required at team+ tier. JSON or logfmt, not plain text. Look for
winston,pino,zap,zerolog,logrus,log/slog,structlog,loguru, SLF4J + Logback JSON encoder, Serilog JSON formatter, etc. - Check for
console.log/print/fmt.Printlnused for production logging — almost always an anti-pattern. - Log lines must be parseable as a single record (no multi-line logs without proper framing; stack traces in a single field).
B. Correlation
- Every request/job/message must have a correlation ID (trace-id / request-id / correlation-id) threaded through all logs for that unit of work.
- Check middleware / interceptors for
X-Request-IDpropagation. - Async boundaries (queue publish → consume) must carry correlation IDs in message metadata.
- User context (tenant-id, user-id) logged on authenticated requests — with PII discipline (see data-protection-audit overlap).
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.
- 12d ago First seen · 355 lines · 106 tokens per session scan A caa5afbd8f5a
observability-audit is a skill published in the GitHub repository Nordic-AI/production-readiness-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 106 tokens to every session and 3,848 once invoked, about $0.0005 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
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
gdpr-compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing Agreements (DPAs), and consent notices, (3) answering GDPR compliance questions with authoritative article citations, and…
iso42001
Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
nist-800-53
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200 system categorization, control tailoring and overlays, privacy controls (PT family), supply chain risk management (SR…
soc2
Expert SOC 2 compliance assistant covering all five Trust Services Criteria (Security/CC, Availability/A, Confidentiality/C, Processing Integrity/PI, Privacy/P). Use this skill whenever a user mentions SOC 2, Trust Services Criteria, SOC 2 Type 1 or Type 2, audit readiness, compliance gaps, control documentation…