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 skills/datadog/pup/dd-file-issuenpx skills add DataDog/pup --skill dd-file-issuegit 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.00020 | $0.02266 |
| Opus 5 | $0.00010 | $0.01133 |
| Sonnet 5 | $0.00004 | $0.00453 |
| Haiku 4.5 | $0.00002 | $0.00227 |
Grade A, and why
dd-file-issue 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DD File Issue Skill
This skill helps you file GitHub issues to the correct repository. All issues — whether related to the pup CLI, skills, agents, or documentation — are tracked in DataDog/pup.
Invocation: /dd-file-issue
Decision Logic: Which Repository?
File to DataDog/pup Repository
All issues are filed here, including:
- API Functionality: API calls failing, incorrect responses, missing API endpoints
- Authentication: OAuth2 issues, token refresh problems, API key handling
- CLI Behavior: Command syntax, flags not working, output format issues
- pup Installation: Binary installation, PATH issues, version problems
- API Coverage: Missing Datadog API endpoints, incomplete command coverage
- Performance: Slow API calls, timeout issues
- Error Messages: Confusing pup error messages, API errors
- Agent Behavior: Agent selection, agent prompts, agent responses
- Documentation: README, CLAUDE.md, AGENTS.md, agent files inaccurate
- Agent Prompts: Agent giving wrong guidance, unclear instructions
- Skill Issues: Skills not working correctly
- Agent Selection: Claude picking wrong agent for task
- Examples/Guides: Missing or incorrect examples in agent files
- User Experience: Confusing workflows, unclear instructions
Example Issues:
- "pup logs search returns 404 error"
- "OAuth token refresh not working"
- "Need support for new Datadog API endpoint"
- "pup --output=json returns invalid JSON"
- "pup auth login fails on Linux"
- "logs agent doesn't explain query syntax clearly"
- "Agent tells me to use wrong pup command"
- "Documentation says to use TypeScript but we use pup now"
- "Need better examples for metrics queries"
- "Agent selection guide is confusing"
Workflow
-
Gather Information
- What went wrong?
- What were you trying to do?
- What error message did you see (if any)?
- What agent/command were you using?
-
Determine Repository
- All issues go to
DataDog/pup
- All issues go to
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 · 346 lines · 20 tokens per session scan A 870aa7df23bc
dd-file-issue is a skill published in the GitHub repository DataDog/pup (999 stars, last pushed 5d ago), licensed Apache-2.0. It adds 20 tokens to every session and 2,266 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 skills, from other repositories
github-ci-fix-onboarding
Onboards and troubleshoots GitHub PR CI fixing by configuring GitHub CLI authentication, a non-exposed GitHub token, a matching local checkout, and a ready coding agent before running fixgithubprci. Use for first-time setup, failed prerequisites, demos, or action-shaped requests to onboard the user onto the local…
posthog-summary
Summarise PostHog product analytics into a per-metric team pulse. Use for PostHog usage overviews, per-metric summaries, product-analytics digests, or "what happened this week" reporting.
yandex-cloud
Read Yandex Cloud through its REST API. Applies to any question about VMs, metrics, logs, audit events, Kubernetes, managed databases, serverless, networking or any other Yandex Cloud resource. Never shell out to the yc CLI — it is not how this agent reaches Yandex Cloud and is usually not installed.
architecture-audit
Architecture audit / layering scan of a repo with AGENT SCAN, heuristic passes, and a filled REPORT TEMPLATE.
morning-report
Weather + news morning briefing: fetch live weather and headlines, compose a plain-text briefing, deliver it. Multi-step; load before acting.
github-security-fix
Remediate GitHub security / Dependabot / CodeQL / code-quality alerts via fixgithubsecurityalert.