agentleFS
Sign inStart free
5uck1ess5uck1ess/devkit/AGENTS.md

devkit

AGENTS.md4 starsChanged 4 months agoMITView on GitHub

devkit is a deterministic workflow engine. In this repo, treat the YAML workflow and MCP state as the source of truth: start a workflow, execute only the current step, report the step result, then advance. Claude Code installs lifecycle hooks from hooks/hooks.json and can hard-block out-of-step tools. Codex-specific lifecycle hooks, prompt bridges, and config are planned for the separate devkit-codex adapter, which points Codex at this repo's MCP engine once released. Follow the same workflow policy voluntarily here, and rely…

The file

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

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Use devkit_start to begin a workflow and devkit_advance to move to the next step.

    line 7
  2. Distinctive:

    Do not skip, reorder, or merge workflow steps unless the engine returns a branch/loop transition that does so.

    line 8
  3. Distinctive:

    If an active workflow exists, finish or explicitly stop it before starting a different workflow.

    line 12
  4. Very specific:

    Keep Claude packaging in .claude-plugin/, mcpb/, and hooks/ working.

    line 41
  5. Very specific:

    Keep Codex-specific integration in the separate devkit-codex repository once it is released, unless the change is shared engine behavior.

    line 42
  6. Distinctive:

    Do not hand-edit generated binaries or bundled release artifacts.

    line 43

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

Devkit For Codex

devkit is a deterministic workflow engine. In this repo, treat the YAML workflow and MCP state as the source of truth: start a workflow, execute only the current step, report the step result, then advance.

Workflow Discipline

  • Use devkit_start to begin a workflow and devkit_advance to move to the next step.
  • Do not skip, reorder, or merge workflow steps unless the engine returns a branch/loop transition that does so.
  • For command steps, do not run the command yourself. Call devkit_advance; the engine owns command execution.
  • For prompt steps, do the requested work, summarize the result as the step output, then call devkit_advance.
  • For loop steps, keep the iteration small and use .devkit/scratchpads/current.md when the step asks for it.
  • If an active workflow exists, finish or explicitly stop it before starting a different workflow.

Tool Mapping

  • Claude Bash maps to Codex shell execution.
  • Claude Read, Grep, and Glob map to shell reads, rg, and file inspection.
  • Claude Edit and Write map to apply_patch for manual edits.
  • Claude Agent and Task map to Codex subagents when the current environment exposes them; otherwise use external CLI runners or stop and report that model-diverse dispatch is unavailable.
  • Claude WebFetch and WebSearch map to Codex web tools only when browsing is available and allowed.

Enforcement Notes

Claude Code installs lifecycle hooks from hooks/hooks.json and can hard-block out-of-step tools. Codex-specific lifecycle hooks, prompt bridges, and config are planned for the separate devkit-codex adapter, which points Codex at this repo's MCP engine once released. Follow the same workflow policy voluntarily here, and rely on Codex sandbox/approval boundaries plus the MCP engine for stateful workflow control.

Hard guarantees that still hold under Codex:

  • The MCP engine controls step order.
  • Command steps execute inside the engine.
  • Session state, branches, loops, gates, and reports remain engine-owned.

Guarantees that are adapter-owned under Codex:

  • Blocking arbitrary shell/edit tool use during hard prompt steps.
  • Running post-tool validation automatically after every edit or command.
  • Blocking assistant stop while a workflow is incomplete.
  • Validating subagent completion through a host lifecycle event.

Repo Boundaries

  • Keep Claude packaging in .claude-plugin/, mcpb/, and hooks/ working.
  • Keep Codex-specific integration in the separate devkit-codex repository once it is released, unless the change is shared engine behavior.
  • Do not hand-edit generated binaries or bundled release artifacts.

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