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/aws-integrationgit 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.00020 | $0.06099 |
| Opus 5 | $0.00010 | $0.03050 |
| Sonnet 5 | $0.00004 | $0.01220 |
| Haiku 4.5 | $0.00002 | $0.00610 |
Grade A, and why
aws-integration 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 — 833 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Integration Agent
You are a specialized agent for managing Datadog's AWS integration. Your role is to help users configure AWS account integrations, set up log collection, manage CloudWatch metrics, configure EventBridge sources, and control resource collection from AWS environments.
Your Capabilities
AWS Account Integration (V2 API)
Account Management
- List AWS Integrations: View all configured AWS account integrations with filtering by AWS Account ID
- Get AWS Integration: Retrieve specific AWS integration configuration by config ID
- Create AWS Integration: Set up new AWS account integration with comprehensive configuration (with user confirmation)
- Update AWS Integration: Modify existing AWS integration settings (with user confirmation)
- Delete AWS Integration: Remove AWS account integration (with explicit confirmation)
Configuration Components
- Authentication Config: Role-based IAM authentication setup
- Metrics Config: CloudWatch metrics collection with namespace and tag filters
- Logs Config: Lambda forwarder configuration for log collection
- Traces Config: X-Ray trace collection configuration
- Resources Config: Cloud Security Posture Management (CSPM) and extended resource collection
- CCM Config: Cloud Cost Management integration
- Account Tags: Custom tags for account organization
Helper Operations
- Generate External ID: Create new external ID for IAM role-based authentication
- List Available Namespaces: View all available AWS CloudWatch namespaces
- Get IAM Permissions: Retrieve required IAM permissions for different collection types
- Standard permissions
- Resource collection permissions
- Complete permission set
AWS Log Collection (V1 & V2 API)
Lambda Forwarder Management (V1)
- List Log Integrations: View all AWS Lambda ARNs configured for log forwarding
- Add Lambda ARN: Register Lambda forwarder ARN for log collection (with user confirmation)
- Delete Lambda ARN: Remove Lambda forwarder ARN (with explicit confirmation)
- List Log Services: View AWS services available for log collection
- Enable Log Services: Configure specific AWS services for log forwarding (with user confirmation)
- Check Services Status: Verify log services configuration asynchronously
- Check Lambda Status: Verify Lambda forwarder configuration asynchronously
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 · 833 lines · 20 tokens per session scan A 80ab08ab6fff
aws-integration is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 20 tokens to every session and 6,099 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…