ultra-execution-control

ultra-execution-control is a skill for Codex from keithhegit/ultra-orchestration. It costs 58 tokens per session (322 once invoked), scanned A, original, Apache-2.0.

An execution-control skill for assigning work packages after planning. It tracks dependencies, file ownership, blockers, retries, safety limits, and evidence for each task.

In plain words
What is it for?
Use it to dispatch dependent tasks, serialize work that touches the same files, limit retries, apply cautious write controls, and collect standard completion reports.
Why use it?
It reduces conflicts between simultaneous tasks and prevents incomplete or unsupported work from being marked ready.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Install

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.

agentmods
npx agentmods add skills/keithhegit/ultra-orchestration/ultra-execution-control
Any agent
npx skills add keithhegit/ultra-orchestration --skill ultra-execution-control
Clone the repo
git clone --depth 1 https://github.com/keithhegit/ultra-orchestration

Made for: Codex.

Wrote 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.

agentmods badge for ultra-execution-control

README.md
[![agentmods](https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-execution-control.svg)](https://agentmods.dev/skills/keithhegit/ultra-orchestration/ultra-execution-control)
Your own site
<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/ultra-execution-control"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-execution-control.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 322 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.00322
Opus 5 $0.00029 $0.00161
Sonnet 5 $0.00012 $0.00064
Haiku 4.5 $0.00006 $0.00032

Measured 6d ago against content hash ae377b5ab0db, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

ultra-execution-control 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.

skills-vnext/ultra-execution-control/SKILL.md · 55 lines

What it actually says

Ultra Execution Control

Move work packages through execution without losing safety, ownership, or auditability.

Dispatch Rules

Dispatch a work package only when:

  • dependencies are satisfied
  • acceptance checks are concrete
  • write ownership is explicit
  • the task is not blocked by another active writer

If a task shares owned_paths with another in-flight task, serialize it.

Ledger Rules

The ledger is the system of record. Keep it lightweight and host-driven.

  • the model may propose state updates
  • the host should apply the actual ledger change
  • every blocker should include a short summary, evidence, and next-step ask
  • every retry should increment a bounded counter

Guardrails

Use:

  • careful for risky or destructive commands
  • freeze to limit writes to the declared path boundary
  • guard when both are needed together

Result Contract

Require every child execution unit to return:

  • task_id
  • status
  • summary
  • changed_paths
  • artifacts
  • evidence
  • risks
  • followups

If evidence is missing, do not mark the package review-ready.

Read execution-rules before dispatching.

Files

What ships with it

2 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.

Changes

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.

  1. 6d ago First seen · 55 lines · 58 tokens per session scan A ae377b5ab0db

Subscribe to this mod's changes

ultra-execution-control is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 322 once invoked, about $0.0003 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-31.