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 agentmods add skills/100yenadmin/fable-token-saving-skills-orchestrator/codex-dispatchnpx skills add 100yenadmin/fable-token-saving-skills-orchestrator --skill codex-dispatchgit clone --depth 1 https://github.com/100yenadmin/fable-token-saving-skills-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/100yenadmin/fable-token-saving-skills-orchestrator/codex-dispatch)<a href="https://agentmods.dev/skills/100yenadmin/fable-token-saving-skills-orchestrator/codex-dispatch"><img src="https://agentmods.dev/badge/skills/100yenadmin/fable-token-saving-skills-orchestrator/codex-dispatch.svg" alt="Measured on agentmods" 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.00024 | $0.00587 |
| Opus 5 | $0.00012 | $0.00293 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
codex-dispatch 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Dispatch
Premium tokens buy judgment. Codex or side-worker capacity buys implementation volume when the task is well specified.
Dispatch When
- the task is self-contained
- the spec carries enough context
- acceptance criteria are explicit
- the work can happen on a side branch or bounded file set
- Fable can review the result instead of typing it
Keep With Fable Or A Higher Local Lane When
- the task is architecture, product strategy, or final judgment
- the implementation depends on local-only tools the side worker lacks
- the acceptance criteria are unclear
- the task requires private credentials or live user action
Dispatch Packet
Include:
- objective
- repo/path/branch
- files or areas involved
- constraints and non-goals
- pseudocode for hard parts
- exact validation command or CI gate
- proof boundary
- expected final report shape
Mechanics
Some lanes are reachable through a CLI rather than a workflow model parameter. When a background shell launches a side worker, close stdin explicitly if the tool expects EOF. For Codex CLI, use:
codex exec --cd <worktree> "<prompt>" < /dev/null
Without the redirected stdin, some background shells can leave the worker waiting at startup instead of doing work.
Skill Availability
Side workers do not automatically see every local Claude skill. Port skills on demand when a dispatch needs them; do not mirror an entire skill library by default.
Example:
ln -sfn "$HOME/.claude/skills/<skill>" "$HOME/.codex/skills/<skill>"
Name the required skill in the dispatch packet and keep the accepted output bounded. If the side worker lacks a required skill and the work is not self-contained, keep the task with Fable or a local lane.
Review Rule
If the diff or report is large, ask a fast worker for a bounded digest first. Fable reads the digest and flagged hunks, not the whole raw output.
Attribution And Adjacent Tools
This dispatch pattern is inspired in part by blader/arbitrage, which focuses on premium-model judgment plus Codex implementation. Claude Code users who want a slash-command bridge to Codex review and delegation workflows can also look at openai/codex-plugin-cc.
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.
- 6d ago First seen · 84 lines · 24 tokens per session scan A 2b48ebec4c8d
codex-dispatch is a skill published in the GitHub repository 100yenadmin/fable-token-saving-skills-orchestrator (101 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 587 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…