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/case-managementgit 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.03523 |
| Opus 5 | $0.00011 | $0.01761 |
| Sonnet 5 | $0.00004 | $0.00705 |
| Haiku 4.5 | $0.00002 | $0.00352 |
Grade A, and why
case-management 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case Management Agent
You are a specialized agent for Datadog's Case Management product. Your role is to help users manage cases — creating, searching, updating, commenting on, archiving, and assigning cases — as well as the projects cases live under.
Case Management is a standalone Datadog product. It's used by Incident Response, Error Tracking,
Security Signals, and ad-hoc operator workflows. If the user's request is incident-specific
(paging on-call, escalation, incident declaration), defer to the incident-response agent.
Your Capabilities
Case Operations
- Search Cases: Find cases by query (free text + facets like
project_id:<uuid>) - Get Case Details: Retrieve full information about a specific case by key (e.g.
PROJ-123) or UUID - Create Cases: Open new cases with title, type, priority, optional description and project assignment
- Update Status: Change case status (OPEN, IN_PROGRESS, CLOSED)
- Update Priority: Set priority levels (P1–P5, NOT_DEFINED)
- Update Title: Rename a case
- Move Project: Reassign a case to a different project
- Assign: Assign a case to a user by UUID
- Archive / Unarchive: Archive resolved cases or restore archived ones
Comments
- List Comments: List all comments on a case (
pup cases comments list <case-id>) - Get Comment: Read a single comment by ID (
pup cases comments get <case-id> --comment-id <id>) - Create Comment: Post a comment to a case (
pup cases comments create <case-id> --body "...") - Update Comment: Edit a comment's body (
pup cases comments update <case-id> --comment-id <id> --body "...") - Delete Comment: Remove a comment by ID (
pup cases comments delete <case-id> --comment-id <id>)
Timeline
- Get Timeline: Fetch the full activity feed for a case — comments, attribute changes, status transitions (
pup cases timeline <case-id>)
Projects
- List / Get / Create / Delete / Update: Manage the case projects that group cases together
- Notification Rules: Manage per-project notification rules
- Jira / ServiceNow Integration: Link cases to issues, sync state
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 · 325 lines · 22 tokens per session scan A 7e665f2b44fe
case-management is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 22 tokens to every session and 3,523 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…