Menú
Codex usage and autonomy insight from ContextDevKit receipts, without reading unstable private transcript formats.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Domain Engineering diagnostic — shows what the classifier decides for an objective (CMIS/DAS/profile/skills/mode). Observation-only; never mutates or blocks.
Business-driven methodology entry point — classify (intake), create/advance an Operation or Business work context, and drive the intake → operation → nested-workflow flow. Host-neutral; dry-run by default.
Workflow Navigator — shows the current phase, deliverables, and next commands for an ADR-0057 workflow. Read-only; never mutates state.
Start a focused session on one objective — locks scope, blocks opportunistic refactors.
Deterministic QA gate (ADR-0055) — run the project suite; green + complete acceptance criteria ⇒ qa-approve testing cards into conclusion; red ⇒ report (and qa-reject only attributable failures).
L6 — autonomous feature pipeline. Drives the full squad: design → implement → review → test → log. Checkpoints can be manual or automatic.
| name | source-command-token-report |
| description | Codex usage and autonomy insight from ContextDevKit receipts, without reading unstable private transcript formats. |
Use this skill when the user asks to run the migrated source command token-report.
Codex does not expose a stable transcript format for project tooling. Do not
scrape private .codex session files or invent token totals.
Use the canonical Session Autonomy Receipts produced by ContextDevKit:
node contextkit/tools/scripts/autonomy-report.mjs --latest
node contextkit/tools/scripts/autonomy-report.mjs --all
node contextkit/tools/scripts/autonomy-report.mjs --session <id> --verify
Report the receipt's consumption mode, measured/estimated claim type, observed or estimated tokens, autonomy multiplier, cost evidence, confidence, and integrity status. When no receipt exists, say that usage evidence is unavailable and recommend finalizing the current session first. Never present an estimate as provider-billed usage.
Also inspect economy surfaces that do not require scraping Codex transcripts:
node contextkit/tools/scripts/token-report.mjs --json
node contextkit/tools/scripts/economics/quota-snapshot.mjs --write --source token-report --capture-method manual <quota flags>
Use the JSON report for routing telemetry/economics, economy lifecycle events,
and quota summaries when they exist. If quota data is not visible from the host,
report quota-snapshot skipped: no host quota data; do not invent quota
numbers.