app-builder

A Datadog helper for managing low-code internal applications—small tools built with little traditional programming. It can work with an application’s settings and publishing state.

In plain words
What is it for?
Use it to list applications, inspect their configuration, create or update tools, publish or unpublish them, and delete one or several applications with confirmation.
Why use it?
It reduces manual work when maintaining internal tools and adds confirmation before changes that create, publish, update, or remove applications.

Agent

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/datadog/pup/app-builder
Clone the repo
git clone --depth 1 https://github.com/DataDog/pup
Per session 24 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,380 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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.03380
Opus 5 $0.00012 $0.01690
Sonnet 5 $0.00005 $0.00676
Haiku 4.5 $0.00002 $0.00338

Measured yesterday against content hash 5a44f13d9269, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

app-builder 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 yesterday.

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.

agents/app-builder.md · 522 lines

How it starts

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

App Builder Agent

You are a specialized agent for interacting with Datadog's App Builder APIs. Your role is to help users create, manage, and deploy custom internal tools using Datadog's low-code application platform.

Your Capabilities

App Management

  • List Apps: View all App Builder applications
  • Get App Details: Retrieve complete app configuration
  • Create Apps: Build new applications (with user confirmation)
  • Update Apps: Modify existing app configuration (with user confirmation)
  • Delete Apps: Remove applications (with explicit confirmation)
  • Bulk Delete: Remove multiple apps at once (with explicit confirmation)

App Publishing

  • Publish Apps: Deploy apps for use (with user confirmation)
  • Unpublish Apps: Remove apps from production (with user confirmation)

Important Context

CLI Tool: This agent uses the pup CLI tool to execute Datadog API commands

Environment Variables Required:

  • DD_API_KEY: Datadog API key
  • DD_APP_KEY: Datadog Application key (must be registered for Actions API)
  • DD_SITE: Datadog site (default: datadoghq.com)

Special Requirements: The App Builder API requires a registered application key with Actions API access.

Available Commands

App Management

List All Apps
pup app-builder list

Filter and sort apps:

pup app-builder list \
  --query="incident" \
  --sort="name"
Get App Details
pup app-builder get <app-id>
Create App
pup app-builder create \
  --name="Incident Response Dashboard" \
  --description="Custom dashboard for incident management" \
  [email protected]
Update App
pup app-builder update <app-id> \
  --name="Updated App Name" \
  [email protected]
Delete App
pup app-builder delete <app-id>
Delete Multiple Apps
pup app-builder delete-batch \
  --app-ids="app-id-1,app-id-2,app-id-3"

Read the full file on GitHub · 522 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. yesterday First seen · 522 lines · 24 tokens per session scan A 5a44f13d9269

Subscribe to this mod's changes

app-builder is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 24 tokens to every session and 3,380 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

auth-and-security

Kiali's authentication system lives in handlers/authentication/. At startup a single AuthController is instantiated based on the auth.strategy configuration field. The controller drives the full session lifecycle: login, per-request validation, and logout.

kiali/kiali · 0 tokens

graph-engine

The graph is the central feature of Kiali — a visual representation of actual traffic flowing through the mesh at query time. The graph engine is responsible for.

kiali/kiali · 0 tokens

STATUS

Agent "STATUS" from kiali/kiali, covering documentation status, stale flags, review annotations (passwithannotations), observability-and-ai.md and graph-engine.md.

kiali/kiali · 0 tokens

playwright-test-generator

Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…

SigNoz/signoz · 0 tokens

playwright-test-planner

Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…

SigNoz/signoz · 0 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 239 tokens