agentleFS
0xdewy0xdewy/skills/AGENTS.md

skills

AGENTS.md1 starsChanged 36 days agoMITView on GitHub

This repository authors and tests Codex-compatible agent skills. The canonical skill sources live in skills/*/SKILL.md with optional references/, scripts/, evals/, templates/, and memory/ subdirectories. Codex discovers installed copies through user skill locations such as ~/.codex/skills and ~/.agents/skills. The repo root .agents/ directory may be read-only in managed environments, so do not assume it can be edited. - For a skill change, read that skill's SKILL.md first. - Read referenced files only when the selected skill points to them for the…

  • Deletes or force-pushes

The file

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

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Read referenced files only when the selected skill points to them for the current task.

    line 16
  2. Very specific:

    Use skills/common/ for shared guidance that affects multiple skills.

    line 18
  3. Very specific:

    Use evals/evals.json when changing triggers, output contracts, safety rules, or behavior that should be tested.

    line 22
  4. Distinctive:

    Do not inspect or summarize these unless the user explicitly asks about local tooling, caches, or runtime state:

    line 27
  5. Distinctive:

    Never use whole-tree destructive recovery commands such as git reset --hard, git checkout ., or broad git restore ..

    line 40
  6. Distinctive:

    Prefer patch-scoped edits and reversions.

    line 44
  7. Very specific:

    Do not add bypass, evasion, credential-harvesting, or access-control circumvention instructions to skills.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

Codex Guidance

Repository Purpose

This repository authors and tests Codex-compatible agent skills. The canonical skill sources live in skills/*/SKILL.md with optional references/, scripts/, evals/, templates/, and memory/ subdirectories.

Codex discovers installed copies through user skill locations such as ~/.codex/skills and ~/.agents/skills. The repo root .agents/ directory may be read-only in managed environments, so do not assume it can be edited.

What To Read

  • For a skill change, read that skill's SKILL.md first.
  • Read referenced files only when the selected skill points to them for the current task.
  • Use skills/common/ for shared guidance that affects multiple skills. In skill text, reference it sibling-relative as ../common/... so paths resolve both from the repo and from an installed skill directory (the skill CLI links common/ as a sibling of each installed skill).
  • Use evals/evals.json when changing triggers, output contracts, safety rules, or behavior that should be tested.

What To Ignore

Do not inspect or summarize these unless the user explicitly asks about local tooling, caches, or runtime state:

  • .venv/
  • .pytest_cache/
  • **/__pycache__/
  • **/*.pyc
  • .claude/settings.local.json
  • skills/**/.claude/settings.local.json
  • generated reports, temporary workspaces, and cache directories

Safety

  • Never use whole-tree destructive recovery commands such as git reset --hard, git checkout ., or broad git restore ..
  • Preserve unrelated worktree changes. This repo is often dirty during skill development.
  • Prefer patch-scoped edits and reversions.
  • Do not add bypass, evasion, credential-harvesting, or access-control circumvention instructions to skills.

Verification

For any skill edit, run:

python3 scripts/check_sources.py
python3 scripts/validate_skills.py

check_sources.py parses every Python, shell, and eval JSON file without creating __pycache__/; validate_skills.py checks the skill contracts.

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.