agentleFS
Sign inStart free
RedSe7enZRedSe7enZ/agent-safety-skill/templates/AGENTS.md

agent-safety-skill / templates

AGENTS.md0 starsChanged 5 months agoMITView on GitHub

Use these lightweight safety rules for AI coding agents working in this repository. Before acting, classify: For L2/L3 work, end with:

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use these lightweight safety rules for AI coding agents working in this repository.

    line 3

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

Agent Safety Rules

Use these lightweight safety rules for AI coding agents working in this repository.

Startup Gate

Before acting, classify:

Task type:
Risk level: L0 / L1 / L2 / L3
Authorization: confirmed / missing / blocked
Will modify files: yes / no
Will leave local machine or repo: yes / no
Decision: proceed / ask confirmation / block

Risk Levels

  • L0: answer only, no file changes.
  • L1: read-only review or analysis, no file changes.
  • L2: local reversible edits within a clear scope, verify before handoff.
  • L3: delete, overwrite, configure, change permissions, touch secrets, push, deploy, publish, or call external write APIs. Stop and ask for explicit confirmation.

Delivery Evidence

For L2/L3 work, end with:

Changed:
Verified:
Not done:
Risks:
Next:

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