Borrowing it
Nothing to install: this file belongs to dikamilo/dx-workflow. 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/dikamilo/dx-workflow/main/CLAUDE.mdgit clone --depth 1 https://github.com/dikamilo/dx-workflowWrote 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/dikamilo/dx-workflow/claude-md)<a href="https://agentmods.dev/instructions/dikamilo/dx-workflow/claude-md"><img src="https://agentmods.dev/badge/instructions/dikamilo/dx-workflow/claude-md/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/instructions/dikamilo/dx-workflow/claude-md"><img src="https://agentmods.dev/badge/instructions/dikamilo/dx-workflow/claude-md.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.01007 | $0.01007 |
| Opus 5.5 | $0.00403 | $0.00403 |
| Sonnet 5.5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
dx-workflow 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 22d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx — maintainer orientation
This repo authors the dx- skill set. DESIGN.md is the source of truth for behavior; this file orients anyone working on the skills. (It is not installed with the skills — each skill ships standalone via skills.sh. Target projects get only a one-line dx- pointer from dx-init; the never-auto-rollback principle lives in the skills themselves.)
Layout
skills/
├── dx-references/ # loader (user-invocable:false) + references/*.md (shared docs)
└── dx-<skill>/SKILL.md # one directory per skill
DESIGN.md # the design spec — authority
package.json # install-skills / list-skills scripts (npx skills)
Authoring rules (the house style)
- Frontmatter.
name: dx-<x>. User-invoked skills setdisable-model-invocation: trueand get a terse human-facing description (no trigger lists → zero context load). The two model-invoked skills —dx-diagnose,dx-domain— omit that flag and keep rich trigger phrasing. The utility skills other skills call by name —dx-new,dx-archive,dx-lesson,dx-standards-update— also omit it but keep terse human-facing descriptions (no trigger lists).dx-referencesusesuser-invocable: false(hidden from the/menu, still model-reachable). - Body. Short and principle-first. Leading words that recruit pretrained concepts (tight, red-capable, tracer bullet, deep module). Apply the no-op test: delete any sentence the model already obeys. Multi-step skills carry a
Done whencompletion criterion. - Shared references are pulled by invoking
dx-referenceswith a topic — never deep-link another skill's files. Add a reference todx-references/references/only when ≥2 skills use it; otherwise collocate it inside its one skill. - Anti-ceremony. Markdown only — no HTML, no sidecar
*.ymlstate. No auto-chain: print the next command and stop. Derive, don't maintain — lists fromls, status from frontmatter, effort progress from child changes.
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.
- 22d ago Changed · +2 lines · +13 tokens per session 84e7a8766110
- 1mo ago Changed · +45 tokens per session 494074c3e572
- 2mo ago First seen · 45 lines · 949 tokens per session scan A 0d58a7cdfc83
dx-workflow CLAUDE.md is an instructions file published in the GitHub repository dikamilo/dx-workflow (8 stars, last pushed 22d ago), licensed MIT. It adds 1,007 tokens to every session, about $0.0040 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-08-31.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.