Borrowing it
Nothing to install: this file belongs to dash0hq/agent-skills. 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/dash0hq/agent-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/dash0hq/agent-skillsWrote 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/instructions/dash0hq/agent-skills/claude-md)<a href="https://agentmods.dev/instructions/dash0hq/agent-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/dash0hq/agent-skills/claude-md.svg" alt="Measured on agentmods" 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.01575 | $0.01575 |
| Opus 5 | $0.00788 | $0.00788 |
| Sonnet 5 | $0.00315 | $0.00315 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
agent-skills CLAUDE.md 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 8d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent rules
Audience
The skills in this repository are consumed operationally by agentic frameworks (AI coding agents, copilots, and autonomous developer tools). Every piece of guidance must be written so that an agent can act on it without human interpretation.
When writing or editing skill content, follow these principles:
- Be prescriptive, not descriptive.
Tell the agent what to do (
Use a Histogram) rather than explaining concepts (Histograms capture distributions). Explanations are acceptable only when they inform the decision. - Make decisions enumerable. When multiple options exist, provide a numbered decision process, a lookup table, or explicit criteria — not open-ended advice.
- Include code examples for every actionable rule.
An agent generating code needs a template to follow.
Show both the correct pattern and, where useful, the incorrect one labelled
// BAD. - Avoid subjective conditions. Do not write "if the user wants" or "it is likely that." State concrete, testable criteria the agent can evaluate from the code or configuration it has access to.
- Keep rules self-contained. An agent may load a single rule file without reading the rest of the skill. Each file must make sense on its own; use cross-references for detail, not for essential context.
Skill separation of concerns
otel-instrumentation vs otel-collector
These two skills have a strict boundary: application code vs Collector configuration.
otel-instrumentationcovers the application and its deployment: SDK setup, environment variables (OTEL_SERVICE_NAME,OTEL_RESOURCE_ATTRIBUTES, etc.), resource attributes, instrumentation libraries, and the Kubernetes workload resources and pod specs that deploy the application (e.g., downward API configuration, container env blocks, secret references for auth tokens in Kubernetes).otel-collectorcovers what happens inside the OpenTelemetry Collector process: receivers, processors (memory_limiter,batch,k8sattributes,resourcedetection,resource), exporters, pipelines, and Collector deployment manifests (e.g., DaemonSet and Deployment in Kubernetes, Docker Compose).
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.
- 8d ago First seen · 97 lines · 1,575 tokens per session scan A f57ae15fbdfb
agent-skills CLAUDE.md is an instructions file published in the GitHub repository dash0hq/agent-skills (87 stars, last pushed 6d ago), licensed Apache-2.0. It adds 1,575 tokens to every session, about $0.0079 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.