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 skills add Dannykkh/skill-olympus --skill datadog-cligit clone --depth 1 https://github.com/Dannykkh/skill-olympusWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dannykkh/skill-olympus/datadog-cli)<a href="https://agentmods.dev/skills/dannykkh/skill-olympus/datadog-cli"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/datadog-cli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dannykkh/skill-olympus/datadog-cli"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/datadog-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00077 | $0.01438 |
| Opus 5.5 | $0.00031 | $0.00575 |
| Sonnet 5.5 | $0.00015 | $0.00288 |
| Haiku 4.5 | $0.00008 | $0.00144 |
Grade A, and why
datadog-cli 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 1mo 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.
This is a copy
86% identical to datadog-cli — 37 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Datadog CLI
A CLI tool for AI agents to debug and triage using Datadog logs and metrics.
Required Reading
You MUST read the relevant reference docs before using any command:
Setup (최초 1회)
이 스킬은 config.json에 설정이 필요합니다.
config.json을 읽는다 (skills/datadog-cli/config.json또는 현재 CLI의 글로벌 스킬 경로)- 빈 필드가 있으면 현재 CLI의 질문 방식으로 사용자에게 질문한다
- 답변을
config.json에 저장한다 - 이후 실행 시에는
config.json에서 자동으로 읽는다
| 항목 | 설명 | 예시 |
|---|---|---|
dd_site |
Datadog 사이트 도메인 | datadoghq.com / datadoghq.eu |
default_service |
기본 서비스명 (쿼리 자동완성에 사용) | api-server |
default_env |
기본 환경 | production / staging |
log_index |
기본 로그 인덱스 | main |
Setup 로직:
config.json 읽기
├─ dd_site가 기본값(datadoghq.com)이면 → "Datadog 사이트를 확인해주세요 (EU 사용자: datadoghq.eu, 맞으면 Enter)"
├─ default_service 비어있음? → "주로 조회할 서비스명을 입력해주세요 (예: api-server, 건너뛰려면 Enter)"
├─ default_env 비어있음? → "기본 환경을 입력해주세요 (예: production, staging)"
└─ 답변 수집 후 config.json에 저장 → 이후 자동 사용
모든 필드가 채워져 있으면 이 단계를 건너뜁니다.
config.json의dd_site값은--site플래그로 자동 주입됩니다.
Setup
Environment Variables (Required)
export DD_API_KEY="your-api-key"
export DD_APP_KEY="your-app-key"
Get keys from: https://app.datadoghq.com/organization-settings/api-keys
Running the CLI
npx @leoflores/datadog-cli <command>
For non-US Datadog sites, use --site flag:
npx @leoflores/datadog-cli logs search --query "*" --site datadoghq.eu
Commands Overview
| Command | Description |
|---|---|
logs search |
Search logs with filters |
logs tail |
Stream logs in real-time |
logs trace |
Find logs for a distributed trace |
logs context |
Get logs before/after a timestamp |
logs patterns |
Group similar log messages |
logs compare |
Compare log counts between periods |
logs multi |
Run multiple queries in parallel |
logs agg |
Aggregate logs by facet |
metrics query |
Query timeseries metrics |
errors |
Quick error summary by service/type |
services |
List services with log activity |
dashboards |
Manage dashboards (CRUD) |
dashboard-lists |
Manage dashboard lists |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 163 lines · 77 tokens per session scan A bfc7707b30ed
datadog-cli is a skill published in the GitHub repository Dannykkh/skill-olympus (7 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 1,438 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to datadog-cli, differing in 37 lines, and is treated as a copy.
Other skills, from other repositories
error-analyzer
Systematic root-cause analysis for build failures, test errors, and runtime issues. Use when: "error", "failed", "broken", "debug", "why did this fail", "root cause".
debug-team
Launch parallel debugging agents for systematic root-cause analysis. Use when: "debug team", "help me debug", "debug-team", "find the bug".
audit-project
Audits the Claude Code configuration of a project against the dotforge template. Generates a report with score and gaps.
init-project
Quick-start Claude Code configuration. Auto-detects stack, asks 4 questions to understand the project, generates complete config.
domain-extract
Extract domain knowledge from existing project sources and generate domain rules. Also handles vault sync and domain listing.
rule-effectiveness
Cross-reference .claude/rules/ globs against git history to find inert rules and uncovered directories. Content quality and context cost are native — run /doctor prompt-audit and /skill-doctor for those.