agentleFS
fierc3fierc3/agent-harness-template/AGENTS.md

agent-harness-template

AGENTS.md0 starsChanged 3 months agoMITView on GitHub

This template has not been initialized for a project. Before substantial project work, read and follow .agents/skills/project-kickoff/SKILL.md. When the kickoff is complete, replace the project context below, rewrite README.md with project-specific documentation, delete this entire DO KICKOFF section, then delete .agents/skills/project-kickoff/. This file is the shared source of truth for repository-wide agent guidance. Keep it short and durable; put focused knowledge and repeatable workflows in skills instead of duplicating them here. Skills live in .agents/skills/. Use a relevant skill before…

  • 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 32,671 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 repository4 other files it gives its agents.

The file

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

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    When the kickoff is complete, replace the project context below, rewrite README.md with project-specific documentation, delete this entire …

    line 8
  2. Distinctive:

    Keep it short and durable.

    line 18
  3. Very specific:

    Use .agents/skills/skill-creator/SKILL.md when creating or revising a skill.

    line 27
  4. Distinctive:

    Read the repository's relevant instructions and skill before changing files.

    line 31
  5. Very specific:

    When changing this template's harness files, run ./scripts/verify-harness.sh before handing off the change.

    line 34

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

Agent instructions

DO KICKOFF

This template has not been initialized for a project. Before substantial project work, read and follow .agents/skills/project-kickoff/SKILL.md.

When the kickoff is complete, replace the project context below, rewrite README.md with project-specific documentation, delete this entire DO KICKOFF section, then delete .agents/skills/project-kickoff/.

Project context

<!-- Add a concise description of this project's purpose, users, architecture, and any non-negotiable conventions here. -->

This file is the shared source of truth for repository-wide agent guidance. Keep it short and durable; put focused knowledge and repeatable workflows in skills instead of duplicating them here.

Skills

Skills live in .agents/skills/. Use a relevant skill before working in the area it covers. Skills own the contextual knowledge and workflows for their topic; keep each skill focused and update it when durable guidance emerges.

Use .agents/skills/skill-creator/SKILL.md when creating or revising a skill.

Working conventions

  • Read the repository's relevant instructions and skill before changing files.
  • Make the smallest change that fully addresses the task, then verify it.
  • Preserve existing user changes and do not commit unless explicitly asked.
  • When changing this template's harness files, run ./scripts/verify-harness.sh before handing off the change.
  • Record temporary investigation notes, task plans, and handoff context in notes/ as Markdown. These files are local scratch material: they are useful for long tasks but are normally not committed.

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.