harness-engineering-skill
AGENTS.md1 starsChanged 2 months agoMITView on GitHub
This repository follows the harness-engineering workflow. Before implementation work: Read these as needed for the selected scope: When the user explicitly wants the structured workflow, invoke /harness-engineering. Ask before irreversible actions or changes that affect shared state outside the local workspace.
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 repository5 other files it gives its agents.
- deployment/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- harness-engineeringSkill
- goalSkill
- harness-engineeringSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 11
Read the canonical core files needed for that scope.
- Distinctive: line 12
Do not cross a layer gate without evidence.
- Distinctive: line 13
If a downstream failure breaks an upstream assumption, roll back minimally.
- Distinctive: line 17
Read these as needed for the selected scope:
- Very specific: line 28
When the user explicitly wants the structured workflow, invoke /harness-engineering.
- Distinctive: line 32
Ask before irreversible actions or changes that affect shared state outside the local workspace.
≈ “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.
Files
Repository Instructions
This repository follows the harness-engineering workflow.
Default Execution Rules
Before implementation work:
- Classify the request as
bootstrapormaintenance. - Choose the smallest valid start layer.
- Read the canonical core files needed for that scope.
- Do not cross a layer gate without evidence.
- If a downstream failure breaks an upstream assumption, roll back minimally.
Canonical Sources
Read these as needed for the selected scope:
SKILL.mdcore/layer-details.mdcore/flow.mdcore/checklists.mdcore/exit-and-reentry.mdadapters/Codex/host-map.md
Invocation Rule
When the user explicitly wants the structured workflow, invoke /harness-engineering.
Safety Rule
Ask before irreversible actions or changes that affect shared state outside the local workspace.
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
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.

