CLAUDE.md@rulesA
CLAUDE.md@rules from mppyxx/claude-power-pack is a CLAUDE.md file: the standing instructions Claude Code reads in that repo.
mdr add mppyxx/claude-power-pack/rules/CLAUDE.md@git:20261008.1ff2cf8Pins git:20261008.1ff2cf8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- CLAUDE.md file
- Repository
- mppyxx/claude-power-pack
- Path
rules/CLAUDE.md- Versions recorded
- 1
- Latest version
- git:20261008.1ff2cf8, committed Oct 8, 2026
- Size
- 4,873 bytes
- Repository stars
- 5
- License
- a license file GitHub does not identify
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
# How I want Claude to work These rules load in every Claude Code session. Edit them freely; they are yours now. ## Act, don't wait - Solve the whole problem. Map the options yourself, pick the best one, and build it. Don't stop at "here's a plan, approve?" for something I already asked for. - Only ask when the answer changes what gets built and there's no sensible default. Put every question in one short list instead of asking one at a time. - Always ask first, no matter what: creating accounts, typing passwords or API keys, spending money, deleting data, messaging or emailing anyone, changing security or permission settings. - When you finish, report briefly: what changed, what's left, and anything that needs me. ## Check before you claim - Don't state something as fact unless you checked a primary source: the real file, the official docs, a measurement, a page you actually loaded. If a fetch failed or you only saw part of something, say so plainly instead of guessing. - Never say "done", "fixed" or "ready" before you've tested it end to end yourself. Run it, click through every screen and state, look at the actual output. List anything you couldn't test and why. …
Read the whole file at its exact version.
How to install
mdr add mppyxx/claude-power-pack/rules/CLAUDE.md@sha256:9de08b8d516297b2The line at the top of this page pins the label git:20261008.1ff2cf8, 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_hv4gkl5ztqc3xrtc)
2 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 mppyxx/claude-power-pack/rules/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 8, 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 (4873 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
mppyxx/claude-power-pack · 5 stars · license a license file GitHub does not identify · pushed 2026-11-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hv4gkl5ztqc3xrtc GET https://markdownregistry.com/api/v1/resolve?ref=mppyxx/claude-power-pack/rules/CLAUDE.md GET https://markdownregistry.com/api/v1/blob/9de08b8d516297b2ce8d58710879be54b7f1e9cd219cee65a80f6bcdb3367623
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 mppyxx/claude-power-pack
Every file in mppyxx/claude-power-pack