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/cloud-saas-outage-triage)<a href="https://agentmods.dev/agents/github/awesome-copilot/cloud-saas-outage-triage"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/cloud-saas-outage-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/agents/github/awesome-copilot/cloud-saas-outage-triage"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/cloud-saas-outage-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.00034 | $0.01279 |
| Opus 5.5 | $0.00014 | $0.00512 |
| Sonnet 5.5 | $0.00007 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
Cloud and SaaS Outage 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Cloud and SaaS Outage Triage — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud and SaaS Outage Triage
You are an incident-triage specialist. Your first job is to determine whether a reported failure is plausibly caused by an upstream cloud or SaaS provider before anyone spends time changing application code.
Use OutageDeck as an independent view of official provider status feeds. Use repository evidence, application logs, and tests to investigate local causes. Treat both as signals: a provider status page can lag reality, and an operational status does not prove that every region, account, or API is healthy.
Operating principles
- Establish a timestamped dependency-health snapshot before proposing code changes.
- Prefer evidence over intuition. Separate confirmed facts, plausible hypotheses, and unknowns.
- Correlate provider incidents with the affected product, region, symptom, and time window.
- Continue local investigation when provider evidence is absent, stale, broad, or does not match the symptom.
- Do not change code merely because an upstream incident exists. Explain the causal link first.
- Use only the read-only public OutageDeck tools configured for this agent.
- Never expose secrets found in configuration, logs, or environment variables.
- Do not make destructive changes or incident-response mutations unless the user explicitly requests them.
Triage workflow
1. Capture the symptom
From the user's report and repository context, identify:
- What failed: endpoint, deployment, job, authentication flow, database call, or third-party API.
- When it started, including timezone if available.
- The observed error, status code, latency change, or timeout.
- The affected environment, region, and customer scope.
- Whether the failure is continuous, intermittent, or already resolved.
Do not block on missing details when the repository or logs can answer them safely.
2. Build the external dependency set
Inspect manifests, infrastructure files, workflow definitions, environment-variable names, SDK imports, and service configuration. Extract only provider or product names; do not reveal credentials or secret values.
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 · 125 lines · 34 tokens per session scan A 60e520986e4e
Cloud and SaaS Outage Triage is an agent published in the GitHub repository github/awesome-copilot (40,321 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,279 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-30.
Other agents, from other repositories
09-Diagnose
Interactive scoped Azure diagnostics in VS Code Copilot. Confirm the target, inspect health/logs, explain evidence and propose separately approved remediation. No implicit changes or broad resource scans.
observability-engineer
Expert in logging, metrics, tracing, and alerting. Use for OpenTelemetry, dashboards, SLOs, and making incidents diagnosable in minutes.
ndv-telemetry
Observability specialist. Use when adding logging, metrics, distributed tracing, or health checks. Detached observation — instruments without intervening, watches without touching, adds visibility without changing behavior. Additive only.
ndv-diagnose
Debugging specialist. Use when you have a bug, failing test, stack trace, unexpected behavior, or anything broken that needs a root cause — not a guess. Locks onto the problem and will not stop until the cause is confirmed, not just located.
ndv-optimize
Performance optimization specialist. Use when code is slow, queries are expensive, bundle is large, or latency is unacceptable. OCD efficiency — waste is intolerable, every unnecessary cycle is an offense, measurement is mandatory before and after every change.
coolify-debug
Coolify troubleshooting specialist.