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 sergei-aronsen/claude-code-toolkit --skill production-observabilitygit clone --depth 1 https://github.com/sergei-aronsen/claude-code-toolkitWrote 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/sergei-aronsen/claude-code-toolkit/production-observability)<a href="https://agentmods.dev/skills/sergei-aronsen/claude-code-toolkit/production-observability"><img src="https://agentmods.dev/badge/skills/sergei-aronsen/claude-code-toolkit/production-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.00048 | $0.00819 |
| Opus 5 | $0.00024 | $0.00409 |
| Sonnet 5 | $0.00010 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
production-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 6d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Observability
Why this skill exists
GSD verifies plan-vs-spec consistency. It does NOT verify product-vs-reality. Code passes all gates, ships to prod, and breaks for users — silently — until you hear about it from support.
Iron law: If a phase ships to production without observability instrumentation, you have NOT shipped quality. You shipped hope.
When this skill activates
- After
/gsd-execute-phasecomplete, before/gsd-ship - When user mentions: "ship", "deploy", "release", "production", "monitor"
- When integrating: payments, auth, third-party API, anything that talks to external service
- When user-facing UI changes (ANY change visible to end users)
Three-tool minimum
1. Sentry — runtime error capture (zero-config catches 90% of crashes)
2. Playwright — pre-ship smoke against deployed URL (catches deploy-time regressions)
3. Posthog/etc. — user-event funnel + session replay (catches "looks fine but conversion dropped")
Skipping ANY of these = blind deploy.
Pre-ship checklist
Before running /gsd-ship:
-
Sentry instrumented?
- Server-side:
Sentry.init(dsn=...)at app startup - Client-side: SDK loaded in HTML head OR via Next.js wizard
- Source maps uploaded for stack traces
- Server-side:
-
Playwright e2e for critical path exists?
- At minimum: load homepage, click primary CTA, verify next page
- For SaaS: signup flow + first action + payment (if applicable)
- Runs in CI, not optional
-
Posthog (or similar) tracking critical events?
- 3-5 events maximum:
signup_completed,first_action,payment_succeeded,error_seen - Funnel built on Posthog dashboard, monitored
- 3-5 events maximum:
If any answer is NO — instrument BEFORE shipping. Not after.
Post-ship verification ritual
Within 1 hour of ship:
1. Sentry dashboard — zero new errors in last hour? OK
2. Playwright in CI — green run against deployed URL? OK
3. Posthog funnel — conversion rate within 10% of pre-ship baseline? OK
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.
- 6d ago First seen · 87 lines · 48 tokens per session scan A 4d60d3bca853
production-observability is a skill published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 20d ago), licensed MIT. It adds 48 tokens to every session and 819 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…