mnema-instructions Cursor ruleA
mnema-instructions from felipesauer/mnema is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add felipesauer/mnema/.cursor/rules/mnema-instructions.mdc@git:20261029.28f8727Pins git:20261029.28f8727 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- felipesauer/mnema
- Path
.cursor/rules/mnema-instructions.mdc- Versions recorded
- 1
- Latest version
- git:20261029.28f8727, committed Oct 29, 2026
- Size
- 2,527 bytes
- Repository stars
- 4
- 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 v3 (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 (an acceptance made by an agent is recorded as an agent’s, and `mnema switch off agent-accepts` leaves it to a person). …
Read the whole file at its exact version.
How to install
mdr add felipesauer/mnema/.cursor/rules/mnema-instructions.mdc@sha256:53ae32010476a8ddThe line at the top of this page pins the label git:20261029.28f8727, 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_66nfvmbiqqqxwvzz)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 29, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2527 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 · 4 stars · license Apache-2.0 · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_66nfvmbiqqqxwvzz GET https://markdownregistry.com/api/v1/resolve?ref=felipesauer/mnema/.cursor/rules/mnema-instructions.mdc GET https://markdownregistry.com/api/v1/blob/53ae32010476a8ddc7072f086a974b2d834319f2fc79d2ef928acb291ed55d60
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: Cursor rules vs AGENTS.md · which agent file does what.