AGENTS.md@.githubA
AGENTS.md@.github from vercel/next.js is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add vercel/next.js/.github/AGENTS.md@git:20260526.b6fea5dPins git:20260526.b6fea5d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- vercel/next.js
- Path
.github/AGENTS.md- Versions recorded
- 1
- Latest version
- git:20260526.b6fea5d, committed May 26, 2026
- Size
- 2,925 bytes
- Repository stars
- 143,627
- 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
## Events Triggering Workflows
- Use `pull_request`, not `pull_request_target`. If you genuinely need secrets on a fork PR, never check out the PR's HEAD ref in the privileged job.
- Be extremely careful with `workflow_run` for similar to `pull_request_target`.
- When operating on `pull_request`, think if the workflow should use `concurrency` to cancel superseded runs.
## Workflow Permissions
Set `permissions: {}` at the workflow level and grant the minimum needed per-job.
```yaml
permissions: {}
jobs:
lint:
permissions:
contents: read
# ...
comment-on-pr:
permissions:
contents: read
pull-requests: write
# ...
```
## Third-party GitHub Actions
Prefer GitHub-provided (`actions/*`) and Vercel-owned actions. For third-party actions:
- Don't include the third-party action if it doesn't provide much value, e.g. if a `pnpm`-installable tool can do the same job without much more code.
- Pin to a full commit SHA, never a tag or branch. Include the tag as a trailing comment:
```yaml
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
```
…Read the whole file at its exact version.
How to install
mdr add vercel/next.js/.github/AGENTS.md@sha256:2249a2aa51b311a4The line at the top of this page pins the label git:20260526.b6fea5d, 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_eojh6hgzu5zjnhfc)
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 vercel/next.js/.github/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 1 version of this file, committed on May 26, 2026.
Watch this file (sign in, one email per new version)
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 (2925 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/next.js · 143,627 stars · license MIT · pushed 2026-11-21 · branch canary
API
GET https://markdownregistry.com/api/v1/artifacts/art_eojh6hgzu5zjnhfc GET https://markdownregistry.com/api/v1/resolve?ref=vercel/next.js/.github/AGENTS.md GET https://markdownregistry.com/api/v1/blob/2249a2aa51b311a478c9fb3281499f83e8583c98618879833b2ce27ca5ff14ad
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.