llms.txtA
llms.txt from pisberg/vibetags is an llms.txt file: plain text a project publishes for AI models to read.
mdr add pisberg/vibetags/llms.txt@git:20261116.f6d4309Pins git:20261116.f6d4309 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- llms.txt file
- Repository
- pisberg/vibetags
- Path
llms.txt- Versions recorded
- 14
- Latest version
- git:20261116.f6d4309, committed Nov 16, 2026
- First version recorded
- Sep 21, 2026
- Size
- 22,897 bytes
- Repository stars
- 25
- 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
# VibeTags > Compile-time Java annotation processor (JSR 269) that generates AI-platform guardrail configuration files — CLAUDE.md, .cursorrules, llms.txt, and 50+ others — from `@AI*` annotations in Java source. Zero runtime overhead; all annotations are `RetentionPolicy.SOURCE`. Orientation facts: build order is `vibetags-annotations` → `vibetags` → `vibetags-bom` → `example`; output files are opt-in by file existence (the processor never creates a file that doesn't already exist); generated content lives between `VIBETAGS-START`/`VIBETAGS-END` markers and hand-authored content outside them is preserved. ## Docs - [CLAUDE.md](CLAUDE.md): agent briefing — build commands, load-bearing architecture invariants, project guardrails (tool-neutral despite the name) - [README.md](README.md): project intro, quick start, supported platforms - [USAGE.md](USAGE.md): consumer guide — every annotation with usage examples - [docs/README.md](docs/README.md): the documentation index — every document and the question it answers - [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md): technical deep dive — system diagram, data flow, design decisions …
Read the whole file at its exact version.
How to install
mdr add pisberg/vibetags/llms.txt@sha256:25be4252e45d9519The line at the top of this page pins the label git:20261116.f6d4309, 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_3fxw5pcmkstsai5q)
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 pisberg/vibetags/llms.txt 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 llms.txt from somewhere else? Ask it: where did my llms.txt 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 14 versions of this file, between Sep 21, 2026 and Nov 16, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.f6d4309 latest | 2026-11-16 | f6d4309 | 22,897 B | A | view · diff |
| git:20261115.6d423ff | 2026-11-15 | 6d423ff | 22,569 B | A | view · diff |
| git:20261113.82bf3e7 | 2026-11-13 | 82bf3e7 | 22,500 B | A | view · diff |
| git:20261107.51bc3ad | 2026-11-07 | 51bc3ad | 21,815 B | A | view · diff |
| git:20261007.cc9cef2 | 2026-10-07 | cc9cef2 | 21,055 B | A | view · diff |
| git:20261006.eb5db58 | 2026-10-06 | eb5db58 | 20,645 B | A | view · diff |
| git:20261006.c9635c9 | 2026-10-06 | c9635c9 | 20,573 B | A | view · diff |
| git:20261005.815b18a | 2026-10-05 | 815b18a | 20,491 B | A | view · diff |
| git:20261005.a7a6600 | 2026-10-05 | a7a6600 | 20,376 B | A | view · diff |
| git:20260926.4c5de5c | 2026-09-26 | 4c5de5c | 19,215 B | A | view · diff |
| git:20260926.4616fdb | 2026-09-26 | 4616fdb | 18,863 B | A | view · diff |
| git:20260925.9f319ed | 2026-09-25 | 9f319ed | 18,514 B | A | view · diff |
| git:20260925.291bde5 | 2026-09-25 | 291bde5 | 18,758 B | A | view · diff |
| git:20260921.99f5f6d | 2026-09-21 | 99f5f6d | 19,187 B | A | view |
Installed this file, say at llms.txt? 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 (22897 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
pisberg/vibetags · 25 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3fxw5pcmkstsai5q GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/llms.txt GET https://markdownregistry.com/api/v1/blob/25be4252e45d9519d462e698628e52b030247613e832cfbfb91ef763359b50a3
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 add an llms.txt file to a website · which agent file does what.
More from pisberg/vibetags
Every file in pisberg/vibetags