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 MLOps-Courses/agentops-open-course --skill incident-triagegit clone --depth 1 https://github.com/MLOps-Courses/agentops-open-courseWrote 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/mlops-courses/agentops-open-course/incident-triage)<a href="https://agentmods.dev/skills/mlops-courses/agentops-open-course/incident-triage"><img src="https://agentmods.dev/badge/skills/mlops-courses/agentops-open-course/incident-triage/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/mlops-courses/agentops-open-course/incident-triage"><img src="https://agentmods.dev/badge/skills/mlops-courses/agentops-open-course/incident-triage.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.00036 | $0.00261 |
| Opus 5.5 | $0.00014 | $0.00104 |
| Sonnet 5.5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
incident-triage 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 1mo 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.
What it actually says
Incident Triage Skill
Instructions
- List every incident with
list_incidents(nostatusfilter), then keep only those whose status isopenorinvestigating(drop anyresolved). - Stop with a clear data-quality error if an active incident has no id, service, supported severity, or
opened_at; do not guess a ranking key. - Rank by severity — SEV1 before SEV2 before SEV3 — then by the oldest
opened_atfirst. - For tied top candidates, call
get_service_status; adownservice outranks adegradedservice, which outranks a healthy service. - Report the most urgent incident first with its id, service, severity, age evidence, current service state, and one-line summary. List the remaining active incidents in priority order.
- Separate observed facts from your recommendation. Do not invent incidents, severities, timestamps, or service state, and do not run remediation from a triage request.
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.
- 1mo ago First seen · 16 lines · 36 tokens per session scan A b7649c277932
incident-triage is a skill published in the GitHub repository MLOps-Courses/agentops-open-course (2 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 261 once invoked, about $0.0001 per session on Opus 5.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
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.
network-rca
Kubernetes network root cause analysis skill powered by Kubeshark MCP. Use this skill whenever the user wants to investigate past incidents, perform retrospective traffic analysis, take or manage traffic snapshots, extract PCAPs, dissect L7 API calls from historical captures, compare traffic patterns over time, detect…
mirrord-up
Helps users run multiple concurrent mirrord sessions from a single mirrord-up.yaml (compose-style multi-service local debugging). Use when the user mentions mirrord up, mirrord-up.yaml, mirrord up init, debugging several related microservices together, or managing multiple mirrord sessions' lifecycle in one command.
routing-calibration
Use when calibrating or validating a maintained routing recipe against live model backends, including probe manifests and evidence reports.
logging-patterns
Java logging best practices with SLF4J, structured logging (JSON), and MDC for request tracing. Includes AI-friendly log formats for Claude Code debugging. Use when user asks about logging, debugging application flow, or analyzing logs.
k8s-incident
Respond to Kubernetes incidents with runbooks and diagnostics. Use for outages, pod failures, node issues, network problems, and emergency response.