Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/rachittshah/cc-codex/codexgit clone --depth 1 https://github.com/rachittshah/cc-codexWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00016 | $0.00745 |
| Opus 5 | $0.00008 | $0.00373 |
| Sonnet 5 | $0.00003 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
codex scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Custom Codex Task
Your task
You are receiving a request to execute a custom Codex task. Determine which Codex tool is most appropriate and execute it.
Available Codex Tools
- codex_reason: Deep reasoning, trade-off analysis, decision-making
- codex_plan: Implementation planning, project roadmaps
- codex_spec: Technical specifications, documentation
- codex_analyze: Code/architecture analysis, security/performance review
- codex_compare: Compare multiple options/technologies
Steps
-
Analyze Request: Determine which Codex tool matches the request
- Keywords like "plan" → codex_plan
- Keywords like "should we" → codex_reason
- Keywords like "specification" → codex_spec
- Keywords like "analyze" → codex_analyze
- Keywords like "compare" → codex_compare
-
Execute Codex Tool: Call the appropriate tool with proper parameters
-
Present Results: Format and present the Codex output clearly
-
Follow Up: Suggest next steps based on the output
Example Usage
User: "/codex compare Redis vs Memcached for our caching layer"
Expected flow:
- Detect: This is a comparison task
- Call codex_compare with options ["Redis", "Memcached"]
- Receive structured comparison
- Present formatted comparison
- Ask: "Based on this comparison, shall we proceed with [recommendation]?"
Task Type Detection
"plan" | "roadmap" | "timeline" | "phases"
→ codex_plan
"should we" | "which is better" | "decide" | "reason"
→ codex_reason
"spec" | "specification" | "document" | "requirements"
→ codex_spec
"analyze" | "review" | "audit" | "examine"
→ codex_analyze
"compare" | "versus" | "vs" | "which one"
→ codex_compare
Notes
- This is a meta-command that routes to specific Codex tools
- All Codex tools use gpt-5 with high reasoning effort
- Results are stored in shared session context
- Can chain multiple Codex calls if needed
Example Scenarios
Scenario 1: Architecture Decision
User: /codex should we use microservices or monolith?
→ Use codex_reason
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 115 lines · 16 tokens per session scan A c58c41487a52
codex is a command published in the GitHub repository rachittshah/cc-codex (11 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 745 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.