AGENTS.mdA
AGENTS.md from ximing/vital is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add ximing/vital/AGENTS.md@git:20261017.74432daPins git:20261017.74432da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- ximing/vital
- Path
AGENTS.md- Versions recorded
- 4
- Latest version
- git:20261017.74432da, committed Oct 17, 2026
- First version recorded
- Sep 13, 2026
- Size
- 3,847 bytes
- Repository stars
- 3
- License
- none declared
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
# Vital — agent notes Monorepo for a single-user personal OS (inbox → todos → reports). Server is Fastify 5 + Drizzle + PostgreSQL. ## Database: no foreign keys PostgreSQL tables **do not use foreign keys**. `user_id` / `*_id` columns are plain `char(36)`. Ownership, existence, and cascade cleanup are enforced in the service layer. When you add or change a write path: - Assert the referenced row exists and `user_id` matches before insert/update. - Any operation that touches more than one table (parent + children, join rows, outbox, history) **must run in a single `getDb().transaction`**. There is no engine-level `ON DELETE CASCADE` / `SET NULL` to fall back on. - Hard-delete of a parent must explicitly delete or null children in that same transaction. Soft-delete (`deleted_at`) can leave children; restore must still see them. - Tests: `resetDb()` deletes every table explicitly. New tables go on that list. - After a schema change, **restart the worker** (`pnpm --filter @vital/server worker`). API `tsx watch` reloads; the worker process does not. Typical parent → child cleanup (same transaction): | Delete | Also in the same transaction | |---|---| …
Read the whole file at its exact version.
How to install
mdr add ximing/vital/AGENTS.md@sha256:17408d99b0475a68The line at the top of this page pins the label git:20261017.74432da, 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_oaq2zwcjfu4blqed)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 13, 2026 and Oct 17, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.74432da latest | 2026-10-17 | 74432da | 3,847 B | A | view · diff |
| git:20260918.fe291fa | 2026-09-18 | fe291fa | 2,262 B | A | view · diff |
| git:20260918.6b86ccc | 2026-09-18 | 6b86ccc | 1,993 B | A | view · diff |
| git:20260913.51dc0f7 | 2026-09-13 | 51dc0f7 | 1,853 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (3847 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
ximing/vital · 3 stars · license none declared · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oaq2zwcjfu4blqed GET https://markdownregistry.com/api/v1/resolve?ref=ximing/vital/AGENTS.md GET https://markdownregistry.com/api/v1/blob/17408d99b0475a685b8a1268142d0b20aef6b33df07ef4d77b3018d13aff1575
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.