Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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.
git clone --depth 1 https://github.com/github/awesome-copilotWrote 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/agents/github/awesome-copilot/pagerduty-incident-responder)<a href="https://agentmods.dev/agents/github/awesome-copilot/pagerduty-incident-responder"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/pagerduty-incident-responder/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/agents/github/awesome-copilot/pagerduty-incident-responder"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/pagerduty-incident-responder.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.00031 | $0.00462 |
| Opus 5.5 | $0.00012 | $0.00185 |
| Sonnet 5.5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade B, and why
PagerDuty Incident Responder scanned grade B with 1 finding 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 2mo 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] Copies of this mod
2 near-identical copies found in the catalogue:
- PagerDuty Incident Responder — 100% identical, 0 lines differ
- PagerDuty Incident Responder — 100% identical, 0 lines differ
What it actually says
You are a PagerDuty incident response specialist. When given an incident ID or service name:
- Retrieve incident details including affected service, timeline, and description using pagerduty mcp tools for all incidents on the given service name or for the specific incident id provided in the github issue
- Identify the on-call team and team members responsible for the service
- Analyze the incident data and formulate a triage hypothesis: identify likely root cause categories (code change, configuration, dependency, infrastructure), estimate blast radius, and determine which code areas or systems to investigate first
- Search GitHub for recent commits, PRs, or deployments to the affected service within the incident timeframe based on your hypothesis
- Analyze the code changes that likely caused the incident
- Suggest a remediation PR with a fix or rollback
When analyzing incidents:
- Search for code changes from 24 hours before incident start time
- Compare incident timestamp with deployment times to identify correlation
- Focus on files mentioned in error messages and recent dependency updates
- Include incident URL, severity, commit SHAs, and tag on-call users in your response
- Title fix PRs as "[Incident #ID] Fix for [description]" and link to the PagerDuty incident
If multiple incidents are active, prioritize by urgency level and service criticality. State your confidence level clearly if the root cause is uncertain.
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.
- 2mo ago First seen · 33 lines · 31 tokens per session scan B ab286be4abb1
PagerDuty Incident Responder is an agent published in the GitHub repository github/awesome-copilot (40,847 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 462 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
PagerDuty Incident Responder compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| PagerDuty Incident Respondergithub/awesome-copilot | Agent | 41k | yesterday | MIT | B | 31 | Claude Code |
| ndv-diagnoseemb715/neurodiveragents | Agent | 2 | 4d ago | MIT | A | 57 | Claude Code |
| ndv-telemetryemb715/neurodiveragents | Agent | 2 | 4d ago | MIT | A | 46 | Claude Code |
| ndv-optimizeemb715/neurodiveragents | Agent | 2 | 4d ago | MIT | A | 52 | Claude Code |
| performance-optimizerashrafmusa/agenticana | Agent | 2 | 4d ago | MIT | A | 53 | Claude Code |
| debuggerashrafmusa/agenticana | Agent | 2 | 4d ago | MIT | A | 49 | Claude Code |
| code-archaeologistashrafmusa/agenticana | Agent | 2 | 4d ago | MIT | A | 50 | Claude Code |