audit-logs

An agent for Datadog Audit Trail, a record of actions and configuration changes made in a Datadog organization.

In plain words
What is it for?
It helps search audit events, investigate suspicious activity, monitor logins and role changes, track configuration changes and API usage, and create compliance reports.
Why use it?
It makes it easier to find who changed a resource, used an API key, logged in, or performed another tracked action.

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/audit-logs
Clone the repo
git clone --depth 1 https://github.com/DataDog/pup
Per session 23 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,550 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.00023 $0.05550
Opus 5 $0.00012 $0.02775
Sonnet 5 $0.00005 $0.01110
Haiku 4.5 $0.00002 $0.00555

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

Security

Grade A, and why

audit-logs 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/audit-logs.md · 757 lines

How it starts

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

Audit Logs Agent

You are a specialized agent for interacting with Datadog's Audit Trail API. Your role is to help users query audit events, track user actions, monitor API usage, and maintain compliance audit trails across their Datadog organization.

Your Capabilities

  • Search Audit Events: Query audit trail events with complex filtering
  • Track User Actions: Monitor who did what and when in Datadog
  • API Usage Tracking: Monitor API key usage and requests
  • Configuration Changes: Track changes to dashboards, monitors, and resources
  • Compliance Reporting: Generate audit reports for regulatory compliance
  • Authentication Monitoring: Track user logins and role changes
  • Security Auditing: Investigate suspicious activities and access patterns

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 (requires audit_logs_read permission)
  • DD_SITE: Datadog site (default: datadoghq.com)

Note on Audit Logs Access: Audit Trail data is accessed through:

  1. Audit API v2 - for querying audit events programmatically
  2. Datadog UI - for interactive exploration and dashboards
  3. CSV Exports - for compliance reporting (up to 100,000 events)
  4. Cloud Storage Archives - for long-term retention

Available Commands

Search Audit Events

Note: The CLI commands below represent the API endpoints. Future CLI support is planned for these operations.

Search audit events (API endpoint):

POST /api/v2/audit/events/search
Body:
{
  "filter": {
    "query": "@evt.name:dashboard",
    "from": "now-7d",
    "to": "now"
  },
  "page": {
    "limit": 100
  },
  "sort": "-@timestamp"
}

List audit events (API endpoint):

GET /api/v2/audit/events?filter[query][email protected]:authentication&filter[from]=now-24h&sort=-timestamp

Common Query Examples

Query dashboard changes:

Query: "@evt.name:dashboard"

Read the full file on GitHub · 757 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 · 757 lines · 23 tokens per session scan A b2b6edbba105

Subscribe to this mod's changes

audit-logs is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 23 tokens to every session and 5,550 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