agentleFS
reefbarmanreefbarman/agentlink/.agents/skills/add-codex-model/SKILL.md

add-codex-model

Skill2 starsChanged 18 days agoMITView on GitHub

Checklist for adding, replacing, or retiring a Codex/OpenAI (GPT) model in AgentLink's picker, routing, prompt profiles, condense thresholds, docs, and tests. Use when a new GPT model ships.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Read the official model page (developers.openai.com/api/docs/models/<id>) and the "Using GPT-N" guide: context window, max output, input …

    line 12
  2. Very specific:

    Check whether it's on ChatGPT/Codex sign-in or API key only, and whether Codex's catalog marks it use_responses_lite or gives it different …

    line 13
  3. Distinctive:

    Don't guess. If something isn't published, say so in the final summary.

    line 14
  4. Very specific:

    Only if needed: CODEX_OAUTH_MODEL_OVERRIDES (different sign-in limits or a larger condenseTargetInputTokens), …

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Add a Codex/OpenAI model

Each model's facts and policy live on its CODEX_MODELS entry in packages/core/src/codex/models.ts. Background routing tiers, review preferences, prompt profiles, and the Codex-aligned condense default are all derived from it. Docs and pinned tests stay manual.

1. Get the facts first

  • Read the official model page (developers.openai.com/api/docs/models/<id>) and the "Using GPT-N" guide: context window, max output, input cap, reasoning efforts and default, Fast/Ultrafast support.
  • Check whether it's on ChatGPT/Codex sign-in or API key only, and whether Codex's catalog marks it use_responses_lite or gives it different sign-in limits.
  • Don't guess. If something isn't published, say so in the final summary.

2. packages/core/src/codex/models.ts

  • CODEX_MODELS: add the entry. Required: routingTier (cheap Luna-class, balanced Sol/Terra-class, deep_reasoning Astra-class) and promptProfile (reasoning for Sol/Terra/Astra-class, compatibility for Luna/Spark-class). Set codexAlignedCondense: true if API prompts above 272K cost more. Then limits, efforts, defaultTextVerbosity, serviceTiers, and apiAvailable: false if sign-in only.
  • Array position matters: within a tier, earlier entries win for background routing and reviews. Keep stronger models first (Sols before Terras).
  • CODEX_PICKER_MODEL_IDS: picker position. Update the "last verified" comment on CODEX_CHATGPT_BACKEND_MODEL_IDS.
  • Only if needed: CODEX_OAUTH_MODEL_OVERRIDES (different sign-in limits or a larger condenseTargetInputTokens), CODEX_OAUTH_RESPONSES_LITE_MODELS, and for replacements SUPERSEDED_MODEL_MIGRATIONS and getCodexUnavailableModelFallback.

3. Tests

  • The "official N models" picker lists in packages/core/src/codex/models.test.ts, src/agent/providers/codex/CodexProvider.test.ts, and the count in apps/cli/src/config.test.ts. Add a capability test for the new model.
  • packages/core/src/codex/models.test.ts "Codex routing tiers" if the strongest model in a tier changes.

4. Docs

  • resources/builtin-skills/documentation/references/: capabilities.md (picker list, availability, Speed tiers), settings.md (limits, condense defaults, text verbosity), providers.md (prompt profiles), troubleshooting.md (rollout and Speed lists).
  • CHANGELOG.md under ## Unreleased, then npm run docs:generate.

5. Validate

  • npx oxfmt <touched files>, then npm run lint.
  • Focused tests: npx vitest run packages/core/src/codex packages/core/src/promptProfilePolicy.test.ts src/agent/providers/codex src/agent/backgroundModelRouter.test.ts src/agent/modelCondenseThresholds.test.ts apps/desktop/src/desktopModelCatalog.test.ts apps/cli/src/config.test.ts.

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.