Codex debugging
Codex debugging: codex-rs core/tui/exec/cli/app-server/config.From its SKILL.md
npx -y skills add mouadja02/skills --skill codex-debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 323 tokens by cl100k_base, as published. Nobody here has run it
Codex Debugging
Attribution: Sourced from steipete/agent-scripts by Peter Steinberger.
When to Use
- Debugging Codex CLI/app behavior, config parsing, or tool invocations
- Navigating the codex-rs codebase (core/tui/exec/cli/app-server)
Use when investigating Codex CLI/app behavior, config parsing, tool behavior, prompts, MCP/app wiring, or runtime bugs.
Source First
Prefer local source before web/docs:
cd ~/Projects/codex
sed -n '1,220p' codex-rs/AGENTS.md
Then search targeted areas:
rg "<symbol|setting|error|feature>" codex-rs/{core,tui,exec,cli,app-server,app-server-protocol,config}
Workflow
- Identify whether the behavior is CLI, TUI, app server, protocol, config, or exec/tooling.
- Read the owning module and adjacent tests before proposing changes.
- Check local config in
~/.codex/config.tomlonly after understanding the source contract. - Prefer small repros or focused tests over broad speculation.
Notes
- For OpenAI API/product docs, use the official-docs path only when source is insufficient.
- For local browser automation in CLI, use
$browser-use; the bundled Browser plugin is Codex app-only.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.