AGENTS.md@assistant/src/plugins/defaults/memoryA
AGENTS.md@assistant/src/plugins/defaults/memory from vellum-ai/vellum-assistant is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add vellum-ai/vellum-assistant/assistant/src/plugins/defaults/memory/AGENTS.md@git:20260922.d53ffc7Pins git:20260922.d53ffc7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- vellum-ai/vellum-assistant
- Path
assistant/src/plugins/defaults/memory/AGENTS.md- Versions recorded
- 9
- Latest version
- git:20260922.d53ffc7, committed Sep 22, 2026
- First version recorded
- Jul 30, 2026
- Size
- 74,009 bytes
- Repository stars
- 1,483
- 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
# Memory Plugin — Agent Instructions Rules for code under `assistant/src/plugins/defaults/memory/` (`MEM/` below). For the user-facing architecture narrative — what each tier does and how the write and read paths fit together — read `assistant/docs/architecture/memory.md` first. This file is the layering contract: where code goes, which names can never be renamed, and how to retire a tier. ## Tier movement is one-way **v1 and v2 are legacy. Assistants move v1 → v2 → v3 and never back.** There is no supported path from v3 to an earlier tier, so "what happens when an assistant returns to v1 (or v2)" is not a scenario this code serves. That rules out a whole class of plausible-sounding work: reconciling state that a lower tier would need, keeping a lower tier's derived data warm while a higher tier is live, or postponing a lower tier's jobs so they survive a downgrade. Review feedback will periodically ask for exactly that — the reasoning looks sound in isolation, because the state genuinely is missing. Decline it and point here. The correct fix for a lower tier's stale derived data is to delete the lower tier (see the runbooks below), not to maintain it. …
Read the whole file at its exact version.
How to install
mdr add vellum-ai/vellum-assistant/assistant/src/plugins/defaults/memory/AGENTS.md@sha256:5b0cf15215bd3e4fThe line at the top of this page pins the label git:20260922.d53ffc7, 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_rfey6cdgcee4u4dk)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Jul 30, 2026 and Sep 22, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.d53ffc7 latest | 2026-09-22 | d53ffc7 | 74,009 B | A | view · diff |
| git:20260917.365ff11 | 2026-09-17 | 365ff11 | 73,851 B | A | view · diff |
| git:20260916.3bb194e | 2026-09-16 | 3bb194e | 72,350 B | A | view · diff |
| git:20260916.57a0969 | 2026-09-16 | 57a0969 | 71,845 B | A | view · diff |
| git:20260906.dcf82c1 | 2026-09-06 | dcf82c1 | 71,505 B | A | view · diff |
| git:20260818.f6e1cb5 | 2026-08-18 | f6e1cb5 | 53,893 B | A | view · diff |
| git:20260818.de25f32 | 2026-08-18 | de25f32 | 53,714 B | A | view · diff |
| git:20260810.e1f0f78 | 2026-08-10 | e1f0f78 | 53,441 B | A | view · diff |
| git:20260730.f82d69d | 2026-07-30 | f82d69d | 53,142 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (74009 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
vellum-ai/vellum-assistant · 1,483 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rfey6cdgcee4u4dk GET https://markdownregistry.com/api/v1/resolve?ref=vellum-ai/vellum-assistant/assistant/src/plugins/defaults/memory/AGENTS.md GET https://markdownregistry.com/api/v1/blob/5b0cf15215bd3e4fba8935a44127788074cff5a47a198e9888f2dece48fa271d
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.