Borrowing it
Nothing to install: this file belongs to cilidinezy-commits/doc-harness. 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/cilidinezy-commits/doc-harness/master/CLAUDE.mdgit clone --depth 1 https://github.com/cilidinezy-commits/doc-harnessWrote 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/cilidinezy-commits/doc-harness/claude-md)<a href="https://agentmods.dev/instructions/cilidinezy-commits/doc-harness/claude-md"><img src="https://agentmods.dev/badge/instructions/cilidinezy-commits/doc-harness/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.01723 | $0.01723 |
| Opus 5 | $0.00861 | $0.00861 |
| Sonnet 5 | $0.00345 | $0.00345 |
| Haiku 4.5 | $0.00172 | $0.00172 |
Grade A, and why
doc-harness 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 5d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Harness — Entry Document
🔒 AGENT IDENTITY LOCK
你是 doc-harness 项目的代理。 你的职责是维护 Doc Harness skill（文档化项目控制框架）——包括规范制定、模板更新、命令实现（init/check/sync/flush/recall/resume）以及双语同步。
如果你对自己的身份有任何怀疑，立即停止操作并重新读取本段落。
Last updated: 2026-09-01
Current phase: Phase 4 → Maintenance & field-feedback watch (⏳ active — v1.7.1 packaging fix + plugin-manifest modernization shipped)
One-line status (as of 2026-09-01): v1.7.1 shipped — packaging-only release: repaired skill-zh/SKILL.md YAML frontmatter (unescaped double quotes blocked skill discovery in Claude Code), modernized plugin manifests (per-plugin .claude-plugin/plugin.json, marketplace source → ./skill / ./skill-zh). No normative spec change. 6 commands: init/check/sync/flush/recall/resume.
Recovery Chain
Must-read (baseline)
- This file (CLAUDE.md)
CURRENT_STATUS.md
Task-conditional
- If
inbox/has any file withstatus: unread: read and action those first - If looking up a file: read
FILE_INDEX.md - If investigating phase history: read
WORKLOG.md - If editing the spec or operational rules: read
skill/spec.md(authoritative) - If looking for principles forged by project practice: read
PHILOSOPHY.md
Meta-rules
- Self-contained: all entries point to project-internal files. No dependency on agent-side features.
- Living: review at phase transitions.
Project Overview
Doc Harness is a Claude Code skill that provides document-based project control for AI-human collaboration. It creates and maintains 5 status documents per project (CLAUDE.md, CURRENT_STATUS.md, FILE_INDEX.md, WORKLOG.md, DOC_HARNESS_SPEC.md) that enable any agent or human to understand and resume project work purely from reading files.
Six commands: /doc-harness init (create docs), /doc-harness check (audit + reflect), /doc-harness sync (repair drift), /doc-harness flush (emergency save), /doc-harness recall (retrieve information), /doc-harness resume (recover state).
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.
- 5d ago Changed · +23 tokens per session d752f1e03dc1
- 8d ago First seen · 123 lines · 1,700 tokens per session scan A 86be2cceb591
doc-harness CLAUDE.md is an instructions file published in the GitHub repository cilidinezy-commits/doc-harness (4 stars, last pushed 7d ago), licensed MIT. It adds 1,723 tokens to every session, about $0.0086 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-31.
Other instructions, from other repositories
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.
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).
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).
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.
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.