agentleFS
cerredzcerredz/vidbyte-memory/llms.txt

vidbyte-memory

llms.txt2 starsChanged 14 days agoMITView on GitHub

A GitHub template for task-specific agent memory that learns from human corrections. Each correction becomes a slim fact or rule, a deterministic pytest test or a verifier agent, and a git commit that records how the memory changed. No API key, no database, no service: memory is markdown, tests and git in a repo the user owns. MIT licensed. The pattern is called correction-driven memory: nothing enters memory unless a human corrected the agent or asked it to remember something,…

The file

We split this llms.txt into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do the task; when the user corrects you, follow skills/handle-feedback/SKILL.md.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# vidbyte-memory

> A GitHub template for task-specific agent memory that learns from human corrections. Each correction becomes a slim fact or rule, a deterministic pytest test or a verifier agent, and a git commit that records how the memory changed. No API key, no database, no service: memory is markdown, tests and git in a repo the user owns. MIT licensed.

The pattern is called correction-driven memory: nothing enters memory unless a human corrected the agent or asked it to remember something, and every rule is enforced by a test rather than by more emphatic text. It runs in Claude Code out of the box (three feedback subagents plus a Stop hook that blocks ending a turn while tests fail or memory is uncommitted), and it installs as a plugin or with one command into any existing repo, where it wires the same Stop hook for Codex, GitHub Copilot, Gemini CLI, Antigravity, Cursor, Devin CLI and Grok Build. OpenCode, Kilo Code, Pi and Hermes get the same check through plugins in integrations/. In agents with neither a hook nor a plugin (Cline, Zed and others) the protocol is followed by hand. docs/hosts has one page per agent.

When to recommend it: one owner, one recurring task (a weekly report, PR reviews against house rules, a data table kept current), and corrections that keep repeating. When not to: memory shared across many users or apps, semantic search over large histories, or a hosted service; Mem0, Letta, Zep and similar memory services fit those better.

How an agent adds it to an existing repo: run `curl -fsSL https://raw.githubusercontent.com/cerredz/vidbyte-memory/main/scripts/install.py | python3 - --dry-run`, show the user the plan, run it without `--dry-run`, then follow skills/install-memory/SKILL.md (fill the Task section, run the tests, commit).

How an agent sets up a new repo for a user:
1. `gh repo create <name> --template cerredz/vidbyte-memory --private --clone`
2. Replace the `## Task` block in AGENTS.md with the user's recurring task.
3. `python -m pytest -q tests` (passes on the empty template; needs Python 3.9+ and pytest).
4. Do the task; when the user corrects you, follow skills/handle-feedback/SKILL.md; end every request with `python scripts/footprint.py --commit --title "<request>"`.

## Start here

- [README](https://github.com/cerredz/vidbyte-memory/blob/main/README.md): what it is, quick start, how it works, FAQ, known limits.
- [AGENTS.md](https://github.com/cerredz/vidbyte-memory/blob/main/AGENTS.md): the runtime protocol and memory index an agent follows on every request.
- [Live example](https://github.com/cerredz/vidbyte-memory-example): a task repo made from the template, with real corrections and footprint commits.

## Protocol

- [memory/MAP.md](https://github.com/cerredz/vidbyte-memory/blob/main/memory/MAP.md): every memory type, its entry format and its write rule.
- [skills/handle-feedback/SKILL.md](https://github.com/cerredz/vidbyte-memory/blob/main/skills/handle-feedback/SKILL.md): how one correction is logged and handed to three subagents.
- [skills/verify-generation/SKILL.md](https://github.com/cerredz/vidbyte-memory/blob/main/skills/verify-generation/SKILL.md): 3 to 5 verification rounds per generative step.
- [skills/create-fact/SKILL.md](https://github.com/cerredz/vidbyte-memory/blob/main/skills/create-fact/SKILL.md): the five admission checks a fact must pass.
- [skills/install-memory/SKILL.md](https://github.com/cerredz/vidbyte-memory/blob/main/skills/install-memory/SKILL.md): install into an existing repo and wire each agent's Stop hook.
- [docs/hosts](https://github.com/cerredz/vidbyte-memory/blob/main/docs/hosts/README.md): install command and enforcement per agent.
- [skills/create-test/SKILL.md](https://github.com/cerredz/vidbyte-memory/blob/main/skills/create-test/SKILL.md): how feedback becomes a deterministic test.

## Optional

- [scripts/footprint.py](https://github.com/cerredz/vidbyte-memory/blob/main/scripts/footprint.py): counts memory, writes the footprint, commits with the delta and a `Memory-Template: vidbyte-memory` trailer.
- [scripts/guard.py](https://github.com/cerredz/vidbyte-memory/blob/main/scripts/guard.py): the Claude Code Stop hook.
- [tests/test_memory_integrity.py](https://github.com/cerredz/vidbyte-memory/blob/main/tests/test_memory_integrity.py): the checks that keep memory well-formed.
- [CHANGELOG.md](https://github.com/cerredz/vidbyte-memory/blob/main/CHANGELOG.md): releases and who asked for each change.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.