agentleFS
arnaudgelasarnaudgelas/K-Ops/.codex/AGENTS.md

K-Ops

AGENTS.md1 starsChanged 7 months agoMITView on GitHub

This repo is designed for agentic CLI workflows. Canonical rules: see OPERATING_RULES.md.

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

The file

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

9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer modifying a small number of files with high signal.

    line 36
  2. Distinctive:

    Prefer precise edits over broad rewrites.

    line 37
  3. Distinctive:

    When uncertain, mark uncertainty explicitly.

    line 39
  4. Very specific:

    Use uv run kops install-agent-assets to sync canonical skills/templates to the Codex runtime directory.

    line 42
  5. Very specific:

    Use uv run kops validate to confirm config loads before running workflows.

    line 43
  6. Very specific:

    Prefer uv run kops compile --agent codex when you want Codex to do the compilation pass.

    line 44
  7. Very specific:

    Use uv run kops extract-claims, extract-contradictions, and scorecard to keep the machine-readable quality layer current.

    line 45
  8. Very specific:

    After extract-claims, run uv run kops verify-spans to confirm claim quote anchors exist in their sources, and uv run kops review-queue to …

    line 46
  9. Very specific:

    Use uv run kops next-action for the single next repair + convergence verdict, and uv run kops consequence-gate --tier <...> before backing …

    line 47

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

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

AGENTS.md

This repo is designed for agentic CLI workflows.

Canonical rules: see OPERATING_RULES.md.

Roles

Source Ingestor

Goal: transform new raw sources into normalized source summaries.

Wiki Compiler

Goal: merge source summaries into durable concept pages and indexes.

Lint + Heal

Goal: detect contradictions, weak structure, missing backlinks, and unsupported claims.

Q&A Agent

Goal: answer using the vault, then file durable insights back into the vault.

Render Agent

Goal: convert the current vault into memos, briefings, slide outlines, diagrams, and plot specs.

Repo Contract

  • data/raw/ holds source evidence
  • notes/Sources/ holds per-source summaries
  • notes/Concepts/ holds durable knowledge pages
  • notes/Answers/ holds generated answer memos
  • notes/Home.md is the Obsidian entry point
  • notes/TODO.md tracks gaps and healing tasks
  • notes/Runbooks/Agent_Workflow_Quick_Reference.md is the compact operator map for cross-CLI workflows
  • research/ holds resumable research-run artifacts and stays separate from curated vault notes
  • kops bootstrap --target <dir> creates a new blank starter vault with the same file structure and tooling

Behavioral Guardrails

  • Prefer modifying a small number of files with high signal.
  • Prefer precise edits over broad rewrites.
  • Preserve provenance from source summaries into concept pages.
  • When uncertain, mark uncertainty explicitly.

Codex-Specific Notes

  • Use uv run kops install-agent-assets to sync canonical skills/templates to the Codex runtime directory.
  • Use uv run kops validate to confirm config loads before running workflows.
  • Prefer uv run kops compile --agent codex when you want Codex to do the compilation pass.
  • Use uv run kops extract-claims, extract-contradictions, and scorecard to keep the machine-readable quality layer current.
  • After extract-claims, run uv run kops verify-spans to confirm claim quote anchors exist in their sources, and uv run kops review-queue to surface everything awaiting human review.
  • Use uv run kops next-action for the single next repair + convergence verdict, and uv run kops consequence-gate --tier <...> before backing a high-stakes answer or render with the vault's claims.

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.