mnema-instructions Copilot instructionsA
mnema-instructions from felipesauer/mnema is a Copilot instructions file: the standing instructions GitHub Copilot reads in that repo.
mdr add felipesauer/mnema/.github/instructions/mnema-instructions.instructions.md@git:20261118.a18dcb8Pins git:20261118.a18dcb8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Copilot instructions
- Repository
- felipesauer/mnema
- Path
.github/instructions/mnema-instructions.instructions.md- Versions recorded
- 3
- Latest version
- git:20261118.a18dcb8, committed Nov 18, 2026
- First version recorded
- Oct 29, 2026
- Size
- 2,946 bytes
- Repository stars
- 5
- License
- Apache-2.0
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
<!-- mnema:begin v5 (written by mnema; `mnema instructions --remove` takes it out) --> ## Recording the work (mnema) This repository keeps a signed record of its decisions in `.mnema/`. Where the mnema tools are connected: - At the start of a session, call `bootstrap`: it opens with what is in force, what awaits a judgement and the work in flight. - Before changing a file, call `governing_rules` with its path. - When a choice is settled, with the person or alone, that someone could later question (a library, an approach, a trade-off, an option turned down), call `record_decision` in that turn, with the `rationale` and, in `alternatives`, what was turned down and why. Record it even when it is also written in a plan, a ledger, this file or your own memory. - A decision is born `proposed`; once it is accepted it is in force here. If the person dictated it, or chose it among options you offered (a recommended one included), accept it now with `decision_transition` and a note quoting their answer; one you concluded alone waits for the person. An agent’s acceptance is recorded as an agent’s, and `mnema switch off agent-accepts` leaves every acceptance to a person. …
Read the whole file at its exact version.
How to install
mdr add felipesauer/mnema/.github/instructions/mnema-instructions.instructions.md@sha256:5a7a90c69da61c91The line at the top of this page pins the label git:20261118.a18dcb8, 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_ei3d5nmh3ms3jl3g)
1 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 felipesauer/mnema/.github/instructions/mnema-instructions.instructions.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 mnema-instructions.instructions.md from somewhere else? Ask it: where did my mnema-instructions.instructions.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 3 versions of this file, between Oct 29, 2026 and Nov 18, 2026, about one every 10 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261118.a18dcb8 latest | 2026-11-18 | a18dcb8 | 2,946 B | A | view · diff |
| git:20261103.120f6fc | 2026-11-03 | 120f6fc | 2,744 B | A | view · diff |
| git:20261029.28f8727 | 2026-10-29 | 28f8727 | 2,523 B | A | view |
Installed this file, say at mnema-instructions.instructions.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 (2946 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
felipesauer/mnema · 5 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ei3d5nmh3ms3jl3g GET https://markdownregistry.com/api/v1/resolve?ref=felipesauer/mnema/.github/instructions/mnema-instructions.instructions.md GET https://markdownregistry.com/api/v1/blob/5a7a90c69da61c91d24719a50d72ca562816eac328927b0c2da061d76089fda4
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: which agent file does what.
More from felipesauer/mnema
Every file in felipesauer/mnema