AGENTS.mdA
AGENTS.md from le0-lin/agentconfigscore is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add le0-lin/agentconfigscore/AGENTS.md@git:20261116.1cec1aaPins git:20261116.1cec1aa in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- le0-lin/agentconfigscore
- Path
AGENTS.md- Versions recorded
- 2
- Latest version
- git:20261116.1cec1aa, committed Nov 16, 2026
- First version recorded
- Aug 20, 2026
- Size
- 1,038 bytes
- Repository stars
- 66
- 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
# Agent instructions — AgentConfigScore Keep the runtime dependency-free on Python 3.10+. ## Verification - Run `PYTHONPATH=src python -m unittest discover -s tests -v` after scanner or CLI changes. - Run `PYTHONPATH=src python -m agent_config_score.cli examples/demo` when changing scoring or output formatting. ## Scope - Put scanning and scoring logic in `src/agent_config_score/scanner.py`. - Keep CLI argument parsing and terminal output in `src/agent_config_score/cli.py`. - Add a regression test for every false positive or false negative that is fixed. ## Safety - Never print the full value of a detected credential. - Keep contradiction detection conservative; do not claim semantic conflicts without strong evidence. ## Deletion and overwrite safeguards - Before deleting existing files, overwriting user changes, or discarding uncommitted work, explain the exact targets and impact and obtain explicit user approval. - This instruction does not authorize destructive commands; follow any stricter repository rules.
Read the whole file at its exact version.
How to install
mdr add le0-lin/agentconfigscore/AGENTS.md@sha256:1a6ffa80d9f0ce16The line at the top of this page pins the label git:20261116.1cec1aa, 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_rly6fyfpol7tvhvq)
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 le0-lin/agentconfigscore/AGENTS.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 AGENTS.md from somewhere else? Ask it: where did my AGENTS.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 Aug 20, 2026 and Nov 16, 2026, about one every 88 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.1cec1aa latest | 2026-11-16 | 1cec1aa | 1,038 B | A | view · diff |
| git:20260820.d917723 | 2026-08-20 | d917723 | 737 B | A | view |
Installed this file, say at AGENTS.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 (1038 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
le0-lin/agentconfigscore · 66 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rly6fyfpol7tvhvq GET https://markdownregistry.com/api/v1/resolve?ref=le0-lin/agentconfigscore/AGENTS.md GET https://markdownregistry.com/api/v1/blob/1a6ffa80d9f0ce16d6cf8d02771c118037afe360c7dc5f43a6b9c987c3b5cbbb
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: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.
More from le0-lin/agentconfigscore
Every file in le0-lin/agentconfigscore