agentleFS
Sign inStart free
vasilyu1983vasilyu1983/AI-Agents-public/hooks/AGENTS.md

AI-Agents-public / hooks

AGENTS.md94 starsChanged 32 days agoMITView on GitHub

- Parse stdin JSON explicitly, and validate every field before use. - Resolve each path to its canonical form before you check it; do not rely on a regex alone. - Never eval hook input. Quote every shell variable. - Fail closed: a guard that cannot parse its input exits 2 (deny), never 0. - Keep synchronous hooks fast. Redact logs and notifications. - Match the JSON output to the schema of the event. Why and procedure: skills/universal/agents-hooks/references/hook-security.md#critical-rules

The file

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

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Never eval hook input. Quote every shell variable.

    line 8
  2. Distinctive:

    Keep synchronous hooks fast.

    line 10

≈ “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
<!-- BEGIN GENERATED: rules/repo --><!-- Generated from rules/repo/ by scripts/checks/check-rules.py --write. Do not edit by hand. -->

hook-scripts.md

  • Parse stdin JSON explicitly, and validate every field before use.
  • Resolve each path to its canonical form before you check it; do not rely on a regex alone.
  • Never eval hook input. Quote every shell variable.
  • Fail closed: a guard that cannot parse its input exits 2 (deny), never 0.
  • Keep synchronous hooks fast. Redact logs and notifications.
  • Match the JSON output to the schema of the event. Why and procedure: skills/universal/agents-hooks/references/hook-security.md#critical-rules
<!-- END GENERATED: rules/repo -->

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.

Check your setup, free