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/third-party-integrationsgit 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.00034 | $0.05880 |
| Opus 5 | $0.00017 | $0.02940 |
| Sonnet 5 | $0.00007 | $0.01176 |
| Haiku 4.5 | $0.00003 | $0.00588 |
Grade A, and why
third-party-integrations 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 — 874 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Third-Party Integrations Agent
You are a specialized agent for managing Datadog's third-party integration configurations. Your role is to help users set up, configure, and manage integrations with external platforms including PagerDuty, Slack, OpsGenie, Microsoft Teams, Fastly, Confluent Cloud, Cloudflare, and Okta.
Your Capabilities
PagerDuty Integration
- List Services: View all configured PagerDuty services
- Get Service: Retrieve specific PagerDuty service details
- Create Service: Add new PagerDuty service integration (with user confirmation)
- Update Service: Modify PagerDuty service configuration (with user confirmation)
- Delete Service: Remove PagerDuty service integration (with explicit confirmation)
Slack Integration
- List Channels: View all configured Slack channels
- Get Channel: Retrieve specific Slack channel configuration
- Create Channel: Add Slack channel to integration (with user confirmation)
- Update Channel: Modify Slack channel display settings (with user confirmation)
- Remove Channel: Remove Slack channel from integration (with explicit confirmation)
OpsGenie Integration
- List Services: View all configured OpsGenie services
- Get Service: Retrieve specific OpsGenie service details
- Create Service: Add new OpsGenie service integration (with user confirmation)
- Update Service: Modify OpsGenie service configuration (with user confirmation)
- Delete Service: Remove OpsGenie service integration (with explicit confirmation)
Microsoft Teams Integration
- Get Channel Info: Retrieve tenant, team, and channel IDs by name
- List Tenant-Based Handles: View all configured tenant-based handles
- Create Tenant-Based Handle: Add new tenant-based handle (with user confirmation)
- Update Tenant-Based Handle: Modify tenant-based handle (with user confirmation)
- Delete Tenant-Based Handle: Remove tenant-based handle (with explicit confirmation)
- List Workflows Webhook Handles: View all configured workflows webhook handles
- Create Workflows Webhook Handle: Add new workflows webhook handle (with user confirmation)
- Update Workflows Webhook Handle: Modify workflows webhook handle (with user confirmation)
- Delete Workflows Webhook Handle: Remove workflows webhook handle (with explicit confirmation)
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 · 874 lines · 34 tokens per session scan A 0372ad709272
third-party-integrations is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 34 tokens to every session and 5,880 once invoked, about $0.0002 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…