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-build-verificationgit 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-build-verification)<a href="https://agentmods.dev/skills/igovet/codex-cortex-orchestrator/worker-build-verification"><img src="https://agentmods.dev/badge/skills/igovet/codex-cortex-orchestrator/worker-build-verification/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-build-verification"><img src="https://agentmods.dev/badge/skills/igovet/codex-cortex-orchestrator/worker-build-verification.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.00025 | $0.02440 |
| Opus 5.5 | $0.00010 | $0.00976 |
| Sonnet 5.5 | $0.00005 | $0.00488 |
| Haiku 4.5 | $0.00003 | $0.00244 |
Grade C, and why
worker-build-verification 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`, How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Verification
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
Independently establish build, test, lint, type, packaging, installation, and release-readiness evidence. This role is read-only: run authorized non-rewriting checks, but never repair failures, edit project files, install unapproved dependencies, or accept another worker's success claim without observation.
When to use this profile
- Select: Independent build, test, packaging, installation, or release-readiness evidence is required.
- Choose another specialist: A failing check must be diagnosed or repaired.
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 · -1 lines 7f8271d30999
- 1mo ago Changed · +8 lines scan A → C c183298c6692
- 1mo ago Changed · +8 lines 30121dd87d73
- 1mo ago Changed e2855d983a6e
- 1mo ago First seen · 218 lines · 25 tokens per session scan A da3ca73d6781
worker-build-verification is a skill published in the GitHub repository igovet/codex-cortex-orchestrator (2 stars, last pushed 29d ago), licensed MIT. It adds 25 tokens to every session and 2,440 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other skills, from other repositories
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.
cicd-pipeline-qe-orchestrator
Orchestrate quality engineering across CI/CD pipeline phases. Use when designing test strategies, planning quality gates, or implementing shift-left/shift-right testing.
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
verification-and-release
Design risk-based verification and judge release readiness from traceable evidence. Use when deciding what must be proven or whether an integrated change can ship.
php-quality-tooling
Use when setting up PHPStan, Rector, or PHP-CS-Fixer on a non-Laravel PHP project, incl. CI wiring. Do NOT use for Laravel (Pint/Larastan), tests, or syntax.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.