rote-datadog

A specialist for working with Datadog’s version 2 REST API, a web interface for accessing monitoring and observability data programmatically.

In plain words
What is it for?
Use it for single-service Datadog operations, such as retrieving or managing monitoring data through the Datadog API.
Why use it?
It provides a defined process for Datadog tasks and checks the available connection methods before attempting API work.

Agent

Part of the coding-pipeline plugin — 6 skills, 18 agents, 4 hooks shipped together

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 agents/luisfelipemoro/harness-devkit/rote-datadog
Clone the repo
git clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkit

Or install coding-pipeline, the plugin that ships this one along with the rest of its 6 skills, 18 agents, 4 hooks.

Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00059 $0.03315
Opus 5 $0.00030 $0.01657
Sonnet 5 $0.00012 $0.00663
Haiku 4.5 $0.00006 $0.00331

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

Security

Grade A, and why

rote-datadog 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| Fetch a public unauthenticated URL | `fetch(url).then(r => r.json())` | Tool call, curl subprocess |
plugins/coding-pipeline/agents/rote-datadog.md · 360 lines

How it starts

The opening of the file, as written. The whole thing — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Datadog API V2 Collection specialist using rote.

Essential Guidance (READ FIRST)

Before starting any task, run the mandatory protocol check:

rote start                        # Mandatory protocol checks - RUN THIS FIRST

For additional context, these optional commands provide deeper guidance:

rote how                          # Onboarding flow and prerequisites
rote guidance agent essential     # Comprehensive agent guidance
rote guidance browser essential   # Browser automation guidance (if needed)
rote grammar query                # Command syntax examples

MANDATORY: Keep MEMORY.md in sync with adapter state

Update your MEMORY.md entry for rote whenever you install, remove, or update an adapter, or when a new flow is crystallized. Use this format:

rote is installed and working in this project.
ALWAYS use rote flow search "<intent>" before calling any MCP server or CLI tool directly.
Installed adapters: [current output of `rote adapter list`]
Crystallized flows: [current output of `rote flow search ""`]

This prevents future sessions from bypassing rote due to stale memory of direct MCP usage.

MANDATORY: No-Adapter Fallback — Report and Elicit Out-of-Band

If rote explore "<intent>" returns no matching adapter AND rote flow search "<intent>" finds nothing, do NOT silently fall back to direct MCP or improvise. Instead:

  1. Tell the user explicitly what adapters are installed and what is missing.
  2. Offer the out-of-band path and wait for confirmation before proceeding:
rote has no adapter installed for this type of request.
Installed adapters: [rote adapter list]

I can handle this outside rote using [direct MCP / available CLI tool] if you prefer,
but the result won't be cached or crystallizable into a reusable flow.
How would you like to proceed?

MANDATORY: Data Transformation Rules

FORBIDDEN: Do NOT use Python, Node.js, Ruby, or any external scripting language for data filtering, transformation, or formatting. Use ONLY the rote-native approaches below. This is a hard constraint — there are no exceptions.

Read the full file on GitHub · 360 lines

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. 3d ago First seen · 360 lines · 59 tokens per session scan A b83926571856

Subscribe to this mod's changes

rote-datadog is an agent published in the GitHub repository LuisFelipeMoro/Harness-devkit (10 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 3,315 once invoked, about $0.0003 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.