agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/dokion/AGENTS.md

dokion

AGENTS.md1 starsChanged 3 months agoMITView on GitHub

Read skills/dokion-hardening/SKILL.md when the task involves Dokion execution, findings, remediation, verification, or reporting. .dokion/playbook.json is the only execution authority. Do not edit it unless the user explicitly asks to author or change the playbook. Never select, install, substitute, reorder, upgrade, or enable capabilities on the user's behalf. Run the complete set before claiming a Dokion code change is ready: For frontend changes also run: Use tests first for runtime behavior changes. Preserve immutable playbook checks, append-only evidence, exact repair rollback,…

The file

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

4 rules. About 1 is common, 1 is distinctive, and 2 are very specific to this project.

  • ≈1

    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
  1. Very specific:

    Read skills/dokion-hardening/SKILL.md when the task involves Dokion execution, findings, remediation, verification, or reporting.

    line 3
  2. Very specific:

    Run the complete set before claiming a Dokion code change is ready:

    line 17
  3. Distinctive:

    Use tests first for runtime behavior changes.

    line 37
  4. Common:

    Do not store credentials or private MCP configuration in the repository

    line 45

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

Dokion Repository Instructions

Read skills/dokion-hardening/SKILL.md when the task involves Dokion execution, findings, remediation, verification, or reporting.

.dokion/playbook.json is the only execution authority. Do not edit it unless the user explicitly asks to author or change the playbook. Never select, install, substitute, reorder, upgrade, or enable capabilities on the user's behalf.

Stack

  • Runtime: Bun
  • Language: TypeScript
  • Contracts: JSON Schema
  • State: .dokion/state.json
  • Human report: HARDENING.md

Required verification

Run the complete set before claiming a Dokion code change is ready:

bun run test
bun run typecheck
bun run validate:contracts
bun run build

For frontend changes also run:

cd frontend
bun install --frozen-lockfile
bun run test
bun run lint
bun run build
cd ..

Use tests first for runtime behavior changes. Preserve immutable playbook checks, append-only evidence, exact repair rollback, and explicit approval records.

Repository boundaries

  • Runtime-owned paths: .dokion/** and HARDENING.md
  • User-owned execution configuration: .dokion/playbook.json
  • Catalog entries in dokion.json are inert
  • Recommendations may be written only as inert suggestions
  • Do not store credentials or private MCP configuration in the repository

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