agentleFS
netanelavrnetanelavr/dotcursor/AGENTS.md

dotcursor

AGENTS.md6 starsChanged 27 days agoMITView on GitHub

Reusable Agent Skills and always-on rules for PRs, review, and shipping. Skills install through the Agent Skills CLI. Rule bodies live in rules/*.mdc. Claude Code reads this file when CLAUDE.md is absent. Use it for install and conventions. This file does not apply the .mdc rules. Do not paste rule bodies here. Skills (any Agent Skills host): npx skills add does not install rules. Copy rules/*.mdc if you want the always-on kit loop. How each vendor picks up rules is…

The file

Show its rules and text

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

21 rules. About 1 is common, 9 are distinctive, and 11 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 11

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Always-on rules are not slash skills.

    line 26
  2. Distinctive:

    When adding a new skill:

    line 45
  3. Very specific:

    Create a directory under skills/ with the kit- prefix (e.g., skills/kit-new-skill/)

    line 46
  4. Very specific:

    Add a SKILL.md file with YAML frontmatter:

    line 47
  5. Distinctive:

    Update the Skills Catalog table in README.md

    line 55
  6. Very specific:

    Run kit-audit-skills (overlaps, stale kit-* refs, catalog vs disk, npx skills add .

    line 56
  7. Distinctive:

    When removing a skill:

    line 59
  8. Very specific:

    Delete the skill directory from skills/

    line 60
  9. Distinctive:

    Remove the entry from the Skills Catalog table in README.md

    line 61
  10. Distinctive:

    When renaming a skill:

    line 64
  11. Very specific:

    Update the name field in the YAML frontmatter

    line 66
  12. Very specific:

    Create rules/kit-<name>.mdc with YAML frontmatter (description, alwaysApply and/or globs) and the rule body

    line 74
  13. Distinctive:

    Keep each rule to one concern and under ~50 lines

    line 75
  14. Very specific:

    Add a row to rules/AGENTS.md

    line 76
  15. Distinctive:

    Update the Rules Catalog in README.md

    line 77
  16. Very specific:

    Delete or rename the .mdc file

    line 80
  17. Very specific:

    Update rules/AGENTS.md and the Rules Catalog in README.md

    line 81
  18. Common:

    No secrets: Never commit credentials, tokens, private hostnames, or work emails

    line 85
  19. Distinctive:

    Keep skills generic: Avoid employer names, internal tools, and proprietary details.

    line 86
  20. Distinctive:

    Maintain catalog: Always update README.md when changing skills or rules

    line 87
  21. Very specific:

    Installation path: Use netanelavr/agent-kit in all documentation examples

    line 88

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

agent-kit

Reusable Agent Skills and always-on rules for PRs, review, and shipping. Skills install through the Agent Skills CLI. Rule bodies live in rules/*.mdc.

Claude Code reads this file when CLAUDE.md is absent. Use it for install and conventions. This file does not apply the .mdc rules. Do not paste rule bodies here.

Install

Skills (any Agent Skills host):

npx skills add netanelavr/agent-kit --all

One skill:

npx skills add netanelavr/agent-kit/skills/kit-create-pr

npx skills add does not install rules. Copy rules/*.mdc if you want the always-on kit loop. How each vendor picks up rules is in the README consumption matrix.

Use

  • Invoke a skill with /<skill-name> (Cursor) or the host’s skill command.
  • Always-on rules are not slash skills. Bodies: rules/*.mdc. How each vendor attaches them: README section How vendors consume the kit.

Kit conventions

  • Skill directories and names use the kit- prefix (skills/kit-<name>/).
  • Rule ids use the same prefix (kit-comment-why, …). Bodies live in rules/kit-<name>.mdc.
  • Skills must stay generic: no employer names, internal tools, or proprietary details.
  • Public examples use netanelavr/agent-kit.
  • Catalogs in README.md must match what is on disk.

Agent Maintenance Guide

Guidelines for maintaining agent-kit.

Skill Management

Adding New Skills

When adding a new skill:

  1. Create a directory under skills/ with the kit- prefix (e.g., skills/kit-new-skill/)
  2. Add a SKILL.md file with YAML frontmatter:
    ---
    name: kit-new-skill
    description: Clear description of when to use this skill
    disable-model-invocation: true
    ---
  3. Update the Skills Catalog table in README.md
  4. Run kit-audit-skills (overlaps, stale kit-* refs, catalog vs disk, npx skills add . -l) before treating the add as done

Removing Skills

When removing a skill:

  1. Delete the skill directory from skills/
  2. Remove the entry from the Skills Catalog table in README.md

Renaming Skills

When renaming a skill:

  1. Rename the directory (must maintain kit- prefix)
  2. Update the name field in the YAML frontmatter
  3. Update the Skills Catalog table in README.md

Rule Management

Rules live in rules/ as .mdc files. They are always-on guidance (not slash skills). npx skills add does not install them. Keep rules/AGENTS.md as a short index only.

Adding Rules

  1. Create rules/kit-<name>.mdc with YAML frontmatter (description, alwaysApply and/or globs) and the rule body
  2. Keep each rule to one concern and under ~50 lines
  3. Add a row to rules/AGENTS.md
  4. Update the Rules Catalog in README.md

Removing or Renaming Rules

  1. Delete or rename the .mdc file
  2. Update rules/AGENTS.md and the Rules Catalog in README.md

General Guidelines

  • No secrets: Never commit credentials, tokens, private hostnames, or work emails
  • Keep skills generic: Avoid employer names, internal tools, and proprietary details. Skills must work in any company.
  • Maintain catalog: Always update README.md when changing skills or rules
  • Installation path: Use netanelavr/agent-kit in all documentation examples

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.