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/usage-meteringgit 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.00031 | $0.00863 |
| Opus 5 | $0.00015 | $0.00432 |
| Sonnet 5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
usage-metering 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage Metering Agent
You help users inspect Datadog usage data through the pup CLI. Use only the
usage commands that are currently implemented by this repository.
Authentication
pup usage requires Datadog credentials for an organization with usage access:
- OAuth2 authentication from
pup auth login, or DD_API_KEY,DD_APP_KEY, andDD_SITE
The Datadog user or keys must have usage_read. An OAuth token scope is not
enough if the Datadog role itself does not grant the permission.
Implemented Commands
pup usage currently exposes two subcommands:
pup usage summary
pup usage hourly
Do not call product-specific usage subcommands for hosts, logs, log indexes,
custom metric timeseries, top metrics, cost by org, or billable summaries under
pup usage. They are not part of the current CLI surface.
Cost commands live under pup costs datadog, not under pup usage.
Time Flags
Both implemented usage commands use the same flags:
--from: start time--to: optional end time
Accepted values:
now- Relative durations such as
1h,30m,7d,5minutes - Calendar months such as
2024-01 - Calendar dates such as
2024-01-01 - RFC3339 timestamps such as
2024-01-01T00:00:00Z - Unix timestamps in seconds or milliseconds
Calendar month and date values are interpreted as midnight UTC at the start of the month or date.
Usage Summary
Use summary for aggregated usage summary data.
pup usage summary --from="2024-01" --to="2024-02"
The command defaults to --from="30d" when no start time is provided:
pup usage summary
Use month boundaries for month-granularity questions:
pup usage summary --from="2024-01-01" --to="2024-02-01"
Hourly Usage
Use hourly for hourly usage data.
pup usage hourly --from="2024-01-01" --to="2024-01-02"
The command defaults to --from="1d" when no start time is provided:
pup usage hourly
Use RFC3339 timestamps when the user asks for exact hourly windows:
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 · 127 lines · 31 tokens per session scan A 6c0c6b452a5a
usage-metering is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 31 tokens to every session and 863 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…