client Copilot instructionsA
client from zhulinsen/daily_stock_analysis is a Copilot instructions file: the standing instructions GitHub Copilot reads in that repo.
mdr add zhulinsen/daily_stock_analysis/.github/instructions/client.instructions.md@git:20261119.92f0209Pins git:20261119.92f0209 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Copilot instructions
- Repository
- zhulinsen/daily_stock_analysis
- Path
.github/instructions/client.instructions.md- Versions recorded
- 2
- Latest version
- git:20261119.92f0209, committed Nov 19, 2026
- First version recorded
- Mar 17, 2026
- Size
- 1,004 bytes
- Repository stars
- 73,646
- 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
# Client Instructions - Preserve the existing Vite + React web structure and Electron desktop runtime assumptions; reuse current API/state patterns instead of adding parallel client abstractions. - If a change affects API fields, auth state, route behavior, Markdown/chart rendering, local backend startup, or report payloads, assess both Web and Desktop compatibility. - Validate Web changes with `cd apps/dsa-web && npm ci && npm run lint && npm run build` when feasible. - For visible changes, link the affected state in screenshots or the current web-gate fixture artifact and say what was inspected. Distinguish Web UI shared by Electron from changes to the desktop shell. - Validate Desktop changes by building Web first, then `apps/dsa-desktop`; if platform limits prevent full Electron validation, call out the exact risk in the final delivery.
Read the whole file at its exact version.
How to install
mdr add zhulinsen/daily_stock_analysis/.github/instructions/client.instructions.md@sha256:e9dd84fb1b2be22eThe line at the top of this page pins the label git:20261119.92f0209, 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_p5mrawxdvrwq6g4k)
3 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 zhulinsen/daily_stock_analysis/.github/instructions/client.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 client.instructions.md from somewhere else? Ask it: where did my client.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 Mar 17, 2026 and Nov 19, 2026, about one every 247 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261119.92f0209 latest | 2026-11-19 | 92f0209 | 1,004 B | A | view · diff |
| git:20260317.b06c098 | 2026-03-17 | b06c098 | 800 B | A | view |
Installed this file, say at client.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 (1004 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
zhulinsen/daily_stock_analysis · 73,646 stars · license MIT · pushed 2026-11-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p5mrawxdvrwq6g4k GET https://markdownregistry.com/api/v1/resolve?ref=zhulinsen/daily_stock_analysis/.github/instructions/client.instructions.md GET https://markdownregistry.com/api/v1/blob/e9dd84fb1b2be22e9bc54d4fa2e3fcbe0c10c032efc8c93a625c556fcd2a1f89
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.