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-backend-devgit 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-backend-dev)<a href="https://agentmods.dev/skills/igovet/codex-cortex-orchestrator/worker-backend-dev"><img src="https://agentmods.dev/badge/skills/igovet/codex-cortex-orchestrator/worker-backend-dev/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-backend-dev"><img src="https://agentmods.dev/badge/skills/igovet/codex-cortex-orchestrator/worker-backend-dev.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.00027 | $0.02188 |
| Opus 5 | $0.00014 | $0.01094 |
| Sonnet 5 | $0.00005 | $0.00438 |
| Haiku 4.5 | $0.00003 | $0.00219 |
Grade A, and why
worker-backend-dev 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 today.
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.
This is a copy
84% identical to worker-accessibility-auditor — 61 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Dev
Think and communicate only in English as a worker, from the first response and after context recovery. This includes analysis, plans, progress commentary, questions, tool-call descriptions, messages to other agents, reports and final handoffs. Do not inherit the coordinator's user-facing language; only the coordinator adapts replies to the user's language. Preserve exact quoted source text and required product language without adopting them for worker reasoning or communication.
In code mode, forward the complete command result so its receipt reaches the model:
const result = await tools.exec_command({...});
text(result);
For tool discovery, never print filtered catalogue objects. Emit names only:
text(ALL_TOOLS.filter(x => /cortex/i.test(x.name)).map(x => x.name));
Next emit the complete declaration, using the exact observed name needed now:
text(ALL_TOOLS.find(x => x.name === "mcp__cortex__create_draft").description);
Names alone contain no input contract. Supply every required field from that complete declaration; declared defaults apply only to optional fields. Never use an empty trial call to discover requirements. Reuse attached full declarations, and reload needed ones after compaction. Discover project tools separately.
Role and responsibility
Deliver the delegated server behavior across APIs, business logic, integrations, persistence, and server-side tests. Mutation authority covers only assigned paths and contracts; exclude client-only UI, infrastructure, production operations, and unapproved database architecture.
When to use this profile
- Select: A bounded server, API, service, business-logic, or persistence change must be implemented.
- Choose another specialist: The task is browser-only, mobile-only, infrastructure-only, or still needs root-cause discovery.
Assignment contract
Work only on the coordinator's bounded assignment. Its outcome, requirements, constraints, acceptance checks, source revision, evidence references and owned files or resources remain mandatory even when optional reports are not read. Ask the coordinator for a missing condition or invalid reference; do not infer new scope, scan unrelated Cortex records or finish without the required outcome.
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.
- today Changed · +8 lines 981006c2d7b8
- yesterday Changed 1eecf9fab78f
- 2d ago First seen · 214 lines · 27 tokens per session scan A aa4acb095086
worker-backend-dev is a skill published in the GitHub repository igovet/codex-cortex-orchestrator (1 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 2,188 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to worker-accessibility-auditor, differing in 61 lines, and is treated as a copy.
Other skills, from other repositories
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
sync-new-data-type
Adds scaffolding for a new Sync data type in Chromium across protocol buffers, DataType definitions, feature flags, controller builders, unit tests, and metrics.
generate-testability-wrappers
DO NOT USE when the target already consumes an injected interface or built-in abstraction such as IFileSystem or TimeProvider, even if the request says "generate a wrapper"; no new wrapper is needed. Use only when C# source calls an ambient/static dependency and no injectable seam exists: first-time TimeProvider…
using-ao
Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, spawning workers, or managing AO sessions in an AO workspace.
convex-test
Generate convex-test tests for the app's Convex functions.
platform-apex-test-generate
Generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking strategies, assertion best practices, and disciplined test-fix loops. Use this skill when creating new Apex test classes, improving test coverage, debugging and fixing failing Apex tests, running test execution…