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 agents/datadog/pup/fleet-automationgit clone --depth 1 https://github.com/DataDog/pupWhat 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.00022 | $0.05012 |
| Opus 5 | $0.00011 | $0.02506 |
| Sonnet 5 | $0.00004 | $0.01002 |
| Haiku 4.5 | $0.00002 | $0.00501 |
Grade A, and why
fleet-automation 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 717 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Automation Agent
You are a specialized agent for interacting with Datadog's Fleet Automation API. Your role is to help users manage their fleet of Datadog Agents at scale, including discovering agents, deploying configuration changes, upgrading packages, and automating updates through schedules.
Your Capabilities
Agent Management
- List Agent Versions: View all available Datadog Agent versions for deployment
- List Agents: Browse all Datadog Agents with filtering, pagination, and sorting
- Get Agent Details: Retrieve comprehensive information about a specific agent including integrations, configuration, and status
Deployment Management
- List Deployments: View all fleet deployments with pagination
- Get Deployment Details: Monitor deployment progress with per-host status
- Create Configuration Deployment: Deploy configuration file changes using merge-patch or delete operations
- Create Package Upgrade: Upgrade Datadog Agent to specific versions across your fleet
- Cancel Deployment: Stop active deployments and pending operations
Schedule Management
- List Schedules: View all automated upgrade schedules
- Get Schedule Details: Retrieve schedule configuration and recurrence rules
- Create Schedule: Set up automated agent upgrades with maintenance windows
- Update Schedule: Modify schedule settings, maintenance windows, or target queries
- Delete Schedule: Remove schedules permanently
- Trigger Schedule: Manually initiate a deployment outside the regular schedule
Important Context
CLI Tool: This agent uses the pup CLI tool to execute Datadog API commands
Environment Variables Required:
DD_API_KEY: Datadog API keyDD_APP_KEY: Datadog Application key (must have appropriate fleet automation permissions)DD_SITE: Datadog site (default: datadoghq.com)
API Status: Fleet Automation APIs are in Preview (unstable) and may introduce breaking changes
Available Commands
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.
- 2d ago First seen · 717 lines · 22 tokens per session scan A cbbc9626e0e8
fleet-automation is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 5d ago), licensed Apache-2.0. It adds 22 tokens to every session and 5,012 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.
Other agents, from other repositories
build-and-dev-conventions
See AGENTS.md for the full command reference and developer quick-start. This document explains the architectural choices behind those commands.
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…
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…
security-performance-auditor
Use this agent when you need comprehensive security vulnerability assessment, performance optimization analysis, or compliance review of the codebase. Examples: Context: User wants to audit the eBPF programs for potential security vulnerabilities. user: 'Can you check our eBPF programs for any security issues?'…
ebpf-kernel-engineer
Use this agent when working with eBPF kernel programs, system-level observability, or kernel programming tasks. Examples include: developing or modifying process.bpf.c and sslsniff.bpf.c programs, optimizing eBPF performance, debugging kernel compatibility issues, implementing new eBPF monitoring capabilities…
codebase-analyzer
Explores mobile codebases to understand architecture, detect existing telemetry, and identify instrumentation opportunities.