AGENTS.md@e2e/demo-nextA
AGENTS.md@e2e/demo-next from zitadel/nextgen is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add zitadel/nextgen/e2e/demo-next/AGENTS.md@git:20261020.fa301b9Pins git:20261020.fa301b9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- zitadel/nextgen
- Path
e2e/demo-next/AGENTS.md- Versions recorded
- 3
- Latest version
- git:20261020.fa301b9, committed Oct 20, 2026
- First version recorded
- Oct 14, 2026
- Size
- 2,828 bytes
- Repository stars
- 27
- License
- AGPL-3.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
# Agent Instructions — the demo lanes (`e2e/demo-next`, `e2e/demo-nuxt`) The demo lanes drive `apps/demo-next` and `apps/demo-nuxt` end to end, and cover only what Vitest cannot reach: the framework integration. Both frameworks have lanes because each SDK implements the proxy and route protection differently, so a regression in one does not show in the other. | Lane | Specs | Backend | App | | --- | --- | --- | --- | | `moon run e2e:demo-next-mock` | `demo-next/src/` | `@zitadel/api-mock` on `:8080` | `:3002` | | `moon run e2e:demo-next-real` | `demo-next/src-real/` | a real instance on `:8092` (`@zitadel/testing`) | `:3002` | | `moon run e2e:demo-nuxt-mock` | `demo-nuxt/src/` | `@zitadel/api-mock` on `:8081` | `:3001` | The Nuxt lane's mock gets its own port so both mock lanes run side by side. Install browsers once with `corepack pnpm --filter @zitadel/e2e exec playwright install`. How the lanes run in CI and locally: [`packages/testing/AGENTS.md`](../../packages/testing/AGENTS.md#moon-and-the-e2e-lanes). ## What belongs here On each framework, the lanes prove that: - `<zitadel-login>` mounts inside the client-only boundary (Next's …
Read the whole file at its exact version.
How to install
mdr add zitadel/nextgen/e2e/demo-next/AGENTS.md@sha256:ef42286aaa8b152bThe line at the top of this page pins the label git:20261020.fa301b9, 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_ogzp4vkbiz5xqztz)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 14, 2026 and Oct 20, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.fa301b9 latest | 2026-10-20 | fa301b9 | 2,828 B | A | view · diff |
| git:20261020.8d47d7a | 2026-10-20 | 8d47d7a | 2,736 B | A | view · diff |
| git:20261014.2e7bbe8 | 2026-10-14 | 2e7bbe8 | 3,186 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2828 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
zitadel/nextgen · 27 stars · license AGPL-3.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ogzp4vkbiz5xqztz GET https://markdownregistry.com/api/v1/resolve?ref=zitadel/nextgen/e2e/demo-next/AGENTS.md GET https://markdownregistry.com/api/v1/blob/ef42286aaa8b152b30268cfcb592ebccc7269695656d10431f57665e741e99b0
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.