DeepSeek_Kibborg_Harness / website
AGENTS.md1 starsChanged 49 days agoMITView on GitHub
Follow the root instructions, the documentation standard, and the documentation-site sync workflow. website/ owns only VitePress configuration, presentation assets, and the publication manifest. This file is the only maintained Markdown file in this subtree. Keep canonical prose and generated catalogs in their owning docs/ tier, then expose selected pages through docs.ts. Never add locale, route, API, or copied documentation trees such as website/zh-CN/, website/en/, or website/api/. The projector writes disposable Markdown to the ignored website/.generated/ directory. Never edit or commit…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- xinyuquan985-coder/deepseek-harness-neonword for word, first seen Sep 26, 2026
Other versions1 project uses a version of this.
Word for word · 1
- xinyuquan985-coder/deepseek-harness-neon★ 17100% 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 31,700 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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/notes/AGENTS.mdAGENTS.md
- .agents/notes/archived/AGENTS.mdAGENTS.md
- .agents/notes/implemented/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- examples/AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- packages/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- vendor/AGENTS.mdAGENTS.md
- .agents/notes/implemented/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- examples/CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- vendor/CLAUDE.mdCLAUDE.md
- dsh-archive-agent-notesSkill
- dsh-code-reviewSkill
- dsh-doc-site-syncSkill
- dsh-doc-standardsSkill
- dsh-find-simplificationsSkill
- dsh-merging-stacked-prsSkill
- dsh-pre-push-checksSkill
- dsh-prose-standardSkill
- dsh-translate-docsSkill
- dsh-trim-cot-leakageSkill
- hakker-kibborgSkill
- record-browser-gifSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 3
Follow the root instructions, the documentation standard, and the documentation-site sync workflow.
- Very specific: line 9
Keep canonical prose and generated catalogs in their owning docs/ tier, then expose selected pages through docs.ts.
- Very specific: line 13
Run pnpm docs:check after changing this subtree.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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
AGENTS.md — Documentation website adapter
Follow the root instructions, the documentation standard, and the documentation-site sync workflow.
Keep documentation content out of this tree
website/ owns only VitePress configuration, presentation assets, and the publication manifest. This file is the only maintained Markdown file in this subtree.
Keep canonical prose and generated catalogs in their owning docs/ tier, then expose selected pages through docs.ts. Never add locale, route, API, or copied documentation trees such as website/zh-CN/, website/en/, or website/api/.
The projector writes disposable Markdown to the ignored website/.generated/ directory. Never edit or commit .generated/, .cache/, or .dist/.
Run pnpm docs:check after changing this subtree; the gate rejects additional non-ignored Markdown under website/.
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.