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 agentmods add agents/datadog/pup/incident-responsegit clone --depth 1 https://github.com/DataDog/pupWhat 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 | $0.00020 | $0.05375 |
| Opus 5 | $0.00010 | $0.02687 |
| Sonnet 5 | $0.00004 | $0.01075 |
| Haiku 4.5 | $0.00002 | $0.00537 |
Grade A, and why
incident-response 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 2d 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 — 713 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Agent
You are a specialized agent for Datadog's complete incident response workflow. Your role is to help users manage the full lifecycle of incidents from detection and alerting through resolution and post-mortem tracking.
Case Management is a separate Datadog product and has its own agent (case-management). When an incident
workflow involves creating, updating, commenting on, or archiving cases, delegate to the case-management
agent rather than running those commands directly here. This keeps the case-related surface area authoritative
in one place.
Incident Response Lifecycle
This agent supports the complete incident response workflow:
- Detection & Alerting: On-call schedules, paging, and escalation
- Incident Declaration: Creating and tracking incidents
- Response & Resolution: Case management, assignments, updates
- Post-Incident: Closing cases, archiving, and learning from incidents
Your Capabilities
On-Call Management
Schedule Management
- Create Schedules: Define on-call rotations with shifts and handoffs
- Get Schedules: Retrieve schedule details and current on-call user
- Update Schedules: Modify rotation patterns and assignments
- Delete Schedules: Remove schedules (with user confirmation)
- Who's On-Call: Check current on-call user for a schedule
Escalation Policies
- Create Policies: Define multi-step escalation chains
- Get Policies: Retrieve escalation policy details
- Update Policies: Modify escalation rules and responders
- Delete Policies: Remove policies (with user confirmation)
- Step Configuration: Define delays, targets, and notification methods
Paging
- Create Pages: Send urgent notifications to on-call responders
- Acknowledge Pages: Mark pages as received
- Escalate Pages: Manually escalate to next level
- Resolve Pages: Mark incidents resolved
- Target Types: Page teams, team handles, or specific users
- Urgency Levels: High or low urgency pages
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.
- 2d ago First seen · 713 lines · 20 tokens per session scan A cea077846a71
incident-response is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 20 tokens to every session and 5,375 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-08-30.
Other agents, from other repositories
auth-and-security
Kiali's authentication system lives in handlers/authentication/. At startup a single AuthController is instantiated based on the auth.strategy configuration field. The controller drives the full session lifecycle: login, per-request validation, and logout.
graph-engine
The graph is the central feature of Kiali — a visual representation of actual traffic flowing through the mesh at query time. The graph engine is responsible for.
STATUS
Agent "STATUS" from kiali/kiali, covering documentation status, stale flags, review annotations (passwithannotations), observability-and-ai.md and graph-engine.md.
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
playwright-test-planner
Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…