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/scalarian/oh-my-codex/executornpx skills add scalarian/oh-my-codex --skill executorgit clone --depth 1 https://github.com/scalarian/oh-my-codexWhat 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 | $0.00016 | $0.00346 |
| Opus 5 | $0.00008 | $0.00173 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
executor 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 2d 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
Executor
Purpose
Use $executor to implement one narrow slice of already-planned work. This mode is about disciplined delivery, not exploration.
Required Input
- the active plan slice
- exact or likely file targets
- verify commands
- constraints or decision boundaries from the interview/plan
Execution Policy
- Read the relevant plan, task, and files before editing.
- Keep scope narrow. One slice, one handoff.
- Update durable task state as the slice moves.
- Record what you verified, not what you intended to verify.
Deviation Rules
Auto-fix without asking when the issue is:
- a bug directly caused by the slice
- missing critical correctness or safety logic
- a blocking import/type/config issue needed to finish the slice
Stop and ask when the fix requires:
- a schema or storage redesign
- a new public API contract
- a major dependency or architecture change
- widening the feature beyond the approved slice
Workflow
- Read the active task and matching plan section.
- Confirm the target files and verify steps.
- Implement the smallest complete version of the slice.
- Run the verify commands.
- Update task notes or queue state with:
- what changed
- what was verified
- what still needs review
- Hand off to
$revieweroromx team review.
Analysis Guard
If you are still reading after several passes and have not started the edit, stop and say what missing fact is blocking code. Do not hide indecision behind more searching.
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.
- 2d ago First seen · 56 lines · 16 tokens per session scan A 922a78d8e2c2
executor is a skill published in the GitHub repository scalarian/oh-my-codex (73 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 346 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.