AI Tool Profile
Datadog Pup CLI and Agent Skills: Security and Evaluation
Datadog Pup is an agent-oriented CLI with dynamic command schemas and structured output across observability, delivery, security and service-management workflows, accompanied by reusable Agent Skills.
Verification & Sources
- Evidence state
- Recheck due
- Source links
- 5
- Freshness
- Needs recheck: checked July 27, 2026
- Last updated
- July 28, 2026
What this evidence state means
- Definition
- The claim was previously checked, but its review window expired or a material change may have invalidated it.
- Required provenance
- The prior evidence and check date are retained, together with the expiry or change signal that triggered recheck.
- Owner
- Kingy freshness queue owner and assigned editorial reviewer
- Freshness rule
- This is already outside its freshness rule. It must not be presented as current until reviewed against current evidence.
- Disputes and corrections
- Use “Suggest a correction” on the record. Kingy editorial reviews the cited evidence, records material corrections, and changes or removes the state when it is not supported.
Key source checks
Suggest a correction
Kingy verdict: Datadog Pup is a serious operational interface for terminal-native agents, not a harmless read-only helper. Its dynamic schema, structured output and OAuth/RBAC model are useful foundations, but the same CLI can reach configuration and destructive commands across a wide Datadog surface.
What Pup adds
Pup is a Rust CLI covering more than 200 commands across more than 33 Datadog product domains. It returns JSON or YAML by default and exposes its command tree through pup agent schema, allowing an agent to load the commands it needs instead of keeping a large static tool catalog in context. The launch guide distinguishes this shell-native workflow from Datadog’s conversational MCP Server. Pup also offers a local ACP server for compatible clients.
The public Agent Skills repository packages workflows for monitors, logs, APM, documentation, agent observability, browser telemetry, audit investigations, software delivery and security ownership. Pup is Apache-2.0 licensed; the separate skills repository is MIT licensed. Open-source clients do not make the Datadog data or underlying services free.
Authentication and control boundaries
The preferred login uses OAuth 2.0 with PKCE, revocable tokens and existing Datadog role-based access control. The repository notes that Dynamic Client Registration must be enabled for this path; otherwise Pup can fall back to API and application keys. OAuth credentials use the platform’s secure store by default, while headless and WASM environments require bearer tokens or keys and do not support browser login.
Inherited RBAC is necessary but not sufficient for agent safety. The documented command examples include deletion, monitor changes, incident access and broad API-backed administration. A human’s role may be wider than the minimum an automated workflow needs. Teams should create a purpose-scoped identity, separate read investigations from mutations, require confirmation for destructive actions, and verify that audit trails distinguish the agent, user and command source.
Pricing and operational cost
Pup and the Agent Skills repositories are public, but Datadog product usage follows the account’s contracts and product-specific meters. A command that queries logs, traces, incidents or cloud-cost data can consume or expose services with different retention and billing models. Public pricing does not define one universal “Pup plan,” so estimate cost from the exact products, data volume and automation frequency in the trial.
How Kingy would evaluate it
Begin with a read-only role and three tasks: retrieve one monitor, search a narrow log window and correlate an incident with a trace. Measure command-schema discovery, output stability, token use, permission failures and audit attribution. Then test one reversible write behind explicit approval. Include expired OAuth, revoked roles, multi-organization selection, a missing DCR configuration and fallback-key leakage. Do not grant broad production access until the workflow fails safely.
Kingy reviewed the launch guide, repositories, API documentation and pricing surface. We did not authenticate to Datadog or execute Pup, and we did not validate the provider’s command-count or product-domain claims independently.
A production pilot should also define a command allowlist, maximum query windows, output-retention rules and an emergency revocation path. Those controls matter because a technically valid command can still be operationally excessive, expensive or inappropriate for the incident at hand.
Primary sources
- Datadog Pup launch guide
- Pup source repository and authentication documentation
- Datadog Agent Skills repository
- Datadog API documentation
- Datadog pricing
The Kingy Brief
Follow The Kingy Brief.
One consequential launch, one pricing, limit, or shutdown change, one hands-on test, one exact prompt or Test Pack, and one try / watch / skip verdict.
Free · Choose your subjects · Double opt-in · Unsubscribe anytime
Tool Links
Launch History
Datadog Pup CLI and Agent Skills
Datadog introduced Pup, an Apache-2.0 agent-oriented CLI with dynamic schemas and structured output across more than 200 commands, alongside a separate MIT-licensed Agent Skills repository.
- Launch readiness
- 8.0 / 10
- Demo evidence
- Not scored yet
- Creator-story fit
- Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.
- Scale
- 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
- Assigned by
- Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
- Rubric and check date
- Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-27.
- Confidence and missing data
- Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
- Freshness
- Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
- Disputes
- Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Datadog Pup is a practical fit for SRE teams that need structured, terminal-native investigations under a purpose-scoped identity. Its OAuth, inherited RBAC and dynamic…