agentleFS
petekppetekp/claude-code-setup/AGENTS.md

claude-code-setup

AGENTS.md48 starsChanged 51 days agoMITView on GitHub

This repo is Pete's configuration for Claude Code and Codex: skills, hook scripts, and the setup that links them into ~/.claude and ~/.codex. It is shell scripts and Markdown, plus the TypeScript of the Claude Code mods in mods/. README.md describes the layout.

The file

We split this AGENTS.md 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:

    After changing skills, scripts or mods, run ./scripts/validate.sh and ./scripts/skill-doctor.sh.

    line 7

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

This repo is Pete's configuration for Claude Code and Codex: skills, hook scripts, and the setup that links them into ~/.claude and ~/.codex. It is shell scripts and Markdown, plus the TypeScript of the Claude Code mods in mods/. README.md describes the layout.

  • The repo is public. Do not commit employer or client names, customer data, private file paths, or session state. Private configuration belongs in ~/.agents, which is a private repo.
  • Scripts with a #!/bin/sh shebang must be POSIX sh. macOS runs them with bash 3.2 in POSIX mode. shellcheck misses two of its failures:
    • A case pattern inside $(...) needs a leading paren, as in ("$x"/*). Without it, the script fails with a syntax error.
    • [a-z] also matches uppercase letters under a UTF-8 locale. Use [[:lower:]] and [[:digit:]].
  • After changing skills, scripts or mods, run ./scripts/validate.sh and ./scripts/skill-doctor.sh.
  • mods/DEVELOPING.md explains how to test a mod's UI live without touching your own sessions' state.
  • skills/ holds only skills written here. Never commit a symlink into it. A skill from anywhere else goes in ~/.agents/skills, where link-skills.sh finds it.
  • ~/.claude/settings.json is a regular file that Claude Code owns. Do not link it to the repo. Record it with ./scripts/settings-snapshot.sh.
  • Hook scripts run in every session and fail silently. Before committing a change to one, pipe sample hook JSON into it and check the output. SessionStart output goes into the model's context, so a SessionStart script prints nothing when healthy.
  • To remove a skill installed with npx skills, run npx skills remove -g -y <name>. It removes the files, the key in ~/.agents/.skill-lock.json, and the agent links. If the files are already gone, delete the key with jq; otherwise npx skills update -g reinstalls the skill.

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.