Borrowing it
Nothing to install: this file belongs to matteocervelli/llms. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/matteocervelli/llms/main/.claude/skills/ops/SKILL.mdgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/ops)<a href="https://agentmods.dev/skills/matteocervelli/llms/ops"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/ops.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.00067 | $0.01154 |
| Opus 5 | $0.00034 | $0.00577 |
| Sonnet 5 | $0.00013 | $0.00231 |
| Haiku 4.5 | $0.00007 | $0.00115 |
Grade A, and why
ops 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 3d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ops — Post-Deploy Observability
Unified observability guidance for production services. Auto-detects context from project files or accepts explicit mode.
Usage
/ops # Auto-detect from project signals
/ops logging # Explicit: structured logging setup
/ops metrics # Explicit: RED metrics + Prometheus instrumentation
/ops dashboard # Explicit: Grafana/DataDog/CloudWatch dashboards
/ops alerting # Explicit: SLO-based alerting policy
/ops overview # Cross-mode sequencing guide
Workflow
Step 1: Determine Context
Parse $ARGUMENTS for explicit mode. If no arguments, run context detector:
DETECTED=$(bash "$HOME/.claude/skills/ops/lib/context-detector.sh")
Step 2: Show Relevant Guidance
Based on detected or explicit mode, use progressive disclosure:
Level 1 — Summary (default, ~20 lines): Read and present the summary template for the detected mode. This is the entry point.
Level 2 — Patterns (on request, ~60-80 lines): When the user asks for more detail, "show me patterns", code examples, or "Don't/Do/Best" style guidance, read the patterns template.
Level 3 — Full SOP (future): Not yet available. If the user asks for a complete reference, offer to dive into patterns and answer specific questions.
Step 3: Handle Multiple Contexts
If context-detector returns multiple modes (e.g., "logging,metrics"):
- Show summary for each detected mode
- Ask: "Which area do you want to dive deeper into?"
Step 4: No Context Detected
If detection returns "none" and no explicit mode was given:
- Read and show
templates/overview.md - Let the user choose which mode to start with
Template Locations
Summary Templates (~20 lines each — L1 default)
| Mode | File |
|---|---|
logging |
~/.claude/skills/ops/templates/logging/summary.md |
metrics |
~/.claude/skills/ops/templates/metrics/summary.md |
dashboard |
~/.claude/skills/ops/templates/dashboard/summary.md |
alerting |
~/.claude/skills/ops/templates/alerting/summary.md |
What ships with it
9 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.
- templates/alerting/patterns.md 5.0 KB
- templates/alerting/summary.md 1.5 KB
- templates/dashboard/patterns.md 4.9 KB
- templates/dashboard/summary.md 1.3 KB
- templates/logging/patterns.md 4.3 KB
- templates/logging/summary.md 1.3 KB
- templates/metrics/patterns.md 5.2 KB
- templates/metrics/summary.md 1.4 KB
- templates/overview.md 1.3 KB
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.
- 3d ago First seen · 123 lines · 67 tokens per session scan A eb46ae8b71e2
ops is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 1,154 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-09-03.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…