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-orchestrationgit 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-orchestration)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/pagerduty-orchestration"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/pagerduty-orchestration/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-orchestration"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/pagerduty-orchestration.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.00018 | $0.00697 |
| Opus 5 | $0.00009 | $0.00349 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
pagerduty-orchestration 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PagerDuty Orchestration Skill
Manage event orchestration and routing rules in PagerDuty.
Tools
| Tool | Description |
|---|---|
get_event_orchestration |
Get orchestration details |
get_event_orchestration_global |
Get global orchestration settings |
get_event_orchestration_router |
Get router rules for an orchestration |
get_event_orchestration_service |
Get service-specific orchestration |
list_event_orchestrations |
List all event orchestrations |
update_event_orchestration_router |
Update router rules (requires write) |
append_event_orchestration_router_rule |
Add a new router rule (requires write) |
Example Queries
List all event orchestrations
→ list_event_orchestrations()
Get orchestration details
→ get_event_orchestration(orchestration_id="E1ABCD23")
Get router rules
→ get_event_orchestration_router(orchestration_id="E1ABCD23")
Get global orchestration settings
→ get_event_orchestration_global(orchestration_id="E1ABCD23")
Workflows
Event Routing Review
- List orchestrations:
list_event_orchestrations() - Get orchestration details:
get_event_orchestration(orchestration_id="...") - Review router rules:
get_event_orchestration_router(orchestration_id="...") - Check service-specific rules:
get_event_orchestration_service(orchestration_id="...", service_id="...")
Add Network Event Routing Rule
- List current orchestrations:
list_event_orchestrations() - Get current router rules:
get_event_orchestration_router(orchestration_id="...") - Append new rule:
append_event_orchestration_router_rule(orchestration_id="...", rule={...}) - Verify rule added:
get_event_orchestration_router(orchestration_id="...")
Event Suppression Setup
- Get global orchestration:
get_event_orchestration_global(orchestration_id="...") - Review existing suppression rules
- Add suppression rule for maintenance window
- Verify:
get_event_orchestration_global(orchestration_id="...")
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 · 83 lines · 18 tokens per session scan A 65f65ed91848
pagerduty-orchestration is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 18 tokens to every session and 697 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…