Ultra Execution Control
Dispatch and execution control for Codex Ultra vNext. Use after planning when work packages must be assigned, retries bounded, blockers surfaced, and write-lock safety enforced through DAG readiness, owned-path checks, careful or freeze guardrails, and host-driven ledger updates.
Install
$ agentstack add skill-keithhegit-ultra-orchestration-ultra-execution-control ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-keithhegit-ultra-orchestration-ultra-execution-control) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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:
carefulfor risky or destructive commandsfreezeto limit writes to the declared path boundaryguardwhen both are needed together
Result Contract
Require every child execution unit to return:
task_idstatussummarychanged_pathsartifactsevidencerisksfollowups
If evidence is missing, do not mark the package review-ready.
Read [execution-rules](references/execution-rules.md) before dispatching.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: keithhegit
- Source: keithhegit/ultra-orchestration
- License: Apache-2.0
- Homepage: https://keithhegit.github.io/ultra-orchestration/docs.html
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.