Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/.agents/skills/datadog-analysis/SKILL.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/packmindhub/packmind/datadog-analysis)<a href="https://agentmods.dev/skills/packmindhub/packmind/datadog-analysis"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/datadog-analysis/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/packmindhub/packmind/datadog-analysis"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/datadog-analysis.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.00068 | $0.01542 |
| Opus 5.5 | $0.00027 | $0.00617 |
| Sonnet 5.5 | $0.00014 | $0.00308 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
datadog-analysis 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Datadog Analysis
Analyze production error logs from Packmind Datadog services, group them into patterns, cross-reference stack traces with the codebase, and produce a structured markdown report with root causes and Datadog search patterns.
Prerequisites
- The Datadog MCP server must be connected. If not connected, prompt the user to run
/mcpfirst. - Read
references/datadog_mcp.mdbefore making any MCP tool calls for guidance on tool usage, gotchas, and known pitfalls.
Services
The analysis covers two production services. Each maps to a Datadog service name, a codebase location, and a Dockerfile:
| Datadog service | App | Codebase | Dockerfile | Runtime |
|---|---|---|---|---|
api-proprietary |
API | apps/api/ + all packages/ |
dockerfile/Dockerfile.api |
Node.js (NestJS, TypeORM, Redis/ioredis, BullMQ) |
frontend-proprietary |
Frontend | apps/frontend/ |
dockerfile/Dockerfile.frontend |
Nginx (static SPA serving) |
Root cause analysis should trace errors back to source files in the monorepo. For Nginx (frontend), also check the Nginx configs in dockerfile/nginx.*.conf and the entrypoint dockerfile/nginx-entrypoint.sh.
Parameters
| Parameter | Default | Description |
|---|---|---|
| Days to analyze | 7 | Number of past days to look at. Override by user request (e.g., "last 3 days") |
Exclusions
The following log patterns should be discarded and not included in the report. Skip them during pattern discovery and do not count them as errors:
-
(node:1) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead.-- Known Node.js deprecation from a transitive dependency. Noise, not actionable. Filter with-DEP0060. -
Nginx stale asset 404s (
open() "/usr/share/nginx/html/assets/..." failed (2: No such file or directory)) -- Expected SPA behavior after deployments. Browsers with a cachedindex.htmlrequest old hashed JS chunks that no longer exist. Not a bug. Filter with-"No such file or directory" -"/assets/"onfrontend-proprietary.
What ships with it
3 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 · 101 lines · 68 tokens per session scan A 3778e1d01686
datadog-analysis is a skill published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,542 once invoked, about $0.0003 per session on Opus 5.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-09-22.
Other skills, from other repositories
context-align
Checks AGENTS.md and SKILL.md files against the actual codebase for drift. Surfaces references to packages, directories, commands, or patterns that no longer match reality.
gsd-debug
Systematic debugging with persistent state across context resets.
gsd-debug
Systematic debugging with persistent state across context resets.
gsd-ns-review
Invoke this Pi skill with /skill:gsd-ns-review.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
openocd
A toolkit for programming and debugging microcontrollers through hardware probes such as ST-Link or CMSIS-DAP. OpenOCD can act as a GDB Server, allowing a debugger to inspect source code, registers, memory, breakpoints, and program execution.