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 automateyournetwork/netclaw --skill pagerduty-incidentsgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/pagerduty-incidents)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/pagerduty-incidents"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/pagerduty-incidents/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/automateyournetwork/netclaw/pagerduty-incidents"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/pagerduty-incidents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.00780 |
| Opus 5 | $0.00007 | $0.00390 |
| Sonnet 5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
pagerduty-incidents 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 9d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PagerDuty Incidents Skill
Manage and investigate incidents in PagerDuty.
Tools
| Tool | Description |
|---|---|
list_incidents |
List incidents with filters (status, urgency, time range) |
get_incident |
Get detailed incident information |
get_alert_from_incident |
Get specific alert from an incident |
list_alerts_from_incident |
List all alerts associated with an incident |
list_incident_notes |
Get notes/timeline from an incident |
get_outlier_incident |
Identify anomalous incident patterns |
get_past_incidents |
Get historical incidents for pattern analysis |
get_related_incidents |
Find related incidents by service or time |
create_incident |
Create a new incident (requires write permission) |
manage_incidents |
Acknowledge, resolve, or merge incidents |
add_note_to_incident |
Add investigation notes to incident |
add_responders |
Add additional responders to an incident |
Example Queries
List all triggered incidents
→ list_incidents(statuses=["triggered"])
Get details of a specific incident
→ get_incident(incident_id="P12ABC3")
List incidents for a service in the past hour
→ list_incidents(service_ids=["PSERVICE1"], since="1h")
Get all alerts from an incident
→ list_alerts_from_incident(incident_id="P12ABC3")
Find related incidents to investigate
→ get_related_incidents(incident_id="P12ABC3")
Workflows
Incident Investigation
- List triggered incidents:
list_incidents(statuses=["triggered"]) - Get incident details:
get_incident(incident_id="...") - Review alerts:
list_alerts_from_incident(incident_id="...") - Check for related incidents:
get_related_incidents(incident_id="...") - Add investigation notes:
add_note_to_incident(incident_id="...", note="...")
Network Outage Response
- List high-urgency incidents:
list_incidents(urgencies=["high"]) - Filter by network services:
list_incidents(service_ids=["network-core"]) - Acknowledge incident:
manage_incidents(incident_ids=["..."], type="acknowledge") - Check past incidents for patterns:
get_past_incidents(incident_id="...") - Add responders if needed:
add_responders(incident_id="...", responder_ids=["..."])
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.
- 9d ago First seen · 86 lines · 14 tokens per session scan A 81e1a31d6d52
pagerduty-incidents is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 14 tokens to every session and 780 once invoked, about $0.0001 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…