harness-engineering-skill / deployment
AGENTS.md1 starsChanged 2 months agoMITView on GitHub
MUST load and follow C:/Users/14156/.codex/skills/goal/SKILL.md for project-level Goal execution. This applies when /goal or $goal is used as a command or project entry point, or when the actual objective independently spans project delivery layers. Merely mentioning /goal in discussion, using it in a quoted command example, or providing a Skill path does not trigger project execution. For an active /goal run that proposes GSD at Layer 6, load C:/Users/14156/.codex/skills/goal/references/gsd-adapter.md after Goal classification and Harness approval. Do not infer GSD activation…
1 other project uses a version of this.
Other versions1 project uses a version of this.
Word for word · 1
- suiuiui6/goal-skill★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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.
- 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
4 rules. About 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
MUST load and follow C:/Users/14156/.codex/skills/goal/SKILL.md for project-level Goal execution.
- Distinctive: line 13
Ask only for the missing project objective.
- Distinctive: line 14
Do not classify or mutate state during goal intake.
- Very specific: line 15
Do not use /goal for local one-off fixes or meta inspection.
≈ “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
Project-Level /goal Routing
MUST load and follow C:/Users/14156/.codex/skills/goal/SKILL.md for project-level Goal execution.
This applies when /goal or $goal is used as a command or project entry point,
or when the actual objective independently spans project delivery layers.
Merely mentioning /goal in discussion, using it in a quoted command example,
or providing a Skill path does not trigger project execution.
Classification: [bootstrap/maintenance], starting from Layer [0..6]Confirmation:is required before bootstrap implementation.- A bare
/goalwithout a concrete objective isgoal-intake. - Ask only for the missing project objective.
- Do not classify or mutate state during goal intake.
- Do not use
/goalfor local one-off fixes or meta inspection. - Windows enforcement is
audit-only-windows.
For an active /goal run that proposes GSD at Layer 6, load
C:/Users/14156/.codex/skills/goal/references/gsd-adapter.md after Goal
classification and Harness approval. Do not infer GSD activation from a mention.
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.

