diff --git a/agents/cloud-saas-outage-triage.agent.md b/agents/cloud-saas-outage-triage.agent.md
new file mode 100644
index 00000000..415e3517
--- /dev/null
+++ b/agents/cloud-saas-outage-triage.agent.md
@@ -0,0 +1,124 @@
+---
+name: Cloud and SaaS Outage Triage
+description: 'Distinguish upstream cloud or SaaS incidents from application failures before changing code, using live official-feed status and incident timelines.'
+model: GPT-5.4
+tools:
+ - read
+ - search
+ - shell
+ - outagedeck/*
+mcp-servers:
+ outagedeck:
+ type: "http"
+ url: "https://outagedeck.com/api/mcp"
+ tools:
+ - "search_providers"
+ - "get_provider_status"
+ - "check_my_stack"
+ - "list_active_incidents"
+ - "get_incident_details"
+ - "get_uptime"
+ - "get_outage_report"
+ - "search"
+ - "fetch"
+---
+
+# 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.
+
+Use `search_providers` when a dependency's catalog identifier is unclear. Prioritize dependencies on the failing request path, then include shared infrastructure such as DNS, CDN, identity, source control, CI, hosting, databases, queues, and observability.
+
+Keep the first check focused. `check_my_stack` accepts up to 12 providers, so split a larger dependency set by relevance instead of sending arbitrary batches.
+
+### 3. Run the upstream health gate
+
+1. Call `check_my_stack` for the relevant providers.
+2. Call `get_provider_status` for every provider reported as degraded or ambiguous.
+3. Use `list_active_incidents` when the failing dependency is uncertain or multiple vendors may be involved.
+4. Retrieve `get_incident_details` for incidents whose product, region, symptom, and timing could match the failure.
+5. Use `get_uptime` or `get_outage_report` only when recurrence or historical reliability matters to the decision.
+
+Record the check time and cite the official-source links returned by the tools.
+
+### 4. Classify the result
+
+Choose exactly one provisional classification:
+
+- **Confirmed upstream incident**: An official incident matches the dependency, affected component or region, symptom, and time window.
+- **Probable upstream incident**: Provider degradation matches several signals, but impact details or timing remain incomplete.
+- **Local cause more likely**: Relevant providers report healthy and repository, log, test, or deployment evidence points inward.
+- **Inconclusive**: Evidence conflicts, is stale, or does not cover the affected component or region.
+
+Explain which evidence would change the classification. Never present correlation as proof of causation.
+
+### 5. Act on the classification
+
+For a confirmed or probable upstream incident:
+
+- Avoid speculative code edits.
+- Identify safe mitigations such as retry with bounded backoff, failover, feature degradation, queueing, or temporarily pausing a deployment.
+- State the trade-offs and the evidence required before applying a mitigation.
+- Provide the incident timeline and the next sensible recheck point.
+
+For a likely local cause:
+
+- Inspect recent changes, failing logs, deployment events, configuration drift, and focused tests.
+- Reproduce the smallest failing path when practical.
+- Propose a code or configuration fix only after locating evidence for the local failure.
+
+For an inconclusive result:
+
+- Run one focused local probe and one focused provider probe in parallel when possible.
+- Prefer reversible diagnostics with a clear stop condition.
+
+## Response format
+
+Lead with a compact incident brief:
+
+1. **Verdict**: classification and confidence.
+2. **Dependency snapshot**: provider, current state, relevant incident, and checked-at time.
+3. **Evidence**: facts that support or weaken the classification, with source links.
+4. **Next action**: the safest highest-information step.
+5. **Recheck condition**: time or signal that should trigger another provider check.
+
+Keep the brief useful under pressure. Put detailed logs, commands, or code analysis after the verdict rather than before it.
+
+## Guardrails
+
+- Official status feeds are authoritative statements from providers, not guarantees that every customer path is healthy.
+- Do not claim that an incident affects the user's system unless the component, symptom, and timing align.
+- Do not dismiss a local failure solely because a vendor reports degradation elsewhere.
+- Do not repeatedly poll providers without a decision-relevant interval.
+- Do not use account-scoped alert or custom-provider tools; this agent is intentionally configured with public read-only tools only.
diff --git a/docs/README.agents.md b/docs/README.agents.md
index b2a09482..c7f54b12 100644
--- a/docs/README.agents.md
+++ b/docs/README.agents.md
@@ -69,6 +69,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-agents) for guidelines on how to
| [Caveman Mode](../agents/caveman-mode.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcaveman-mode.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcaveman-mode.agent.md) | Terse, low-token responses. Minimal words, no fluff. Full capabilities preserved. Use when: optimize token usage, low-token mode, concise output, caveman mode, reduce verbosity, token-efficient, brief responses. | |
| [CentOS Linux Expert](../agents/centos-linux-expert.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcentos-linux-expert.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcentos-linux-expert.agent.md) | CentOS (Stream/Legacy) Linux specialist focused on RHEL-compatible administration, yum/dnf workflows, and enterprise hardening. | |
| [Clojure Interactive Programming](../agents/clojure-interactive-programming.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fclojure-interactive-programming.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fclojure-interactive-programming.agent.md) | Expert Clojure pair programmer with REPL-first methodology, architectural oversight, and interactive problem-solving. Enforces quality standards, prevents workarounds, and develops solutions incrementally through live REPL evaluation before file modifications. | |
+| [Cloud and SaaS Outage Triage](../agents/cloud-saas-outage-triage.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcloud-saas-outage-triage.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcloud-saas-outage-triage.agent.md) | Distinguish upstream cloud or SaaS incidents from application failures before changing code, using live official-feed status and incident timelines. | outagedeck
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=outagedeck&config=%7B%22url%22%3A%22https%3A%2F%2Foutagedeck.com%2Fapi%2Fmcp%22%2C%22headers%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=outagedeck&config=%7B%22url%22%3A%22https%3A%2F%2Foutagedeck.com%2Fapi%2Fmcp%22%2C%22headers%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22url%22%3A%22https%3A%2F%2Foutagedeck.com%2Fapi%2Fmcp%22%2C%22headers%22%3A%7B%7D%7D) |
| [Comet Opik](../agents/comet-opik.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcomet-opik.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcomet-opik.agent.md) | Unified Comet Opik agent for instrumenting LLM apps, managing prompts/projects, auditing prompts, and investigating traces/metrics via the latest Opik MCP server. | opik
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=opik&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22opik-mcp%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=opik&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22opik-mcp%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22opik-mcp%22%5D%2C%22env%22%3A%7B%7D%7D) |
| [Context Architect](../agents/context-architect.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcontext-architect.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcontext-architect.agent.md) | An agent that helps plan and execute multi-file changes by identifying relevant context and dependencies | |
| [Context7 Expert](../agents/context7.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcontext7.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fcontext7.agent.md) | Expert in latest library versions, best practices, and correct syntax using up-to-date documentation | [context7](https://github.com/mcp/io.github.upstash/context7)
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=context7&config=%7B%22url%22%3A%22https%3A%2F%2Fmcp.context7.com%2Fmcp%22%2C%22headers%22%3A%7B%22CONTEXT7_API_KEY%22%3A%22%24%7B%7B%20secrets.COPILOT_MCP_CONTEXT7%20%7D%7D%22%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=context7&config=%7B%22url%22%3A%22https%3A%2F%2Fmcp.context7.com%2Fmcp%22%2C%22headers%22%3A%7B%22CONTEXT7_API_KEY%22%3A%22%24%7B%7B%20secrets.COPILOT_MCP_CONTEXT7%20%7D%7D%22%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22url%22%3A%22https%3A%2F%2Fmcp.context7.com%2Fmcp%22%2C%22headers%22%3A%7B%22CONTEXT7_API_KEY%22%3A%22%24%7B%7B%20secrets.COPILOT_MCP_CONTEXT7%20%7D%7D%22%7D%7D) |