general Copilot instructionsA
general from henriquecotta/ownership-driven-ai-customization-architecture is a Copilot instructions file: the standing instructions GitHub Copilot reads in that repo.
mdr add henriquecotta/ownership-driven-ai-customization-architecture/.github/instructions/ownership/repository/general.instructions.md@git:20260428.d12018dPins git:20260428.d12018d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Copilot instructions
- Repository
- henriquecotta/ownership-driven-ai-customization-architecture
- Path
.github/instructions/ownership/repository/general.instructions.md- Versions recorded
- 1
- Latest version
- git:20260428.d12018d, committed Apr 28, 2026
- Size
- 1,974 bytes
- Repository stars
- 6
- 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
# Repository Root Ownership This repository is both the published ODA reference and a working example of ODA. Root-owned guidance belongs here only when it is an architecture-wide contract for the whole repository. The live customization should model the architecture it teaches. Keep each customization layer in its documented role instead of using one surface as a catch-all. Do not place owner instructions directly under `.github/instructions/ownership/`, and do not replace the literal `repository/` folder with the checkout or repository name. Prefer GitHub-native versioning through tags and releases over repo-local version files. ## Repository Hygiene Treat drift between public guidance and repository behavior as a real defect. When the current change moves content or changes a rule, update every dependent surface in the same change. Prefer one coherent source of truth over repeated near-copies. ## Writing Standard Avoid enumeration unless the set itself is the contract. Prefer wording that names the underlying relationship or consequence, so the guidance still covers future surfaces. Better: update every surface that teaches or validates the same rule. …
Read the whole file at its exact version.
How to install
mdr add henriquecotta/ownership-driven-ai-customization-architecture/.github/instructions/ownership/repository/general.instructions.md@sha256:2fceabfd3fb94aabThe line at the top of this page pins the label git:20260428.d12018d, 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_54f2goerww6eekgz)
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 henriquecotta/ownership-driven-ai-customization-architecture/.github/instructions/ownership/repository/general.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 general.instructions.md from somewhere else? Ask it: where did my general.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 1 version of this file, committed on Apr 28, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at general.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 (1974 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
henriquecotta/ownership-driven-ai-customization-architecture · 6 stars · license MIT · pushed 2026-04-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_54f2goerww6eekgz GET https://markdownregistry.com/api/v1/resolve?ref=henriquecotta/ownership-driven-ai-customization-architecture/.github/instructions/ownership/repository/general.instructions.md GET https://markdownregistry.com/api/v1/blob/2fceabfd3fb94aab7dd1449bff7e00b3d31e8dc1a97181f192bedba2649ec45a
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 henriquecotta/ownership-driven-ai-customization-architecture
Every file in henriquecotta/ownership-driven-ai-customization-architecture