← ClaudeAtlas

codex-trimlisted

Use when a user wants to trim Codex CLI's startup context, injected instructions, tools, apps, or skill listings by interactively choosing unused configuration and measuring before/after. Not for Claude Code, conversation compaction, or historical cost analysis.
Rhovian/niles · ★ 4 · AI & Automation · score 70
Install: claude install-skill Rhovian/niles
# Codex trim ## 1. Establish scope and dependencies Require the operator to specify global, project, or local before choosing a write target. Global is `$CODEX_HOME/config.toml` (normally `~/.codex/config.toml`); project is trusted `.codex/config.toml`. Inspect effective layers, trust, managed requirements, launch overrides, and profile before proposing changes. Inventory can proceed while scope is pending. Explain who shares the target: global reaches sessions using that config directory across projects; project settings also affect other sessions in that tree on reload or relaunch, including Niles workers. For local scope, discover whether the CLI supports private project configuration. Otherwise explain supported invocation overrides and agree how the operator will launch them; do not silently write project/global config or invent an ignored config filename. If persistence is wanted, agree a supported mechanism and its actual scope first. Discover supported controls, profiles, and feature inspection commands from `codex --help` and the official [configuration reference](https://developers.openai.com/codex/config-reference/). Confirm that documented controls are supported by the installed CLI; reject unsupported settings rather than assuming that a parsed TOML key is effective. Ask which workflows must survive; preserve their execution/file tools, required instructions, skills, and integrations. Under Niles or another orchestrator, preserve shell access and injected `d