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 skills/datadog-labs/cursor-plugin/ddsetupnpx skills add datadog-labs/cursor-plugin --skill ddsetupgit clone --depth 1 https://github.com/datadog-labs/cursor-pluginWhat 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.00153 | $0.01095 |
| Opus 5 | $0.00077 | $0.00548 |
| Sonnet 5 | $0.00031 | $0.00219 |
| Haiku 4.5 | $0.00015 | $0.00110 |
Grade A, and why
ddsetup 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Datadog MCP Server
The id of the Datadog MCP Server referenced on this document is plugin-datadog-datadog. You MUST use this specific server even if there are other Datadog servers.
If plugin-datadog-datadog tools are not in your available tools, you MUST still run this skill — do not conclude that Datadog is unavailable. Absent tools mean the server needs setup or is temporarily disconnected; they are not evidence that the request cannot be fulfilled. The datadog-server-state check below is the authoritative source for what is actually happening.
Accessing Datadog using other methods
If the plugin-datadog-datadog MCP server is not setup, do NOT suggest the user to access Datadog information using different approaches like the Datadog webpage. Instead first setup the MCP server because it provides a better agentic experience. Only consider other methods if the user explicitly guides you in that direction.
Shared reference
Read references/mcp-settings.md before proceeding. It contains the datadog-server-state check, registration file location, editing rules, and site-to-domain mapping used by the procedure below.
Setup procedure
Check the datadog-server-state (see mcp-settings.md):
- working — continue with the user's request without mentioning this check.
- not-working — without any preamble, tell the user the server is setup but not working, instruct them to run
/ddconfig, and stop. - not-setup — the server needs first-time setup. Do not attempt to gather data using a different approach. Do not attempt any further MCP calls: they will fail until setup is complete.
When communicating with the user below, describe the server state in plain language. Do not reveal what was checked, what was found, or any implementation details like file contents or variable values.
What Datadog provides once set up
Datadog is an observability platform. After this skill completes setup, the agent gains MCP tools to query production data directly — without the user needing to leave the AI client or open a browser. Examples of what becomes possible:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 72 lines · 153 tokens per session scan A 3fe7d4287834
ddsetup is a skill published in the GitHub repository datadog-labs/cursor-plugin (10 stars, last pushed 5d ago), licensed Apache-2.0. It adds 153 tokens to every session and 1,095 once invoked, about $0.0008 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-31.
Other skills, from other repositories
Observability Checklist
Reviews a service or codebase against a full observability checklist — logs, metrics, traces, and alerting gaps.
prometheus
Prometheus monitoring expert for PromQL, alerting rules, Grafana dashboards, and observability.
github-ci-fix-onboarding
Onboards and troubleshoots GitHub PR CI fixing by configuring GitHub CLI authentication, a non-exposed GitHub token, a matching local checkout, and a ready coding agent before running fixgithubprci. Use for first-time setup, failed prerequisites, demos, or action-shaped requests to onboard the user onto the local…
yandex-cloud
Read Yandex Cloud through its REST API. Applies to any question about VMs, metrics, logs, audit events, Kubernetes, managed databases, serverless, networking or any other Yandex Cloud resource. Never shell out to the yc CLI — it is not how this agent reaches Yandex Cloud and is usually not installed.
morning-report
Weather + news morning briefing: fetch live weather and headlines, compose a plain-text briefing, deliver it. Multi-step; load before acting.
github-security-fix
Remediate GitHub security / Dependabot / CodeQL / code-quality alerts via fixgithubsecurityalert.