codex-preflight
Skill0 starsChanged 4 months agoMITView on GitHub
This skill should be used when the user asks to "run a Codex preflight", "check Codex MCP health", "verify the ChatGPT Codex login", or "test a Codex roundtrip" before relying on Codex in Cowork.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- santiago-afonso/codex-sandbox-preflighttheir own version, first seen Apr 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- santiago-afonso/codex-sandbox-preflight★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- codex-orchestrationSkill
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
- Very specific: line 12
Use the installed codex-preflight MCP server only for a safe readiness check.
- Very specific: line 14
Call preflight_health to establish whether the locally installed Codex executable is available and which existing login mode it will use.
- Very specific: line 16
Call preflight_codex_roundtrip only when the user wants an authenticated readiness test.
- Distinctive: line 22
Treat a failed preflight as an environment issue.
≈ “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.
Files
Codex Preflight
Use the installed codex-preflight MCP server only for a safe readiness check.
- Call
preflight_healthto establish whether the locally installed Codex executable is available and which existing login mode it will use. - Call
preflight_codex_roundtriponly when the user wants an authenticated readiness test. It starts a temporary read-only Codex session and removes its temporary directory after the test. - Report only the returned status and check outcomes. Do not request, set, reveal, or troubleshoot API keys, access tokens, prompts, model output, thread identifiers, or stderr.
- Treat a failed preflight as an environment issue. Do not modify any project file, retry with broader permissions, or switch authentication methods.
The roundtrip is deliberately deterministic: it validates a first session and a same-thread reply that recalls an internal value from the first turn, without retaining that value, the thread identifier, or either response.
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
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.