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 agentmods add skills/cacheforge-ai/cacheforge-skills/pager-triagenpx skills add cacheforge-ai/cacheforge-skills --skill pager-triagegit clone --depth 1 https://github.com/cacheforge-ai/cacheforge-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/cacheforge-ai/cacheforge-skills/pager-triage)<a href="https://agentmods.dev/skills/cacheforge-ai/cacheforge-skills/pager-triage"><img src="https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/pager-triage.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.00056 | $0.03167 |
| Opus 5 | $0.00028 | $0.01584 |
| Sonnet 5 | $0.00011 | $0.00633 |
| Haiku 4.5 | $0.00006 | $0.00317 |
Grade A, and why
pager-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 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PagerDuty Incident Triage
AI-powered incident triage for PagerDuty. Read-only by default. Write operations require explicit confirmation.
When to Activate
Use this skill when the user:
- Asks "what's firing?", "any incidents?", "what's on fire?", or anything about active alerts
- Mentions PagerDuty, pager, on-call, or incidents
- Asks "who's on call?" or "who's oncall right now?"
- Wants to acknowledge, resolve, or add a note to an incident
- Says "triage", "incident response", or "what happened last night?"
- Asks about service health or recent incidents for a service
Quick Setup
1. Create a PagerDuty API Key
- Go to PagerDuty → Settings → API Access Keys
- Click "Create New API Key"
- Name it
OpenClaw Agent - Select Read-only (recommended for triage; choose Full Access only if you need ack/resolve)
- Copy the key
2. Set Environment Variables
# Required — your PagerDuty REST API v2 token
export PAGERDUTY_API_KEY="u+your_key_here"
# Optional — required only for write operations (ack, resolve, note)
export PAGERDUTY_EMAIL="[email protected]"
3. Verify
Ask your agent: "What's firing on PagerDuty?"
Subcommands Reference
Read Operations (always safe, no confirmation needed)
incidents — List Active Incidents
Lists all triggered and acknowledged incidents, sorted by urgency.
pager-triage incidents
Example output:
{
"tool": "pd_incidents",
"provider": "pagerduty",
"timestamp": "2026-02-16T03:45:00Z",
"total_incidents": 3,
"incidents": [
{
"id": "P123ABC",
"incident_number": 4521,
"title": "High CPU on prod-web-03",
"status": "triggered",
"urgency": "high",
"service": { "id": "PSVC123", "name": "Production Web" },
"created_at": "2026-02-16T03:00:00Z",
"assignments": [{ "name": "Jane Doe", "email": "..." }],
"alert_count": 3,
"escalation_level": 1,
"last_status_change": "2026-02-16T03:05:00Z"
}
],
"summary": "3 active incident(s): high (triggered) x1, high (acknowledged) x1, low (triggered) x1"
}
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.
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 · 393 lines · 56 tokens per session scan A 2b718c898d04
pager-triage is a skill published in the GitHub repository cacheforge-ai/cacheforge-skills (10 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 3,167 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
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
sre_triage
SRE first-response triage for distributed training incidents. Automates the manual checks from PyTorch/NCCL debugging runbooks.
Diagnose CrashLoopBackOff
Triage pods restarting repeatedly and identify the most likely root cause.
Triage Kubernetes Node Pressure
Diagnose node-level memory/disk/pid pressure and determine safe mitigations.
Triage Pending Pods
Diagnose pods stuck in Pending and identify scheduling constraints.
Investigate Terraform Drift
Determine why actual infrastructure differs from Terraform state and choose a safe reconciliation path.