harness-setup
Skill2 starsChanged 28 days agoMITView on GitHub
Set up or absorb the harness-kit operating rules in this repo. Use when the user asks to install harness-kit, set up agent rules, fill AGENTS.md placeholders, or fold harness-kit ideas into existing rules docs.
- Pipes a download into a shell
7 other projects use a version of this.
Adopted by
Most recently taken up by
- GangJaeYu/harness_loop_full_koreantheir own version, first seen Oct 29, 2026
- hmj1026/dhpktheir own version, first seen Oct 13, 2026
- Chachamaru127/claude-code-harnesstheir own version, first seen Oct 13, 2026
- jcarlosrodicio/normatheir own version, first seen Oct 9, 2026
- MrBogomips/agentic-harnesstheir own version, first seen Jun 13, 2026
- ArtLjn/harness-setuptheir own version, first seen May 9, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Chachamaru127/claude-code-harness★ 3.2ksame name
- GangJaeYu/harness_loop_full_korean★ 4same name
- hmj1026/dhpk★ 2same name
- BedirT/harness-setup★ 1same name
- jcarlosrodicio/norma★ 1same name
- MrBogomips/agentic-harness★ 1same name
- ArtLjn/harness-setup★ 0same name
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.
In this repository6 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- absence-checkSkill
- canon-upkeepSkill
- independent-reviewSkill
- pattern-cardSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
If the kit files are not present yet, run the installer from the repo root: curl -fsSL …
- Very specific: line 22
Read AGENTS.md and WORK_PROTOCOL.md.
- Very specific: line 29
Keep AGENTS.md to rules only and under ~150 lines.
- Very specific: line 35
Read harness-kit's MINIMAL.md and principles/absence-judgment.md.
- Distinctive: line 36
Read the repo's existing rules docs end to end.
- Distinctive: line 44
Create no new rule files unless the user agrees.
- Distinctive: line 48
Ask a fresh session: "Summarize the rules file in five bullets and quote the top invariant." An answer that is not from the file means the …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Set up harness-kit in this repo
Decide which path applies, then follow only that path.
Which path
- The repo has no rules docs (no AGENTS.md, CLAUDE.md, or house dev guide), or
AGENTS.mdstill contains<PLACEHOLDER>marks -> Fill. - The repo already runs its own rules docs -> Absorb. Never install a second rules system beside an existing one: the same rule stated in two places drifts.
Fill
- If the kit files are not present yet, run the installer from the repo root:
curl -fsSL https://raw.githubusercontent.com/chocomyong/harness-kit/main/install.sh | shIt only adds files and never overwrites. - Read
AGENTS.mdandWORK_PROTOCOL.md. - Survey the repo: file tree,
git log, README and other docs, build and deploy scripts. - Fill every
<PLACEHOLDER>inAGENTS.mdanddocs/REPO_MAP.mdwith measured facts about this repo. Each value comes from something you read here, not from what similar repos look like. - Section 0 (the top invariant) is confirmed by the human. Propose candidates you found - a production datastore, a one-way sync, a paid API - with the file and line that suggested each. Never invent one.
- Keep
AGENTS.mdto rules only and under ~150 lines. Layout and names go todocs/REPO_MAP.md. - Show the full diff and wait for confirmation before saving. Then delete the HTML guidance comments from the filled files.
Absorb
- Read harness-kit's
MINIMAL.mdandprinciples/absence-judgment.md. - Read the repo's existing rules docs end to end.
- Propose the smallest set of edits that folds into the existing docs, in their language and
format:
- the top invariant stated at the top of the highest-authority doc,
- absence-judgment as a named rule,
- an index-first incident registry, seeded with lessons the team keeps re-explaining,
- the three-question done check (ran / fails when wrong / measured in the right place).
- Where a kit idea duplicates one the repo already has, keep theirs and skip the kit's.
- Create no new rule files unless the user agrees. Show the diff before saving.
Confirm it loaded
Ask a fresh session: "Summarize the rules file in five bullets and quote the top invariant." An answer that is not from the file means the wiring is broken; fix that before other work.
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.