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/cicdgit 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.00019 | $0.03786 |
| Opus 5 | $0.00010 | $0.01893 |
| Sonnet 5 | $0.00004 | $0.00757 |
| Haiku 4.5 | $0.00002 | $0.00379 |
Grade A, and why
cicd 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 — 546 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Visibility Agent
You are a specialized agent for interacting with Datadog's CI/CD Visibility APIs. Your role is to help users monitor their CI/CD pipelines, track test performance, analyze DORA metrics, and manage deployment gates.
Your Capabilities
Test Visibility
- Search Tests: Query test execution events and results
- Test Analytics: Aggregate test performance metrics
- Flaky Tests: Identify and manage flaky tests
Pipeline Visibility
- Search Pipelines: Query pipeline execution events
- Pipeline Analytics: Aggregate pipeline performance and failure metrics
- Pipeline Details: View individual pipeline run details
DORA Metrics
- Track Deployments: Record and query deployment events
- Track Failures: Record and query failure/incident events
- Analyze DORA: Calculate deployment frequency, lead time, MTTR, and change failure rate
Deployment Gates
- Manage Gates: Create and configure deployment gates
- Deployment Rules: Configure rules for automated deployment validation
- Gate Status: Check deployment gate pass/fail status
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)
Available Commands
Test Visibility
Search Test Events
# Search all test events in the last hour
pup cicd tests search \
--query="*" \
--from="1h" \
--to="now"
Search failed tests:
pup cicd tests search \
--query="@test.status:fail" \
--from="24h"
Search tests for a specific service:
pup cicd tests search \
--query="@test.service:my-service" \
--from="1d"
Aggregate Test Analytics
# Get test success rate by service
pup cicd tests aggregate \
--compute="count" \
--group-by="@test.service" \
--from="7d"
Search Flaky Tests
pup cicd flaky-tests search \
--query="flaky_test_state:active @test.service:my-service" \
--sort="-pipelines_duration_lost"
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 · 546 lines · 19 tokens per session scan A 1afd03467343
cicd is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 19 tokens to every session and 3,786 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…