CLAUDE.md@templatesA
CLAUDE.md@templates from chrono-meta/forge-harness is a CLAUDE.md file: the standing instructions Claude Code reads in that repo.
mdr add chrono-meta/forge-harness/templates/CLAUDE.md@git:20261024.85539eePins git:20261024.85539ee in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- CLAUDE.md file
- Repository
- chrono-meta/forge-harness
- Path
templates/CLAUDE.md- Versions recorded
- 6
- Latest version
- git:20261024.85539ee, committed Oct 24, 2026
- First version recorded
- Jun 7, 2026
- Size
- 9,642 bytes
- Repository stars
- 30
- License
- MIT
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# CLAUDE.md
> **Role-matched self-inspection (incubator bequest, 2026-08-10)**: this harness should carry at
> least ONE self-check instrument matched to *its own role* — something that answers "is what this
> harness verifies still aligned with what it is for?" — run at sync/upgrade moments, not only at
> incidents. The parent hub's instance is an env-purity scan (does shared prose still apply here?);
> a QA harness's is spec↔implementation↔TC triad consistency; yours follows YOUR role. An
> instrument the harness never runs on itself is decoration — wire it to a recurring moment.
## Session Start
When a user starts a session with greetings like "hello", "let's start", "resume", "continuing from where we left off", or says "read root memory", **both layers must activate**:
### Layer A — Auto read (4 steps required)
1. **Read CATALOG.md** — `~/projects/forge-harness/CATALOG.md` (recent work context + latest meta cwd work cross-link)
2. **Read latest session file** — `~/projects/forge-harness/tracks/{project}/` most recent mtime item (last work on domain + next round reverse-injection intent persistence location / use `ls -lat` or `find -mtime`)
…Read the whole file at its exact version.
How to install
mdr add chrono-meta/forge-harness/templates/CLAUDE.md@sha256:062709f09ef75517The line at the top of this page pins the label git:20261024.85539ee, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ul7n2627oitlecus)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 7, 2026 and Oct 24, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.85539ee latest | 2026-10-24 | 85539ee | 9,642 B | A | view · diff |
| git:20260810.69d1ce6 | 2026-08-10 | 69d1ce6 | 7,965 B | A | view · diff |
| git:20260610.4868e97 | 2026-06-10 | 4868e97 | 7,377 B | A | view · diff |
| git:20260610.17da4e9 | 2026-06-10 | 17da4e9 | 6,780 B | A | view · diff |
| git:20260610.5764b66 | 2026-06-10 | 5764b66 | 5,299 B | A | view · diff |
| git:20260607.495a7a3 | 2026-06-07 | 495a7a3 | 5,252 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (9642 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chrono-meta/forge-harness · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ul7n2627oitlecus GET https://markdownregistry.com/api/v1/resolve?ref=chrono-meta/forge-harness/templates/CLAUDE.md GET https://markdownregistry.com/api/v1/blob/062709f09ef755170218ea4ee79675fcdd0fda6714161f7f162e52c88277833f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: what a CLAUDE.md file is · keeping AGENTS.md and CLAUDE.md in sync · which agent file does what.
More from chrono-meta/forge-harness
Every file in chrono-meta/forge-harness