Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/instructions/sushilti80/datadog-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/sushilti80/datadog-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sushilti80/datadog-mcp/copilot-instructions.svg" alt="Measured on agentmods" 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.02347 | $0.02347 |
| Opus 5 | $0.01174 | $0.01174 |
| Sonnet 5 | $0.00469 | $0.00469 |
| Haiku 4.5 | $0.00235 | $0.00235 |
Grade A, and why
datadog-mcp copilot-instructions.md scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:8080/health How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Datadog MCP Server - AI Agent Instructions
Architecture Overview
This is a FastMCP-based Model Context Protocol (MCP) server that exposes Datadog observability APIs to AI agents. The architecture centers on two core systems:
- FastMCP Server (
src/datadog_mcp_server.py) - HTTP+SSE transport server with tools, resources, and prompts - Key Rotation System (
src/key_rotation.py) - Intelligent multi-key management for rate limit avoidance
Key Components
- DatadogMCPServer class: Main server with
_execute_with_key_rotation()wrapper for all API calls - KeyPoolManager: Manages 3-5 API key pairs with 5 rotation strategies (adaptive, round_robin, LRU, weighted, random)
- Circuit Breaker: Automatically isolates problematic keys after configurable failure threshold
- Debug System: Enum-based debug levels (NONE/INFO/DEBUG/TRACE) with correlation IDs and sensitive data masking
Critical Pattern: DD_SITE Must Always Come From Environment
NEVER hardcode Datadog site values. Always use environment variables:
# ✅ CORRECT - Always read from environment
site = os.getenv("DD_SITE") or os.getenv("DATADOG_SITE") or "us3.datadoghq.com"
# ✅ For numbered keys
site = os.getenv(f"DD_SITE_{i}") or os.getenv(f"DATADOG_SITE_{i}") or "us3.datadoghq.com"
# ❌ NEVER do this
site = "datadoghq.com" # Wrong - hardcoded value
The default fallback us3.datadoghq.com should only appear in environment loading functions (load_keys_from_environment() in key_rotation.py), never in API client configuration.
Development Workflows
Running the Server
# Local development - reads .env file automatically
python3 src/datadog_mcp_server.py
# With debug tracing
MCP_DEBUG_LEVEL=TRACE python3 src/datadog_mcp_server.py
# Check server health on port 8080
curl http://localhost:8080/health
Testing
# Run all tests including key rotation
pytest tests/ -v
# Run specific test suite
pytest tests/test_key_rotation.py -v
# Test with coverage
pytest tests/ --cov=src --cov-report=html
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.
- 5d ago First seen · 286 lines · 2,347 tokens per session scan A 99f733c366ef
datadog-mcp copilot-instructions.md is an instructions file published in the GitHub repository sushilti80/datadog-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 2,347 tokens to every session, about $0.0117 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.