agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/get-fable/.codex/AGENTS.md

get-fable

AGENTS.md6 starsChanged 3 months agoMITView on GitHub

This supplements root AGENTS.md with Codex-specific execution guidance. .agents/ and .claude/ compatibility files are adapters or legacy surfaces. Do not treat them as independent workflow definitions. Use the repo-local profiles in .codex/config.toml as execution aids: Profiles intentionally inherit the active Codex model instead of hard-coding a model ID. Keep credentials and private MCP configuration in user-owned Codex configuration, not in this repository. Repo MCP entries are development defaults only and are not part of the universal ChatGPT plugin contract.

The file

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

2 rules. About 1 is common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Use the repo-local profiles in .codex/config.toml as execution aids:

    line 16
  2. Common:

    Keep credentials and private MCP configuration in user-owned Codex configuration, not in this repository.

    line 30

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

get-fable for Codex

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

Source of truth

  • Canonical workflow registry: skills/get-fable/registry.json
  • Canonical entry skill: skills/get-fable/SKILL.md
  • Specialist skills: skills/fable-*/SKILL.md
  • Durable runtime state: .fable/state.json when the project is initialized

.agents/ and .claude/ compatibility files are adapters or legacy surfaces. Do not treat them as independent workflow definitions.

Codex agents

Use the repo-local profiles in .codex/config.toml as execution aids:

  • Explorer: evidence gathering for $fable-discover
  • Planner: bounded decomposition for $fable-plan
  • Executor: one accepted card for $fable-execute
  • Verifier: adversarial proof for $fable-verify
  • Recovery: failure attribution for $fable-recover
  • Reviewer: PR correctness and regression review
  • Docs researcher: primary documentation and release verification

Profiles intentionally inherit the active Codex model instead of hard-coding a model ID.

Configuration boundary

Keep credentials and private MCP configuration in user-owned Codex configuration, not in this repository. Repo MCP entries are development defaults only and are not part of the universal ChatGPT plugin contract.

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