codex-first

Route implementation tasks to Codex CLI via temporary file prompts.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Khang5687/agent-scripts --skill codex-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-first
Source: https://github.com/Khang5687/agent-scripts/tree/main/skills/codex-first
Command: npx skills add https://github.com/Khang5687/agent-scripts --skill codex-first

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codex-cli, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the delegation of implementation work to Codex CLI, reducing the need for Claude's expensive tokens while still capitalizing on Claude's strengths in design, spec-writing, and review.

Core Features & Use Cases

  • Codex for Implementation: Automate tasks like code refactoring, bug fixes, and CI script updates.
  • Claude for Design & Review: Leverage Claude's expertise for design, API development, and thorough code reviews.
  • Mixed Task Routing: Efficiently decide between Codex and Claude based on the nature of the task, optimizing resource allocation.

Quick Start

Execute the 'codex-first' skill with a temporary file to define your task, specifying the goal, repository paths, and any constraints or non-goals.

Frequently Asked Questions about codex-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route code implementation tasks to Codex CLI while using Claude for design review?

You can route code implementation tasks to Codex CLI by using a skill that delegates refactoring and bug fixes, reserving Claude's tokens for design judgment, spec-writing, and thorough code reviews. This mixed task routing optimizes resource allocation efficiently.

What is the best way to reduce Claude token usage during code refactoring and bug fixes?

The best way to reduce Claude token usage for code refactoring and bug fixes is to delegate the implementation work to Codex CLI. This approach capitalizes on Codex for execution while saving Claude's expensive tokens for design and review tasks.

Do I need Codex CLI integration to automate CI script updates and code generation?

Yes, you need Codex CLI integration to automate CI script updates and code generation. The skill requires this integration to route implementation tasks effectively, using temporary file prompts to define your specific goals, repository paths, and constraints.

How do I define tasks for Codex CLI using temporary file prompts?

To define tasks for Codex CLI, execute the skill with a temporary file that specifies the implementation goal, repository paths, and any constraints or non-goals. This temporary file prompt structure ensures Codex receives clear directions for code generation.

When should I use Codex CLI for implementation instead of Claude?

You should use Codex CLI for implementation tasks like code refactoring, bug fixes, and CI script updates, whereas Claude should be used for design, API development, and thorough code reviews. This separation optimizes resource allocation based on task nature.

Can I update CI scripts automatically by routing implementation work to Codex CLI?

Yes, you can update CI scripts automatically by routing implementation work to Codex CLI. The skill streamlines the delegation of these implementation tasks, allowing Codex to handle the execution while Claude focuses on design and review.