dx-codex-identity

Establishes Codex CLI agent identity for session directory naming and artifact generation.

3|5|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/DEEPX-AI/dx_stream --skill dx-codex-identity-deepx-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dx-codex-identity
Source: https://github.com/DEEPX-AI/dx_stream/tree/main/.codex/skills/dx-codex-identity
Command: npx skills add https://github.com/DEEPX-AI/dx_stream --skill dx-codex-identity-deepx-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running as OpenAI Codex CLI within the DEEPX Agent-Driven Development framework, session directories and artifacts must follow a strict naming convention that identifies the agent, coding model, and target model. This Skill ensures the agent always uses the correct 'codex' identifier and never confuses the coding model with the target inference model. ## Core Features & Use Cases - Agent Identity Enforcement: Mandates 'codex' as the agent identifier in all session directory names, preventing misuse of identifiers like 'copilot', 'cursor', or 'claude'. - Session ID Generation: Provides a timestamped naming pattern (YYYYMMDD-HHMMSS_codex_<coding_model><target_model><task>) for consistent artifact organization. - Knowledge Base Navigation: Documents the .deepx/ directory structure containing agent definitions, skills, memory, and toolset references. - Use Case: When compiling a YOLO26n model, the agent creates a session directory like '20260513-100000_codex_gpt53codex_yolo26n_compile' instead of using an incorrect agent name. ## Quick Start Activate this skill and create a new session directory for compiling the yolo26n model using the codex agent identifier.

Frequently Asked Questions about dx-codex-identity

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

FAQPage Schema
How do I name a session directory in the DEEPX framework?▼

Use the pattern YYYYMMDD-HHMMSS_codex_<coding_model>_<target_model>_<task>, for example 20260513-100000_codex_gpt53codex_yolo26n_compile. The agent identifier must always be 'codex' when running as Codex CLI.

What agent identifier should Codex CLI use for artifacts?▼

Codex CLI must always use 'codex' as the agent identifier in session directory names. Never use 'copilot', 'cursor', 'claude', or 'opencode', as those refer to other supported agents in the framework.

What is the difference between coding model and target model?▼

The coding model is the AI model running the agent, such as gpt-5.3-codex shortened to gpt53codex. The target model is the user's inference model being compiled or deployed, such as yolo26n or plantseg.

Where is the DEEPX knowledge base located?▼

The knowledge base lives in the .deepx/ directory at each project level, containing agents/, skills/, memory/, and toolsets/ subdirectories. Read a skill with 'cat .deepx/skills/<skill-name>/SKILL.md'.

Which shell tools are available in Codex CLI sessions?▼

Standard tools like bash, python3, find, grep, cat, and sed are available. Note that ripgrep (rg) may not be installed, so use 'grep -r' as a fallback for recursive searches.