agentleFS
Sign inStart free
ArogyaReddyArogyaReddy/https-github.com-affaan-m-everything-claude-code1/.codex/AGENTS.md

https-github.com-affaan-m-everything-claude-code1

AGENTS.md2 starsChanged 7 months agoMITView on GitHub

This supplements the root AGENTS.md with Codex-specific guidance. Skills are auto-loaded from .agents/skills/. Each skill contains: - SKILL.md — Detailed instructions and workflow - agents/openai.yaml — Codex interface metadata Available skills: - tdd-workflow — Test-driven development with 80%+ coverage - security-review — Comprehensive security checklist - coding-standards — Universal coding standards - frontend-patterns — React/Next.js patterns - frontend-slides — Viewport-safe HTML presentations and PPTX-to-web conversion - article-writing — Long-form writing from notes and voice references - content-engine — Platform-native social…

  • Reads credentials

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

6 rules. About 1 is common, 1 is distinctive, and 4 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.

  • 4

    Very specific

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

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

    Treat the project-local .codex/config.toml as the default Codex baseline for ECC.

    line 47
  2. Very specific:

    Use /agent inside Codex CLI to inspect and steer child agents

    line 70
  3. Distinctive:

    Always validate inputs at system boundaries

    line 92
  4. Common:

    Never hardcode secrets — use environment variables

    line 93
  5. Very specific:

    Run npm audit / pip audit before committing

    line 94
  6. Very specific:

    Use sandbox_mode = "workspace-write" in config

    line 96

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

ECC for Codex CLI

This supplements the root AGENTS.md with Codex-specific guidance.

Model Recommendations

Task TypeRecommended Model
Routine coding, tests, formattingGPT 5.4
Complex features, architectureGPT 5.4
Debugging, refactoringGPT 5.4
Security reviewGPT 5.4

Skills Discovery

Skills are auto-loaded from .agents/skills/. Each skill contains:

  • SKILL.md — Detailed instructions and workflow
  • agents/openai.yaml — Codex interface metadata

Available skills:

  • tdd-workflow — Test-driven development with 80%+ coverage
  • security-review — Comprehensive security checklist
  • coding-standards — Universal coding standards
  • frontend-patterns — React/Next.js patterns
  • frontend-slides — Viewport-safe HTML presentations and PPTX-to-web conversion
  • article-writing — Long-form writing from notes and voice references
  • content-engine — Platform-native social content and repurposing
  • market-research — Source-attributed market and competitor research
  • investor-materials — Decks, memos, models, and one-pagers
  • investor-outreach — Personalized investor outreach and follow-ups
  • backend-patterns — API design, database, caching
  • e2e-testing — Playwright E2E tests
  • eval-harness — Eval-driven development
  • strategic-compact — Context management
  • api-design — REST API design patterns
  • verification-loop — Build, test, lint, typecheck, security
  • deep-research — Multi-source research with firecrawl and exa MCPs
  • exa-search — Neural search via Exa MCP for web, code, and companies
  • claude-api — Anthropic Claude API patterns and SDKs
  • x-api — X/Twitter API integration for posting, threads, and analytics
  • crosspost — Multi-platform content distribution
  • fal-ai-media — AI image/video/audio generation via fal.ai
  • dmux-workflows — Multi-agent orchestration with dmux

MCP Servers

Treat the project-local .codex/config.toml as the default Codex baseline for ECC. The current ECC baseline enables GitHub, Context7, Exa, Memory, Playwright, and Sequential Thinking; add heavier extras in ~/.codex/config.toml only when a task actually needs them.

ECC's canonical Codex section name is [mcp_servers.context7]. The launcher package remains @upstash/context7-mcp; only the TOML section name is normalized for consistency with codex mcp list and the reference config.

Automatic config.toml merging

The sync script (scripts/sync-ecc-to-codex.sh) uses a Node-based TOML parser to safely merge ECC MCP servers into ~/.codex/config.toml:

  • Add-only by default — missing ECC servers are appended; existing servers are never modified or removed.
  • 7 managed servers — Supabase, Playwright, Context7, Exa, GitHub, Memory, Sequential Thinking.
  • Canonical naming — ECC manages Context7 as [mcp_servers.context7]; legacy [mcp_servers.context7-mcp] entries are treated as aliases during updates.
  • Package-manager aware — uses the project's configured package manager (npm/pnpm/yarn/bun) instead of hardcoding pnpm.
  • Drift warnings — if an existing server's config differs from the ECC recommendation, the script logs a warning.
  • --update-mcp — explicitly replaces all ECC-managed servers with the latest recommended config (safely removes subtables like [mcp_servers.supabase.env]).
  • User config is always preserved — custom servers, args, env vars, and credentials outside ECC-managed sections are never touched.

Multi-Agent Support

Codex now supports multi-agent workflows behind the experimental features.multi_agent flag.

  • Enable it in .codex/config.toml with [features] multi_agent = true
  • Define project-local roles under [agents.<name>]
  • Point each role at a TOML layer under .codex/agents/
  • Use /agent inside Codex CLI to inspect and steer child agents

Sample role configs in this repo:

  • .codex/agents/explorer.toml — read-only evidence gathering
  • .codex/agents/reviewer.toml — correctness/security review
  • .codex/agents/docs-researcher.toml — API and release-note verification

Key Differences from Claude Code

FeatureClaude CodeCodex CLI
Hooks8+ event typesNot yet supported
Context fileCLAUDE.md + AGENTS.mdAGENTS.md only
SkillsSkills loaded via plugin.agents/skills/ directory
Commands/slash commandsInstruction-based
AgentsSubagent Task toolMulti-agent via /agent and [agents.<name>] roles
SecurityHook-based enforcementInstruction + sandbox
MCPFull supportSupported via config.toml and codex mcp add

Security Without Hooks

Since Codex lacks hooks, security enforcement is instruction-based:

  1. Always validate inputs at system boundaries
  2. Never hardcode secrets — use environment variables
  3. Run npm audit / pip audit before committing
  4. Review git diff before every push
  5. Use sandbox_mode = "workspace-write" in config

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.

Reviews can't be read right now.

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