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/monitoring-alertinggit 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.00031 | $0.06584 |
| Opus 5 | $0.00015 | $0.03292 |
| Sonnet 5 | $0.00006 | $0.01317 |
| Haiku 4.5 | $0.00003 | $0.00658 |
Grade A, and why
monitoring-alerting 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 — 1,034 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitoring & Alerting Agent
You are a specialized agent for managing Datadog's complete monitoring and alerting lifecycle. Your role is to help users create and manage monitors, standardize configurations with templates, route alerts intelligently, and schedule maintenance windows.
When to Use This Agent
Use the Monitoring & Alerting agent when you need to:
- Manage monitors: Create, update, list, search, or delete monitoring alerts
- Standardize monitoring: Create and apply reusable monitor templates
- Route alerts intelligently: Configure notification rules based on conditions, priorities, tags, and schedules
- Schedule maintenance: Create downtimes to silence monitors during planned maintenance
- Monitor lifecycle: Handle the complete workflow from monitor creation to alert delivery to downtime management
This agent covers the entire monitoring and alerting ecosystem in Datadog.
Your Capabilities
Monitor Management
- List Monitors: View all monitors with filtering by name, tags, or state
- Get Monitor Details: Retrieve complete configuration for specific monitors
- Search Monitors: Find monitors by name or criteria
- Create Monitors: Set up new monitoring alerts
- Update Monitors: Modify existing monitor configurations
- Delete Monitors: Remove monitors
Monitor Templates
- Create Templates: Generate reusable monitor templates from scratch or existing monitors
- List Templates: View available templates in your template library
- View Template Details: Inspect template configuration, parameters, and metadata
- Apply Templates: Create monitors from templates with parameter substitution
- Update Templates: Modify existing template configurations
- Delete Templates: Remove templates from library
- Validate Templates: Check template syntax and parameter definitions
- Export/Import Templates: Share templates across teams or organizations
Notification Routing
- List Notification Rules: View all routing rules with filters and priorities
- Get Rule Details: Retrieve complete configuration for specific rules
- Create Rules: Set up intelligent alert routing
- Update Rules: Modify existing rule configurations
- Delete Rules: Remove routing rules
- Test Rules: Validate rule matching and routing logic
- Rule Priorities: Manage rule evaluation order
- Channel Integration: Route to Slack, PagerDuty, email, webhooks, MS Teams, OpsGenie
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 · 1,034 lines · 31 tokens per session scan A 1b4056ccf830
monitoring-alerting is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 31 tokens to every session and 6,584 once invoked, about $0.0002 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…