CODEX INSTRUCTION WORKFLOW

# Codex instruction workflow

This guide explains how scaldex fits into the workflow for improving Codex instructions.

## The AGENTS problem

Codex instruction files can help, stay neutral or make work more expensive.

An `AGENTS.md` or `AGENTS.override.md` entry file may reduce tool use by telling Codex where to look and when to stop. It can also refer to support files or folders. The measured package may cost tokens if the entry file or support material adds too much context, points Codex at the wrong files or gives rules that do not match the task.

scaldex measures that trade-off. It does not decide whether your instructions are generally good. It checks whether the measured package helps Codex complete controlled task workflows with fewer non-cached input tokens and clean quality gates.

## Roles

- You provide the instruction package to measure.
- scaldex runs paired benchmark tasks and writes evidence.
- Codex can help interpret the evidence or propose instruction changes when you give it the handoff and a clear task.

The measured package lives in `subject/`: