datadog-incidents

datadog-incidents is a skill for Claude Code, Codex from automateyournetwork/netclaw. It costs 15 tokens per session (515 once invoked), scanned A, original, Apache-2.0.

A tool for managing incidents in Datadog Incident Management, the part of Datadog used to track service problems and their response.

In plain words
What is it for?
Use it to list active or historical incidents, inspect a specific incident, create or update incidents, and track outages by service, severity, or time period.
Why use it?
It keeps incident status, severity, tags, timelines, and related information in one place during an investigation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to list active or historical incidents, inspect a specific incident, create or update incidents, and track outages by service, severity, or time period.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/automateyournetwork/netclaw/datadog-incidents
Install

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.

Any agent
npx skills add automateyournetwork/netclaw --skill datadog-incidents
Clone the repo
git clone --depth 1 https://github.com/automateyournetwork/netclaw

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for datadog-incidents

README.md
[![agentmods](https://agentmods.dev/badge/skills/automateyournetwork/netclaw/datadog-incidents/github.svg)](https://agentmods.dev/skills/automateyournetwork/netclaw/datadog-incidents)
Your own site
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/datadog-incidents"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/datadog-incidents/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.

agentmods 80×15 button for datadog-incidents

Your own site · 80×15
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/datadog-incidents"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/datadog-incidents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 515 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00515
Opus 5 $0.00008 $0.00258
Sonnet 5 $0.00003 $0.00103
Haiku 4.5 $0.00002 $0.00052

Measured 12d ago against content hash 49816a0a3ae4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

datadog-incidents 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 12d 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.

workspace/skills/datadog-incidents/SKILL.md · 75 lines

What it actually says

Datadog Incidents Skill

Manage incidents in Datadog Incident Management.

Tools

Tool Description
list_incidents List incidents with optional filters
get_incident Get detailed incident information
create_incident Create a new incident (read-only by default)
update_incident Update incident status or fields (read-only by default)

Example Queries

List all active incidents
→ list_incidents(status="active")

Get details of a specific incident
→ get_incident(incident_id="INC-12345")

List recent network-related incidents
→ list_incidents(tags=["service:network"], time_range="7d")

List SEV1 incidents from the past month
→ list_incidents(severity="SEV-1", time_range="30d")

Workflows

Incident Investigation

  1. List active incidents: list_incidents(status="active")
  2. Get incident details: get_incident(incident_id="INC-12345")
  3. Review timeline and related monitors
  4. Check correlated metrics and logs
  5. Document findings in incident

Network Outage Tracking

  1. Search network incidents: list_incidents(tags=["service:network"])
  2. Filter by impact: list_incidents(severity="SEV-1,SEV-2")
  3. Review affected services and dependencies
  4. Track MTTR and resolution patterns

Post-Incident Review

  1. Get incident timeline: get_incident(incident_id="INC-12345")
  2. Extract key events and decisions
  3. Identify detection and response gaps
  4. Document lessons learned

Prerequisites

  • DD_API_KEY Datadog API key
  • DD_APP_KEY Datadog application key
  • DD_SITE Datadog site (optional, defaults to datadoghq.com)

Server

This skill uses the datadog-mcp server via remote MCP transport.

Notes

  • Create and update operations may require additional permissions
  • NetClaw operates in read-only mode by default for safety
  • Incident creation should follow your organization's incident process
Changes

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.

  1. 12d ago First seen · 75 lines · 15 tokens per session scan A 49816a0a3ae4

Subscribe to this mod's changes

datadog-incidents is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 15 tokens to every session and 515 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens