AGENTS.md@examples/with-nextjs-elysia/apps/webA
AGENTS.md in bronz3beard/ai.tech-lead-stack is at git:20261010.a05d44a (Oct 10, 2026), graded A.
mdr add bronz3beard/ai.tech-lead-stack/AGENTS.md@git:20261010.a05d44aThis copy is 4 versions behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
AGENTS.md@examples/with-nextjs-elysia/apps/web from vercel/turborepo is an AGENTS.md file: the standing instructions coding agents read in that repo.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- vercel/turborepo
- Path
examples/with-nextjs-elysia/apps/web/AGENTS.md- Versions recorded
- 1
- Latest version
- git:20260330.1559d0f, committed Mar 30, 2026
- Size
- 327 bytes
- Repository stars
- 31,365
- 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
<!-- BEGIN:nextjs-agent-rules --> # This is NOT the Next.js you know This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` before writing any code. Heed deprecation notices. <!-- END:nextjs-agent-rules -->
Read the whole file at its exact version.
How to install
mdr add vercel/turborepo/examples/with-nextjs-elysia/apps/web/AGENTS.md@git:20260330.1559d0fPins git:20260330.1559d0f in mdr.lock, 4 versions behind the newest at the top of this page.
mdr add vercel/turborepo/examples/with-nextjs-elysia/apps/web/AGENTS.md@sha256:e3447d84251880fbThe older copy line above pins the label git:20260330.1559d0f, 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_zgvblxbya674ur3y)
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: get me the newest bronz3beard/ai.tech-lead-stack/AGENTS.md, and what changed since e3447d8? 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 1 version of this file, committed on Mar 30, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20261010.a05d44a of AGENTS.md in bronz3beard/ai.tech-lead-stack (AGENTS.md), graded A.
This copy: byte for byte that file's version git:20260319.d56f2f1, which it committed on Mar 19, 2026, before this repository did; graded A, 4 versions behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
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 (327 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
vercel/turborepo · 31,365 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zgvblxbya674ur3y GET https://markdownregistry.com/api/v1/resolve?ref=vercel/turborepo/examples/with-nextjs-elysia/apps/web/AGENTS.md GET https://markdownregistry.com/api/v1/blob/e3447d84251880fb34cfae09131cb4c57471529bbfe60976a3245793cf621627
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.