agentleFS
VincentChuWaiChowVincentChuWaiChow/vanguard-frontier-agentic/schemas/AGENTS.md

vanguard-frontier-agentic / schemas

AGENTS.md23 starsChanged 4 months agoApache-2.0View on GitHub

- skill.frontmatter.schema.json — required SKILL.md frontmatter contract; enforced by tests/validate-skill-frontmatter-schema.py (validate:skill-schema). - agent.schema.json — agent metadata.json contract (id, provider, harnesses, source_type, official_docs, security_notes, last_verified, companion_skills). - agent.frontmatter.schema.json — required AGENT.md frontmatter contract. Empirically derived from the 141-file corpus: only metadata.author and metadata.version are required. Optional fields (name, description, model, allowed-tools, tools, color) are typed when present, and additionalProperties: true keeps harness-specific extensions non-breaking. Enforced by tests/validate-agent-frontmatter-schema.py (validate:agent-schema).

The file

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

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

  • 3

    Very specific

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

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

    Keep schema enums aligned with validator constants in tests/validate-catalog.py.

    line 8
  2. Very specific:

    Update docs/release-versioning.md if schema compatibility policy changes.

    line 9
  3. Very specific:

    Run npm run validate after schema edits.

    line 10

≈ “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

AGENTS.md

Purpose

  • Store JSON Schema contracts for catalog metadata and manifests.

Rules

  • Schema-required-field changes are breaking for npm consumers.
  • Keep schema enums aligned with validator constants in tests/validate-catalog.py.
  • Update docs/release-versioning.md if schema compatibility policy changes.
  • Run npm run validate after schema edits.

Schemas

  • skill.frontmatter.schema.json — required SKILL.md frontmatter contract; enforced by tests/validate-skill-frontmatter-schema.py (validate:skill-schema).
  • agent.schema.json — agent metadata.json contract (id, provider, harnesses, source_type, official_docs, security_notes, last_verified, companion_skills).
  • agent.frontmatter.schema.json — required AGENT.md frontmatter contract. Empirically derived from the 141-file corpus: only metadata.author and metadata.version are required. Optional fields (name, description, model, allowed-tools, tools, color) are typed when present, and additionalProperties: true keeps harness-specific extensions non-breaking. Enforced by tests/validate-agent-frontmatter-schema.py (validate:agent-schema).

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.