AGENTS.md@tools/vibespecA
AGENTS.md@tools/vibespec from eliza-research/thenetwork is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add eliza-research/thenetwork/tools/vibespec/AGENTS.md@git:20261113.ab49380Pins git:20261113.ab49380 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- eliza-research/thenetwork
- Path
tools/vibespec/AGENTS.md- Versions recorded
- 1
- Latest version
- git:20261113.ab49380, committed Nov 13, 2026
- Size
- 34,855 bytes
- Repository stars
- 67
- 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
# Operating procedure for agents Each application has one source of truth, `spec/<name>.md`: its stories, rules and Quint model. `gen/` is derived from it. Keep the spec true to what the user wants and `npm run check` green. **Read this file and [README.md](README.md) in full before doing any work.** The spec format, naming rules and everything the tools accept are in [Spec reference](#spec-reference) below. ## Who does what `npm run check` detects; you translate: story → rules, rule → Quint, changed Quint → prose, counterexample → rule. That is your work in this session; it needs no other program or account. **Whenever `spec/` or `src/` has changed, follow [.claude/skills/sync/SKILL.md](.claude/skills/sync/SKILL.md)**: the loop, what each failure asks of you, and what to report. Claude Code loads it as the `sync` skill; other agents read the file. The user signs off with `npm run accept`. ## Hard rules - Never edit `gen/`, `.spec-cache/` or `spec/*.lock.json`, and never add a `lemmascript.json`. The tools own them; a change there could make a check pass that should not. - Never run `npm run accept -- unproved` unless the user asks. It lowers the …
Read the whole file at its exact version.
How to install
mdr add eliza-research/thenetwork/tools/vibespec/AGENTS.md@sha256:fa4b8d039314b853The line at the top of this page pins the label git:20261113.ab49380, 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_2ratqi4e6rwhn3zv)
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: what changed in eliza-research/thenetwork/tools/vibespec/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 Nov 13, 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 (34855 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
eliza-research/thenetwork · 67 stars · license none declared · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2ratqi4e6rwhn3zv GET https://markdownregistry.com/api/v1/resolve?ref=eliza-research/thenetwork/tools/vibespec/AGENTS.md GET https://markdownregistry.com/api/v1/blob/fa4b8d039314b8538a69929dc5f9df0b0bcb47a0ed14bac4f540dfcf909e18f0
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.