agentleFS
josixjosix/agent-flow/AGENTS.md

agent-flow

AGENTS.md8 starsChanged 17 days agoMITView on GitHub

This file is for Codex reviewing changes to the agent-flow plugin itself. Claude Code sessions in this repo use .claude/CLAUDE.md instead. The general co-review rubric — your role next to Lawliet, the output contract (one verdict line + SEVERITY: file:line: issue findings), the severity scale, what to defer to Lawliet, and the tie-breaker — ships with the plugin at templates/codex/review-rubric.md and is inlined into every review prompt by scripts/dispatch-codex-review.sh. Follow it. The checklist below adds the blocker classes specific to…

The file

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

1 rule. About 1 is common, 0 are distinctive, and 0 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    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. Common:

    No secrets: no API keys, tokens, passwords, or credentials in committed files.

    line 31

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

Codex co-review — agent-flow repo checklist

This file is for Codex reviewing changes to the agent-flow plugin itself. Claude Code sessions in this repo use .claude/CLAUDE.md instead.

The general co-review rubric — your role next to Lawliet, the output contract (one verdict line + SEVERITY: file:line: issue findings), the severity scale, what to defer to Lawliet, and the tie-breaker — ships with the plugin at templates/codex/review-rubric.md and is inlined into every review prompt by scripts/dispatch-codex-review.sh. Follow it. The checklist below adds the blocker classes specific to this repository.

Project context

Agent Flow is a multi-agent orchestrator plugin for Claude Code. Agents are markdown files under agents/; orchestration commands live in commands/; skills under skills/; the Phases 3–5 loop is the plugin workflow workflows/implement-review-verify.js. /orchestrate delegates each phase to a specialist agent (Riko, Senku, Loid, Lawliet, Alphonse).

Repo-specific blocker classes

  1. Shell safety: standalone .sh files must use set -euo pipefail at the top (hook scripts that intentionally fail open may use set -uo pipefail with a comment). Flag a new .sh file missing it. ERROR. Embedded Bash inside commands/*.md is out of scope.
  2. Heredoc variable expansion: commands/*.md Bash blocks must not use $VAR inside <<'PROMPT' heredocs — single-quoted delimiters suppress expansion, so the variable is emitted literally. ERROR.
  3. YAML validity: YAML emitted to .claude/orchestration.local.md must be syntactically valid; unclosed keys, bad indentation, or stray characters break the grep-based parsers. ERROR.
  4. No hardcoded paths: scripts must not contain /Users/... or other machine-specific absolute paths — use ${HOME}, $(git rev-parse --show-toplevel), or ${CLAUDE_PLUGIN_ROOT}. WARNING.
  5. No secrets: no API keys, tokens, passwords, or credentials in committed files. ERROR.
  6. Hook output contracts: PreToolUse denials use hookSpecificOutput.permissionDecision: "deny", never top-level continue: false (which halts the whole session); Stop hooks emit {"decision": "block", ...} only when blocking and stay silent otherwise (sole exception: the {systemMessage} bypass notice when .claude/skip-test-verification exists); a hook's stdout must be exactly one JSON object (tool output goes to stderr). ERROR.
  7. Workflow script rules: workflows/*.js must keep export const meta a pure literal as the first statement, must not use Date.now(), Math.random(), argless new Date(), or import(), and behavior changes need a matching scenario in scripts/test-implement-review-verify.js. ERROR for the forbidden APIs, WARNING for a missing test.

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.