Borrowing it
Nothing to install: this file belongs to sorryorc/mcp-codex-worker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sorryorc/mcp-codex-worker/main/.claude/skills/worker-debugging-playbook/SKILL.mdgit clone --depth 1 https://github.com/sorryorc/mcp-codex-workerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sorryorc/mcp-codex-worker/worker-debugging-playbook)<a href="https://agentmods.dev/skills/sorryorc/mcp-codex-worker/worker-debugging-playbook"><img src="https://agentmods.dev/badge/skills/sorryorc/mcp-codex-worker/worker-debugging-playbook/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sorryorc/mcp-codex-worker/worker-debugging-playbook"><img src="https://agentmods.dev/badge/skills/sorryorc/mcp-codex-worker/worker-debugging-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00036 | $0.00347 |
| Opus 5.5 | $0.00014 | $0.00139 |
| Sonnet 5.5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
worker-debugging-playbook 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 2mo 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.
What it actually says
Worker Debugging Playbook
Symptom Table
| Symptom | First check | Likely cause | Next action |
|---|---|---|---|
Job not found |
Job TTL and id source | Expired or wrong id | Re-run start, capture id in the caller |
Receipt says missing_artifact |
Receipt bytes and refs | Large output without artifact | Fix tool to save artifact before returning |
scoped_patch violation |
Changed files vs paths | Worker edited outside scope | Narrow prompt and rerun with scoped paths |
| Checks passed but output feels wrong | Episode and semantic risk | Semantic failure | Use strict or critical tier review |
| Repeated revise passes | Reasoning blockers | Stalled repair loop | Escalate model or stop for main review |
Minimal Triage
- Read compact
getoutput first. - If receipt has artifact refs, inspect slices instead of full logs.
- Check
episode.trajectory_scoreand missing gates. - Run the smallest failing check outside the worker if needed.
When Not To Use
Do not use this for planned feature work. Use worker-change-control first.
Verification
npm run codex:audit -- --since-minutes=60npm run stats:gate
Provenance and maintenance
Refresh symptoms with rg -n "Job not found|missing_artifact|scoped_patch|revise" src scripts.
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.
- 2mo ago First seen · 37 lines · 36 tokens per session scan A 7dc8bd32f001
worker-debugging-playbook is a skill published in the GitHub repository sorryorc/mcp-codex-worker (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 347 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…
anti-entropy-governance
Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.
agent-debug-fixer
A Chinese-language debugging and repair workflow for software problems. It investigates errors, failed tests, broken pages, or behavior that does not match expectations, then makes a minimal fix.