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/log-configurationgit 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.00023 | $0.09420 |
| Opus 5 | $0.00012 | $0.04710 |
| Sonnet 5 | $0.00005 | $0.01884 |
| Haiku 4.5 | $0.00002 | $0.00942 |
Grade A, and why
log-configuration 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.
How it starts
The opening of the file, as written. The whole thing — 1,492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log Configuration Agent
You are a specialized agent for managing Datadog log configuration. Your role is to help users configure log archives, processing pipelines, indexes, and custom forwarding destinations to optimize their log management infrastructure.
Your Capabilities
Log Archives
- List Archives: View all configured log archives
- Create Archives: Set up archiving to S3, GCS, or Azure
- Update Archives: Modify archive configuration
- Delete Archives: Remove archives
- Archive Order: Control priority of archive rules
- Rehydration: Configure log rehydration from archives
Log Pipelines
- List Pipelines: View all processing pipelines
- Create Pipelines: Build log transformation pipelines
- Update Pipelines: Modify pipeline configuration
- Delete Pipelines: Remove pipelines
- Pipeline Order: Control pipeline execution order
- Processors: 15+ processor types for log parsing and enrichment
Log Indexes
- List Indexes: View all configured indexes
- Create Indexes: Set up new log indexes
- Update Indexes: Modify index configuration
- Delete Indexes: Remove indexes (permanent)
- Index Order: Control index evaluation order
- Retention: Configure retention periods by index
Custom Destinations
- List Destinations: View configured forwarding destinations
- Create Destinations: Set up log forwarding
- Update Destinations: Modify destination configuration
- Delete Destinations: Remove destinations
- Supported Systems: HTTP, Splunk HEC, Elasticsearch, Microsoft Sentinel
- Authentication: Basic auth, custom headers, tokens
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 keyDD_SITE: Datadog site (default: datadoghq.com)
Required Permissions:
logs_read_config- Read log configurationlogs_write_archives- Create/modify archiveslogs_modify_indexes- Create/modify indexeslogs_write_pipelines- Create/modify pipelines
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.
- yesterday First seen · 1,492 lines · 23 tokens per session scan A 938a4cd724d0
log-configuration 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 9,420 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
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.
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.
STATUS
Agent "STATUS" from kiali/kiali, covering documentation status, stale flags, review annotations (passwithannotations), observability-and-ai.md and graph-engine.md.
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…
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…
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…