CLAUDE.md@evals/consumer/fixtureA
CLAUDE.md@evals/consumer/fixture from pisberg/vibetags is a CLAUDE.md file: the standing instructions Claude Code reads in that repo.
mdr add pisberg/vibetags/evals/consumer/fixture/CLAUDE.md@git:20261019.e691f74Pins git:20261019.e691f74 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- CLAUDE.md file
- Repository
- pisberg/vibetags
- Path
evals/consumer/fixture/CLAUDE.md- Versions recorded
- 1
- Latest version
- git:20261019.e691f74, committed Oct 19, 2026
- Size
- 2,316 bytes
- Repository stars
- 25
- 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
# Acme Shop
Order and payment service behind the Acme web shop and its mobile apps.
- Java 21. Sources live under `src/main/java/com/acme/shop`.
- Packages: `api` (checkout endpoints for web and mobile), `order` (pricing), `customer`
(registration), `payment` (card acquirer client).
- Keep changes small and focused; match the style of the surrounding code.
<!-- VIBETAGS-START -->
<!-- # Generated by VibeTags | https://github.com/PIsberg/vibetags -->
<project_guardrails>
<locked_files>
<file path="com.acme.shop.payment.PaymentGateway">
<reason>The acquirer's nightly settlement file is matched against these exact method signatures and integer minor units (contract ACQ-2291); any change here breaks reconciliation, so route changes through the payments team.</reason>
</file>
</locked_files>
<contextual_instructions>
</contextual_instructions>
<pii_guardrails>
<element path="com.acme.shop.customer.Customer.email">
<reason>Personal data under GDPR Art. 4: must never reach logs, metrics, traces or error messages. Identify a customer by id instead.</reason>
</element>
<element path="com.acme.shop.customer.Customer.taxId">
…Read the whole file at its exact version.
How to install
mdr add pisberg/vibetags/evals/consumer/fixture/CLAUDE.md@sha256:7d19ffa2b8a54b07The line at the top of this page pins the label git:20261019.e691f74, 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_oaaivqoyb22a32sq)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in pisberg/vibetags/evals/consumer/fixture/CLAUDE.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of CLAUDE.md from somewhere else? Ask it: where did my CLAUDE.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 19, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at CLAUDE.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2316 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
pisberg/vibetags · 25 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oaaivqoyb22a32sq GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/evals/consumer/fixture/CLAUDE.md GET https://markdownregistry.com/api/v1/blob/7d19ffa2b8a54b074b671857373b4bb2eab7d954e5b194f659f7221620973cc7
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.