go-files Copilot instructionsA
go-files from rshade/finfocus is a Copilot instructions file: the standing instructions GitHub Copilot reads in that repo.
mdr add rshade/finfocus/.github/instructions/go-files.instructions.md@git:20261005.91a226dPins git:20261005.91a226d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Copilot instructions
- Repository
- rshade/finfocus
- Path
.github/instructions/go-files.instructions.md- Versions recorded
- 4
- Latest version
- git:20261005.91a226d, committed Oct 5, 2026
- First version recorded
- Dec 9, 2025
- Size
- 2,109 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
# Go Code Instructions This repository uses the Go version in the `go` directive of `go.mod`, with specific coding standards and best practices. ## Go Version Requirements: - **Version**: the `go` directive in `go.mod` is both the minimum and the target - **Compatibility**: Use only language and standard library features available in that version ## Code Quality Standards: - Use modern Go idioms and patterns - Follow standard Go formatting (gofmt) - Include proper error handling with error wrapping - Use generics where appropriate for type safety - Ensure proper documentation for exported functions and types - Follow Go naming conventions (camelCase for private, PascalCase for exported) - Use structured logging through internal/logging package - Keep public structs JSON-tagged for CLI/JSON outputs ## Security Best Practices: - Validate all inputs and handle edge cases - Use proper error wrapping and context propagation - Avoid common security vulnerabilities - Follow Go security guidelines ## Performance Considerations: - Use appropriate data structures for the use case - Consider memory usage and garbage collection impact - Use goroutines and channels appropriately …
Read the whole file at its exact version.
How to install
mdr add rshade/finfocus/.github/instructions/go-files.instructions.md@sha256:b2a279c335b811daThe line at the top of this page pins the label git:20261005.91a226d, 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_ghl3rn6e4di7qb6l)
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/go-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 go-files.instructions.md from somewhere else? Ask it: where did my go-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 4 versions of this file, between Dec 9, 2025 and Oct 5, 2026, about one every 100 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.91a226d latest | 2026-10-05 | 91a226d | 2,109 B | A | view · diff |
| git:20260909.79f9c71 | 2026-09-09 | 79f9c71 | 2,022 B | A | view · diff |
| git:20260130.5aaefc4 | 2026-01-30 | 5aaefc4 | 2,022 B | A | view · diff |
| git:20251209.4f383df | 2025-12-09 | 4f383df | 2,022 B | A | view |
Installed this file, say at go-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 (2109 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_ghl3rn6e4di7qb6l GET https://markdownregistry.com/api/v1/resolve?ref=rshade/finfocus/.github/instructions/go-files.instructions.md GET https://markdownregistry.com/api/v1/blob/b2a279c335b811dab37aef43f62f3382df594ca0fea80efee9cd82af4985a052
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.