A setup guide for creating a new Datadog App, a small application that extends Datadog’s monitoring platform. It only covers the initial project scaffolding.

Use it when starting a Datadog App project with the Datadog app tools or npm create command.

It gives you the correct starting structure and commands for a new Datadog App, while keeping later development steps separate.

datadog-app — Skill by datadog-labs

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.

agentmods

npx agentmods add skills/datadog-labs/claude-code-plugin/datadog-app

Any agent

npx skills add datadog-labs/claude-code-plugin --skill datadog-app

Clone the repo

git clone --depth 1 https://github.com/datadog-labs/claude-code-plugin

Made for: Claude Code, Codex.

Or install datadog, the plugin that ships this one along with the rest of its 5 skills, 2 hooks.

Per session 127 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 315 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00127	$0.00315
Opus 5	$0.00063	$0.00158
Sonnet 5	$0.00025	$0.00063
Haiku 4.5	$0.00013	$0.00032

Measured 3d ago against content hash bec3201018d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

datadog-app 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 3d 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.

skills/datadog-app/SKILL.md · 23 lines

What it actually says

Datadog Apps

Use this skill only to scaffold a new Datadog App. It covers nothing else.

Once the app is scaffolded, all further guidance — local development, auth, deploy, publish, CI/CD, backend functions, data access, upgrading, and troubleshooting — lives in the generated project's AGENTS.md and docs/agents/ files.

Reference Routing

User task	Read
Create a new Datadog App	`references/getting-started.md`

Boundaries

This skill covers scaffolding only. Stop here once the project is created.
Do not provide auth, deploy, publish, CI/CD, or app logic guidance from this skill — read the project's AGENTS.md instead.
Do not cover Datadog package/platform development in this skill.

Files

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.

references/getting-started.md 1.6 KB

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.

3d ago First seen · 23 lines · 127 tokens per session scan A bec3201018d4

Subscribe to this mod's changes

datadog-app is a skill published in the GitHub repository datadog-labs/claude-code-plugin (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 127 tokens to every session and 315 once invoked, about $0.0006 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.

observability profiling telemetry

frontmcp-observability

Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…

agentfront/frontmcp · 177 tokens

tt

See which docs your AI actually discovers with local, zero-token telemetry. Subcommands; /tt status, /tt watch [demo|replay], /tt insights, /tt instructions, /tt suggestions, /tt badge, /tt gate, /tt note , /tt doctor, /tt setup, /tt uninstall, /tt help.

Hedde/trigger_tree · 74 tokens

debugging-with-wide-events

Use when investigating production behavior by querying wide events (a slow route, an error spike, a suspicious deploy, "why is this happening for account X"). Covers the data model, the symptom-to-query workflow, and standing queries worth running.

adammiribyan/wide_events · 54 tokens

setting-up-wide-events-store

Use when a human asks to set up, deploy, or finish deploying the bundled Wide Events DuckDB store (the Kamal accessory that receives production telemetry). Covers the store generator, DNS, kamal setup, and post-deploy verification end to end.

adammiribyan/wide_events · 58 tokens

instrumenting-wide-events

Use when adding or changing app code that should be observable in production: new features, slow paths, rescue blocks, background jobs. Covers the WideEvent API (set/phase/error!), attribute naming conventions, the registry workflow, and test assertions.