oda-board Copilot instructionsA
oda-board 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/oda-board.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/oda-board.instructions.md- Versions recorded
- 1
- Latest version
- git:20260428.d12018d, committed Apr 28, 2026
- Size
- 775 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
# ODA Board Interpretation Use this instruction only when board state or tracked ODA work could affect the task. This is repo-owned interpretation policy for the board, not an exact operational workflow. The ODA Board owns planning state and explicit carry-forward. It does not prove current implementation behavior unless linked to merged code, tests, or accepted docs. If board state conflicts with repository evidence, classify the disputed claim first. Code and tests own current implementation behavior. Accepted docs own documented architecture. The board owns planned or deferred work. If board access is unavailable, follow the `oda-board` supporting-source fallback. Use skill `oda-task-tracking` for operational issue or board changes.
Read the whole file at its exact version.
How to install
mdr add henriquecotta/ownership-driven-ai-customization-architecture/.github/instructions/ownership/repository/oda-board.instructions.md@sha256:d38885266ecf46e0The 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_jcae7l5nf2rd7yw7)
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 henriquecotta/ownership-driven-ai-customization-architecture/.github/instructions/ownership/repository/oda-board.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 oda-board.instructions.md from somewhere else? Ask it: where did my oda-board.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 oda-board.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 (775 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_jcae7l5nf2rd7yw7 GET https://markdownregistry.com/api/v1/resolve?ref=henriquecotta/ownership-driven-ai-customization-architecture/.github/instructions/ownership/repository/oda-board.instructions.md GET https://markdownregistry.com/api/v1/blob/d38885266ecf46e055c7a4806ccc0867487bc255b83dd6922c3dd5591e123722
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