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-failure-archaeology/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-failure-archaeology)<a href="https://agentmods.dev/skills/sorryorc/mcp-codex-worker/worker-failure-archaeology"><img src="https://agentmods.dev/badge/skills/sorryorc/mcp-codex-worker/worker-failure-archaeology/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-failure-archaeology"><img src="https://agentmods.dev/badge/skills/sorryorc/mcp-codex-worker/worker-failure-archaeology.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.00033 | $0.00256 |
| Opus 5.5 | $0.00013 | $0.00102 |
| Sonnet 5.5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
worker-failure-archaeology 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 Failure Archaeology
Use this to avoid re-fighting settled battles.
Method
- Start with
git log --oneline -- src scripts README.md. - Search for the exact symptom string.
- Read tests that encode the old failure.
- Preserve the root cause, evidence, rejected fix, and current status in a note or test.
Failure Record Template
| Field | Content |
|---|---|
| Symptom | User-visible failure |
| Root cause | Mechanism, not guess |
| Evidence | Commit, test, metric, or log |
| Rejected paths | Fixes that failed or were too risky |
| Current guard | Test, gate, or doc that prevents recurrence |
When Not To Use
Do not use this for fresh prototype ideas with no production implication. Use worker-research-frontier.
Verification
rg -n "<symptom>" .git log --oneline -- <files>
Provenance and maintenance
Update the record when a guard moves from docs into tests or code.
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 · 39 lines · 33 tokens per session scan A 8e7bee0bd426
worker-failure-archaeology is a skill published in the GitHub repository sorryorc/mcp-codex-worker (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 256 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.