agentleFS
Sign inStart free
AgriciDanielAgriciDaniel/deepseek-harness-brain/AGENTS.md

deepseek-harness-brain

AGENTS.md9 starsChanged 3 months agoMITView on GitHub

The canonical agent entrypoint is SKILL.md; this file exists for agent runtimes that load project-level AGENTS.md instructions. - Do not call this brain market-ready unless scripts/audit_brain.py --require market-ready passes. - A scaffold is not a finished brain. - Domain-specific claims require dated trustworthy sources. - Research evidence must be recorded in references/source-ledger.json. - Adapter completion must be recorded in references/adapter-manifest.json. - Preserve .raw/ as immutable source material. - Keep Obsidian wiki/, CODEX.md, dashboards, canvases, frontmatter, wikilinks, graph hygiene, and source…

  • 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,774 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 repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not call this brain market-ready unless scripts/audit_brain.py --require market-ready passes.

    line 19
  2. Very specific:

    Keep Obsidian wiki/, CODEX.md, dashboards, canvases, frontmatter, wikilinks, graph hygiene, and source citations healthy.

    line 26

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

DeepSeek Harness Brain Agent Instructions

The canonical agent entrypoint is SKILL.md; this file exists for agent runtimes that load project-level AGENTS.md instructions.

Read Order

  1. SKILL.md
  2. README.md
  3. docs/OPERATOR_KIT.md
  4. docs/PRODUCT_BOUNDARIES.md
  5. references/product-spec.md
  6. references/source-ledger.json
  7. references/adapter-manifest.json
  8. agents/deepseek-harness-secretary.md

Operating Rules

  • Do not call this brain market-ready unless scripts/audit_brain.py --require market-ready passes.
  • A scaffold is not a finished brain.
  • Domain-specific claims require dated trustworthy sources.
  • Research evidence must be recorded in references/source-ledger.json.
  • Adapter completion must be recorded in references/adapter-manifest.json.
  • Preserve .raw/ as immutable source material.
  • Keep Obsidian wiki/, CODEX.md, dashboards, canvases, frontmatter, wikilinks, graph hygiene, and source citations healthy.
  • V1 is advisory and read-only unless a future release defines approval and rollback for mutations.
  • For grounded answers or vault maintenance, use agents/deepseek-harness-secretary.md. It must cite a vault note and an official URL for any domain claim.

Verification

python -m compileall scripts deepseek_harness_brain tests
python tests/test_pipeline.py
python scripts/audit_brain.py --json
python scripts/package_release.py --version 0.2.0 --release-type community-ready

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.

Check your setup, free