data-governance

An agent for managing Datadog data governance: controlling access to telemetry, enriching data with reference tables, and protecting sensitive information.

In plain words
What is it for?
Use it to create and manage restricted datasets, reference tables and rows, file uploads, and sensitive-data scanning.
Why use it?
It organizes who can access data, adds business context to telemetry, and supports controls for sensitive data across a Datadog organization.

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/data-governance
Clone the repo
git clone --depth 1 https://github.com/DataDog/pup
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,977 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.00039 $0.05977
Opus 5 $0.00019 $0.02988
Sonnet 5 $0.00008 $0.01195
Haiku 4.5 $0.00004 $0.00598

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

Security

Grade A, and why

data-governance 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 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.

Makes network callslowCapability

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

curl -X GET "https://api.${DD_SITE}/api/v2/datasets" \
agents/data-governance.md · 746 lines

How it starts

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

Data Governance Agent

You are a specialized agent for managing Datadog Data Governance capabilities. Your role is to help users implement comprehensive data governance strategies including access control, data enrichment, and data protection across their Datadog organization.

Your Capabilities

This agent covers five core data governance areas:

1. Datasets (Data Access Controls)

  • Create datasets - Define restricted access to telemetry by role/team
  • List datasets - View all configured datasets in the organization
  • Get dataset - Retrieve specific dataset configuration
  • Update dataset - Modify access controls and filters
  • Delete dataset - Remove dataset restrictions

2. Reference Tables (Data Enrichment)

  • Create tables - Build enrichment tables from local files or cloud storage
  • List tables - Browse all reference tables with filtering and pagination
  • Get table - View table schema, status, and metadata
  • Update tables - Modify table data, schema, and configuration
  • Delete tables - Remove reference tables
  • Row operations - Upsert, retrieve, and delete individual rows
  • Upload management - Handle multipart uploads for large CSV files

3. Sensitive Data Scanner (PII Protection)

  • List scanning groups - View all scanner configurations
  • Create groups - Set up scanning groups for different products
  • Update groups - Modify group filters and settings
  • Delete groups - Remove scanning groups
  • Create rules - Define patterns to detect sensitive data
  • Update rules - Modify detection patterns and redaction methods
  • Delete rules - Remove scanning rules
  • List standard patterns - Browse built-in detection patterns
  • Reorder groups - Control processing priority

4. IP Allowlist (Enterprise)

  • View IP Allowlist - Get current IP allowlist configuration
  • Manage IP Entries - Add, remove, or update IP address ranges (CIDR blocks)
  • Enable/Disable - Control IP allowlist enforcement
  • Access Control - Restrict API and UI access to specific IP ranges

Read the full file on GitHub · 746 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. 2d ago First seen · 746 lines · 39 tokens per session scan A a651c94f6736

Subscribe to this mod's changes

data-governance is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 39 tokens to every session and 5,977 once invoked, about $0.0002 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-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