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 ashermahonin/agentic-skills --skill observability-operationsgit clone --depth 1 https://github.com/ashermahonin/agentic-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/ashermahonin/agentic-skills/observability-operations)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/observability-operations"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/observability-operations.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.00054 | $0.00469 |
| Opus 5 | $0.00027 | $0.00234 |
| Sonnet 5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
observability-operations 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Operations
Purpose
You make systems diagnosable. Your work should help engineers answer what is broken, who is affected, why it happened, and what action is safe next.
Operational context
- Read
references/workflow.md. - Identify target platform, observability stack, required signals, critical user journeys, retention, privacy, and cost constraints.
- Verify current documentation for telemetry SDKs, collectors, alerting rules, dashboard provisioning, log pipelines, and semantic conventions.
Safe change sequence
- Define the signal model: metrics, logs, traces, profiles, events, or a combination.
- Map signals to user impact using RED, USE, four golden signals, or SLI/SLO language.
- Design labels, cardinality limits, trace/log correlation, retention, alert severity, and routing.
- Implement instrumentation, dashboards, alerts, provisioning, or pipeline configuration.
- Validate by generating signals, checking dashboard data, testing alerts, reviewing cardinality, and confirming trace-log correlation.
Safety rules
- Use Context7 MCP for current cloud, Kubernetes, IaC, CI/CD, container, observability, security, network, API, CLI, provider, and configuration documentation whenever the task depends on external technology behavior.
Change record
Provide signal goals, documentation validation status, instrumentation/config changes, dashboard and alert behavior, validation steps, privacy/cost risks, and assumptions.
Verification
- Alerts must be actionable and tied to user impact where possible.
- Critical alerts need runbook hints.
- Avoid high-cardinality labels and duplicated metrics.
- Do not log secrets or sensitive personal data.
- Preserve correlation IDs across logs, metrics, and traces.
Handoff
For incidents, pair with incident-troubleshooting. For Kubernetes monitoring, pair with kubernetes-operations. For CI/deploy telemetry, pair with cicd-automation.
References
references/workflow.mdfor observability design and validation checklist.
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 · 49 lines · 54 tokens per session scan A dd303be8662a
observability-operations is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 15d ago), licensed MIT. It adds 54 tokens to every session and 469 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…