agentleFS
serhii12serhii12/vault-os/_admin/AGENTS.md

vault-os / _admin

AGENTS.md2 starsChanged 6 months agoMITView on GitHub

Templates, attachments, vault configuration, and connection documentation. Connection Map: Read CONNECTIONS.md in this folder for the full relation diagram showing how tasks, notes, projects, tags, people, goals, and content link together. This is essential before creating files that need to connect to other parts of the vault. Key connection properties used across templates: Agent rules: Read CONNECTIONS.md before creating files that need to link to other vault content. You may create or improve templates when asked.

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Connection Map: Read CONNECTIONS.md in this folder for the full relation diagram showing how tasks, notes, projects, tags, people, goals, …

    line 5
  2. Very specific:

    Agent rules: Read CONNECTIONS.md before creating files that need to link to other vault content.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md 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
AGENTS.md

Admin

Templates, attachments, vault configuration, and connection documentation.

Connection Map: Read CONNECTIONS.md in this folder for the full relation diagram showing how tasks, notes, projects, tags, people, goals, and content link together. This is essential before creating files that need to connect to other parts of the vault.

Structure:

  • CONNECTIONS.md — Relation diagram and frontmatter property reference
  • templates/notes/ — Note, Web Clip, Meeting Note, Voice Note, Journal Entry, Focus Session, Habit Tracker, Weekly Review Checklist, Task
  • templates/periodic/ — Daily, Weekly, Monthly, Quarterly, Yearly note templates
  • templates/para/ — Project, Area, Resource, Person, Book, Recipe, Goal
  • templates/content/ — Content Idea
  • attachments/ — Images and files referenced by notes

Key connection properties used across templates:

  • project: — direct relation to a project (tasks, notes)
  • pulls: — reference material pulled into a project (notes only)
  • tag: — PARA organizer (areas, resources, entities)
  • people: — person relation (tasks, notes, projects)
  • goal: — goal relation (projects)
  • area: — area relation (projects, goals)
  • content: — content piece relation (tasks, notes)

Agent rules: Read CONNECTIONS.md before creating files that need to link to other vault content. You may create or improve templates when asked.

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.