devharness: Instructions file for Claude Code

CLAUDE.md

devharness CLAUDE.md is an instructions file for Claude Code from InDate/devharness. It costs 233 tokens per session, scanned A, original, MIT.

Repository instructions for working on devharness, including its build, test, hot-reload, and release guidance. They warn that rebuilding restarts the running child process and discards its in-memory browser and proxy state.

In plain words
What is it for?
Use them when developing devharness, especially when changing the proxy or browser controls and then running a build-and-drive test.
Why use it?
They prevent misleading test results caused by using evidence collected before a rebuild. They also explain why live connections and captured events disappear after rebuilding.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is InDate/devharness's own configuration. It tells Claude Code how to work on devharness 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 devharness configures →

Reuse

Borrowing it

Nothing to install: this file belongs to InDate/devharness. 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/InDate/devharness/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/InDate/devharness

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 devharness CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/indate/devharness/claude-md"><img src="https://agentmods.dev/badge/instructions/indate/devharness/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 233 This file is loaded in full into every session.
When invoked 233 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.00233 $0.00233
Opus 5.5 $0.00093 $0.00093
Sonnet 5.5 $0.00047 $0.00047
Haiku 4.5 $0.00023 $0.00023

Measured 28d ago against content hash 2803719f8493, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

devharness 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 28d 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.

CLAUDE.md · 21 lines

What it actually says

devharness

Working on this repo, as opposed to using its tools against another app. CONTRIBUTING.md holds the build, test, hot-reload and release mechanics, and the devharness-contributing skill holds the code conventions.

A rebuild discards what the running child held in memory

npm run build signals SIGUSR2 from its postbuild hook, and the supervisor restarts build/index.js. Everything that child held goes with it, not only the Chrome instances listed under Hot reload in CONTRIBUTING.md:

  • The proxy registry (src/proxy/registry.ts). A proxy started by connection({ action: 'launch', proxy: true }) is gone, and every event it captured with it.
  • Live connections, so a connection resolves to nothing until a fresh connection launch.

A drive that checks a change has to run after the rebuild that carries the change. Build first, drive second. Rebuilding part-way through a drive discards the evidence collected so far and returns Connection not found.

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. 28d ago Changed · -1 tokens per session 2803719f8493
  2. 1mo ago Changed · +4 tokens per session a4a9fac322fe
  3. 1mo ago First seen · 21 lines · 230 tokens per session scan A 9f6fd7a4b17e

Subscribe to this mod's changes

devharness CLAUDE.md is an instructions file published in the GitHub repository InDate/devharness (19 stars, last pushed today), licensed MIT. It adds 233 tokens to every session, about $0.0009 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-25.

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,715 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,461 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

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,750 tokens

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.

denoland/deno · 3,077 tokens