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 automateyournetwork/netclaw --skill datadog-logsgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/datadog-logs)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/datadog-logs"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/datadog-logs/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/automateyournetwork/netclaw/datadog-logs"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/datadog-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 44 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00017 | $0.00518 |
| Opus 5 | $0.00009 | $0.00259 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade B, and why
datadog-logs scanned grade B with 1 finding 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 9d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
3. Check for privilege escalation: `search_logs(query="@action:sudo OR @action:su")` What it actually says
Datadog Logs Skill
Search and analyze logs in Datadog Log Management.
Tools
| Tool | Description |
|---|---|
search_logs |
Search logs with query syntax, time range, and filters |
get_log_details |
Get detailed information about a specific log entry |
list_log_indexes |
List all available log indexes |
get_log_pipeline |
Get log pipeline configuration for processing |
Example Queries
Search for error logs in the network service
→ search_logs(query="service:network status:error", time_range="1h")
Find all logs from a specific host
→ search_logs(query="host:router-core-01", time_range="15m")
Get logs with a specific trace ID
→ search_logs(query="trace_id:abc123", time_range="1d")
List all log indexes
→ list_log_indexes()
Workflows
Security Event Hunting
- Search for authentication failures:
search_logs(query="@auth.status:failed") - Correlate by source IP:
search_logs(query="@network.client.ip:10.0.0.1") - Check for privilege escalation:
search_logs(query="@action:sudo OR @action:su") - Review timeline and patterns
Network Log Correlation
- Search interface events:
search_logs(query="service:network @interface.status:down") - Correlate with routing changes:
search_logs(query="@event.type:bgp_state_change") - Check for cascading failures across regions
- Build incident timeline
Syslog Analysis
- Search by facility:
search_logs(query="@syslog.facility:local0") - Filter by severity:
search_logs(query="@syslog.severity:<4")(warning and above) - Aggregate by host and time window
- Identify anomalous patterns
Prerequisites
DD_API_KEYDatadog API keyDD_APP_KEYDatadog application keyDD_SITEDatadog site (optional, defaults to datadoghq.com)
Server
This skill uses the datadog-mcp server via remote MCP transport.
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.
- 9d ago First seen · 68 lines · 17 tokens per session scan B f5e6faa3a21b
datadog-logs is a skill published in the GitHub repository automateyournetwork/netclaw (651 stars, last pushed 2d ago), licensed Apache-2.0. It adds 17 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.