copilot-instructions.mdA
copilot-instructions.md from getmaat/maat is a Copilot instructions file: the standing instructions GitHub Copilot reads in that repo.
mdr add getmaat/maat/.github/copilot-instructions.md@git:20260703.c5bfbf2Pins git:20260703.c5bfbf2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Copilot instructions
- Repository
- getmaat/maat
- Path
.github/copilot-instructions.md- Versions recorded
- 2
- Latest version
- git:20260703.c5bfbf2, committed Jul 3, 2026
- First version recorded
- Jul 2, 2026
- Size
- 733 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
<!-- maat:begin (generated — edit the source docs, not this block) --> # GitHub Copilot — project instructions > This project uses **Ma'at**. The single source of truth for agent instructions is [`AGENTS.md`](../AGENTS.md) at the repository root. Read it first. **Before changing code**, read the relevant documentation in [`docs/`](../docs/) — start from [`docs/llms.txt`](../docs/llms.txt), which indexes every doc. **After changing code**, update the matching doc(s) in the same change, as described in [`AGENTS.md`](../AGENTS.md) under "Documentation update protocol". Treat docs as part of the diff, not an afterthought. <!-- This file is generated by `maat sync`. Edit AGENTS.md, not this file. --> <!-- maat:end -->
Read the whole file at its exact version.
How to install
mdr add getmaat/maat/.github/copilot-instructions.md@sha256:0d3a5a7264395097The line at the top of this page pins the label git:20260703.c5bfbf2, 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_cs35eyvlakibjhok)
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 getmaat/maat/.github/copilot-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 copilot-instructions.md from somewhere else? Ask it: where did my copilot-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 2 versions of this file, between Jul 2, 2026 and Jul 3, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260703.c5bfbf2 latest | 2026-07-03 | c5bfbf2 | 733 B | A | view · diff |
| git:20260702.e7adb41 | 2026-07-02 | e7adb41 | 744 B | A | view |
Installed this file, say at copilot-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 (733 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
getmaat/maat · 4 stars · license Apache-2.0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cs35eyvlakibjhok GET https://markdownregistry.com/api/v1/resolve?ref=getmaat/maat/.github/copilot-instructions.md GET https://markdownregistry.com/api/v1/blob/0d3a5a7264395097320b6608782466a1195231aec7ab43e296a6f1d0622cb81d
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.