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/claude-code-plugin/ddviznpx skills add datadog-labs/claude-code-plugin --skill ddvizgit clone --depth 1 https://github.com/datadog-labs/claude-code-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.00047 | $0.00293 |
| Opus 5 | $0.00023 | $0.00147 |
| Sonnet 5 | $0.00009 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
ddviz 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.
What it actually says
What this controls
ddviz renders Datadog charts in a floating macOS panel, backed by a background daemon. The forwarding hook reads an opt-out marker file at $DDVIZ_DATA_DIR (defaults to $HOME/.ddviz).
Determine the user's intent
- Status ("is ddviz on?", "check ddviz"): run
bash "${CLAUDE_PLUGIN_ROOT}/skills/ddviz/scripts/status.sh". Present the result as "enabled" or "disabled". Do not describe the file path or implementation details unless asked. - Disable: run
bash "${CLAUDE_PLUGIN_ROOT}/skills/ddviz/scripts/disable.sh". Confirm that ddviz is now disabled on this machine, the panel closed if one was open, and future chart calls fall back to the sandbox-URL link. - Enable: run
bash "${CLAUDE_PLUGIN_ROOT}/skills/ddviz/scripts/enable.sh". Confirm that ddviz is enabled again. A chart-producing tool call is needed to bring the panel back up, since disabling shuts the daemon down.
If the intent is ambiguous, ask which of the three the user wants.
What ships with it
4 files 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.
- 3d ago First seen · 20 lines · 47 tokens per session scan A e66e8e105338
ddviz is a skill published in the GitHub repository datadog-labs/claude-code-plugin (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 293 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 skills, from other repositories
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…
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.
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.
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.
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.
trigger-tree
Inspect and improve documentation discovery using trigger-tree's local telemetry. Use for trigger-tree status, live dashboard, heat/cold maps, documentation health, router suggestions, setup, or diagnostics.