dev-workflow-kit: Instructions file for Claude Code

CLAUDE.md

dev-workflow-kit CLAUDE.md is an instructions file for Claude Code from dsnger/dev-workflow-kit. It costs 2,446 tokens per session, scanned A, original, MIT.

A project instruction file for dev-workflow-kit that sets rules for planning changes, keeping implementations simple, and limiting edits to what the task requires.

In plain words
What is it for?
Use it when planning or implementing repository changes, deciding between multiple approaches, and reviewing whether a solution is smaller and more focused than necessary.
Why use it?
It helps coding agents expose assumptions and uncertainties before changing code, reducing unnecessary features, refactors, and unrelated edits.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

This is dsnger/dev-workflow-kit's own configuration. It tells Claude Code how to work on dev-workflow-kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dev-workflow-kit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dsnger/dev-workflow-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dsnger/dev-workflow-kit/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/dsnger/dev-workflow-kit

Made for: Claude Code.

Wrote 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.

agentmods badge for dev-workflow-kit CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dsnger/dev-workflow-kit/claude-md/github.svg)](https://agentmods.dev/instructions/dsnger/dev-workflow-kit/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/dsnger/dev-workflow-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/dsnger/dev-workflow-kit/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.

agentmods 80×15 button for dev-workflow-kit CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/dsnger/dev-workflow-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/dsnger/dev-workflow-kit/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,446 This file is loaded in full into every session.
When invoked 2,446 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02446 $0.02446
Opus 5.5 $0.00978 $0.00978
Sonnet 5.5 $0.00489 $0.00489
Haiku 4.5 $0.00245 $0.00245

Measured today against content hash b7c1f8bb9993, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dev-workflow-kit 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 today.

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.

CLAUDE.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

dev-workflow-kit

Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

Before implementing:

  • State your assumptions explicitly. If uncertain, ask.
  • If multiple interpretations exist, present them - don't pick silently.
  • If a simpler approach exists, say so. Push back when warranted.
  • If something is unclear, stop. Name what's confusing. Ask.

Don't guess

Applies to factual claims in every answer, not only implementation. Confidence is not evidence.

Leave gaps visible. Do not invent missing or ambiguous facts. State what is unknown and why. In extraction tasks, leave unsupported fields blank where the format permits; otherwise use the format's defined missing-value handling.

Separate evidence from inference. Cite the relevant source for factual conclusions. Identify deductions and assumptions as such, with their basis. For extraction tasks, label populated fields EXTRACTED or INFERRED and explain each inference where the required output format permits. If neither annotations nor accompanying explanations are permitted, preserve the required format. This does not permit inventing unsupported values.

Keep decisions distinct from facts. Make reasonable design and implementation choices within the authorized scope, describing them as choices rather than source facts. Ask when missing information changes correctness or scope.

Verify before claiming. Report a test or action as completed only when its result was observed. Preserve required output formats; put explanations outside structured artifacts where permitted.

2. Simplicity First

Minimum code that solves the problem. Nothing speculative.

  • No features beyond what was asked.
  • No abstractions for single-use code.
  • No "flexibility" or "configurability" that wasn't requested.
  • No error handling for impossible scenarios.
  • If you write 200 lines and it could be 50, rewrite it.

Read the full file on GitHub · 145 lines

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.

  1. today Changed · +44 tokens per session b7c1f8bb9993
  2. 4d ago Changed · -2 lines · -80 tokens per session d57a481baafd
  3. 5d ago Changed · +18 tokens per session 4c395c46bdef
  4. 9d ago Changed · +9 lines · +399 tokens per session 05f087a62cb2
  5. 10d ago Changed · +18 lines · +830 tokens per session 2f76af0a1132
  6. 11d ago Changed · -1,501 lines · -27,552 tokens per session ef21eb5fb48d
  7. 14d ago Changed · +8 tokens per session 92e69280d3b9
  8. 17d ago Changed · +13 lines · +319 tokens per session e1d545208314
  9. 18d ago Changed · -7 tokens per session 430487982ec6
  10. 20d ago First seen · 1,608 lines · 28,467 tokens per session scan A 912d439cb725

Subscribe to this mod's changes

dev-workflow-kit CLAUDE.md is an instructions file published in the GitHub repository dsnger/dev-workflow-kit (6 stars, last pushed today), licensed MIT. It adds 2,446 tokens to every session, about $0.0098 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.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,257 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens

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).

microsoft/vscode · 2,731 tokens