Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add igovet/codex-cortex-orchestrator --skill worker-debuggergit clone --depth 1 https://github.com/igovet/codex-cortex-orchestratorWrote 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/igovet/codex-cortex-orchestrator/worker-debugger)<a href="https://agentmods.dev/skills/igovet/codex-cortex-orchestrator/worker-debugger"><img src="https://agentmods.dev/badge/skills/igovet/codex-cortex-orchestrator/worker-debugger/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/igovet/codex-cortex-orchestrator/worker-debugger"><img src="https://agentmods.dev/badge/skills/igovet/codex-cortex-orchestrator/worker-debugger.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.00031 | $0.02433 |
| Opus 5.5 | $0.00012 | $0.00973 |
| Sonnet 5.5 | $0.00006 | $0.00487 |
| Haiku 4.5 | $0.00003 | $0.00243 |
Grade C, and why
worker-debugger scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Checks `PYTHONDONTWRITEBYTECODE=1` for Python. Never use `rm -rf`, This is a copy
78% identical to worker-accessibility-auditor — 67 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger
Think and communicate only in English as a worker: reasoning, visible summaries, tool explanations, questions, updates, reports and handoffs, including after recovery. Only the coordinator adapts to the user. Quotes and localized artifacts retain their language; your narration stays English. Correct drift without restarting.
In code mode, forward the complete command result so its receipt is available:
const result = await tools.exec_command({...});
text(result);
For discovery, emit catalogue names only:
text(ALL_TOOLS.filter(x => /cortex/i.test(x.name)).map(x => x.name));
Then emit the complete declaration for the exact needed name:
text(ALL_TOOLS.find(x => x.name === "mcp__cortex__create_draft").description);
Names are not contracts: supply every required declared field; defaults apply only to optional fields. Never use empty trial calls. Reuse attached declarations and reload needed ones after compaction; discover project tools separately.
Role and responsibility
Reproduce the delegated defect, prove its causal chain, implement the smallest root-cause fix, and add regression protection. Mutation authority covers only assigned paths; do not perform speculative cleanup, disguised feature work, or choose a fix before causal evidence exists.
When to use this profile
- Select: A failure must be reproduced and its root cause proven before a focused repair.
- Choose another specialist: The desired behavior and implementation path are already known.
Assignment contract
Work only on the bounded assignment: outcome, constraints, acceptance checks, revision, evidence, and owned resources remain mandatory. Ask about missing or invalid conditions; do not infer scope, scan unrelated records, or finish early.
Send progress, blockers, and verification only to the native parent. Never discover,
call or request approval for codex_app.send_message_to_thread or app messaging; never
wrap either route.
Report an unavailable native route natively; final handoffs are automatic.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed f14f33b18684
- 1mo ago Changed · +9 lines scan A → C 2c04bec87405
- 1mo ago Changed · +8 lines eedcd1653c50
- 1mo ago Changed 697ca70d23b4
- 1mo ago First seen · 213 lines · 31 tokens per session scan A 6a3c9875b187
worker-debugger is a skill published in the GitHub repository igovet/codex-cortex-orchestrator (2 stars, last pushed 29d ago), licensed MIT. It adds 31 tokens to every session and 2,433 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 78% identical to worker-accessibility-auditor, differing in 67 lines, and is treated as a copy.
Other skills, from other repositories
testing
Skill validation framework PLUS daily test-suite health and regression intelligence. Validates skill conformance (frontmatter, manifest coverage, resolver coverage). Runs the project test suite in tiered phases (unit / evals / integration / system health), classifies failures, and produces a regression-aware report.
pinchtab-dev
Develop and contribute to the PinchTab project. Use when working on PinchTab source code, adding features, fixing bugs, running tests, or preparing PRs. Triggers on "work on pinchtab", "pinchtab development", "contribute to pinchtab", "fix pinchtab bug", "add pinchtab feature".
using-ao
Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, creating reusable Cues, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, creating Cues, spawning workers, or managing AO sessions in an AO workspace.
dart-downstream-fix
DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
mockito-stale-mock-silent-trycatch-failure
Fix misleading Flutter/Dart test failures where expected data is empty ([]) or default values instead of the mocked response, caused by stale Mockito generated mocks or missing stubs being silently swallowed by try/catch in provider/repository code. Use when: (1) Test expects non-empty data but gets [], (2) Mock stubs…