agentleFS
on-keydayon-keyday/agent-harness/AGENTS.md

agent-harness

AGENTS.md2 starsChanged 2 days agoMITView on GitHub

This task runs inside a harness-managed worktree. - harness-cli is on PATH; HARNESS_* env vars are pre-set by the runner. - Read the harness-cli skill for agent-to-agent messaging on the agentboard: run harness-cli skill harness-cli (works in any agent), or open .claude/skills/harness-cli/SKILL.md / .agents/skills/harness-cli/SKILL.md. - Your inbound agentboard topic is chat.<first-8-hex-of-HARNESS_TASK_ID>; the server subscribes you to it. There is no board-wide discovery topic. Harness-injected files in this worktree are NOT your work — do not commit them as your own:…

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:

    Read the harness-cli skill for agent-to-agent messaging on the agentboard: run harness-cli skill harness-cli (works in any agent), or open …

    line 4

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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 task runs inside a harness-managed worktree.

  • harness-cli is on PATH; HARNESS_* env vars are pre-set by the runner.
  • Read the harness-cli skill for agent-to-agent messaging on the agentboard: run harness-cli skill harness-cli (works in any agent), or open .claude/skills/harness-cli/SKILL.md / .agents/skills/harness-cli/SKILL.md.
  • Your inbound agentboard topic is chat.<first-8-hex-of-HARNESS_TASK_ID>; the server subscribes you to it. There is no board-wide discovery topic.

Harness-injected files in this worktree are NOT your work — do not commit them as your own: this file (CLAUDE.md/AGENTS.md/GEMINI.md), .claude/, and .agents/skills/. If you intentionally add project-specific content to one of them, that addition IS legitimate work and may be 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.