markdown-files Copilot instructionsA
markdown-files from rshade/finfocus is a Copilot instructions file: the standing instructions GitHub Copilot reads in that repo.
mdr add rshade/finfocus/.github/instructions/markdown-files.instructions.md@git:20251209.4f383dfPins git:20251209.4f383df in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Copilot instructions
- Repository
- rshade/finfocus
- Path
.github/instructions/markdown-files.instructions.md- Versions recorded
- 1
- Latest version
- git:20251209.4f383df, committed Dec 9, 2025
- Size
- 1,601 bytes
- Repository stars
- 11
- 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
# Markdown Documentation Instructions Documentation files follow specific standards and formatting requirements. ## Documentation Standards: - Use clear, concise language - Follow Google markdown style guide - Include proper frontmatter (title, description, layout) - Use consistent heading hierarchy - Include table of contents for long documents ## Content Organization: - Start with overview/summary - Use logical section organization - Include examples and code snippets - Provide troubleshooting information - Link to related documentation ## Code Examples: - Use proper syntax highlighting - Test all code examples - Include language identifiers - Use consistent formatting - Provide context for examples ## Link Management: - Use relative links within the repository - Check for broken links regularly - Use descriptive link text - Maintain link accuracy ## Frontmatter Requirements: - Include title, description, and layout fields - Use proper YAML formatting - Follow Jekyll conventions for docs/ - Include metadata for SEO and navigation ## Linting and Validation: - Pass markdownlint checks - Follow repository-specific rules - Use consistent formatting …
Read the whole file at its exact version.
How to install
mdr add rshade/finfocus/.github/instructions/markdown-files.instructions.md@sha256:eabcf1f2ef0363adThe line at the top of this page pins the label git:20251209.4f383df, 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_eek4n5banx3k7h6z)
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 rshade/finfocus/.github/instructions/markdown-files.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 markdown-files.instructions.md from somewhere else? Ask it: where did my markdown-files.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 Dec 9, 2025.
Watch this file (sign in, one email per new version)
Installed this file, say at markdown-files.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 (1601 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
rshade/finfocus · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eek4n5banx3k7h6z GET https://markdownregistry.com/api/v1/resolve?ref=rshade/finfocus/.github/instructions/markdown-files.instructions.md GET https://markdownregistry.com/api/v1/blob/eabcf1f2ef0363ad7a17fed08066e53df89723fb11d385a6b8c702d576722b48
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.