ultra-vnext-core — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ultra-vnext-core (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill as a compatibility alias for the mainline $ultra-orchestrator protocol. The user should not need to list every subskill.
Prefer the same behavior as the new main entry point:
$ultra-orchestrator <task description>$ultra-vnext-core <task description> remains valid for existing users and pilot runs.
Classify the run before planning or execution:
LIGHTreview-only, QA-only, explanation-only, or user-explicit lightweight work
STANDARDuser-explicit fast orchestration with bounded risk and no full control plane
STRICTdevelopment work where OpenSpec is unavailable but ledger and JSON contracts are still required
STRICT_OPENSPECdefault for development work, bug fixes, multi-file implementation, pilots, full orchestration tests, OpenSpec work, slice DAG work, and control-plane validation
Development tasks must prefer STRICT_OPENSPEC. If that mode is impossible, explain why and downgrade explicitly. Markdown-only artifacts are not enough for STRICT or STRICT_OPENSPEC.
When invoked:
run_modeSTRICT_OPENSPEC appliesSTRICT and STRICT_OPENSPECDo not ask the user to manually name every subskill.
For STRICT and STRICT_OPENSPEC, the run must use:
scripts/new_run.py to initialize a run directoryledger.json as the execution state recordTaskManifestWorkPackageAgentResultscripts/validate_contracts.py for core artifact validationcontrol_surface_usedIf a required script or artifact cannot be used, stop with a blocker instead of silently downgrading to markdown-only orchestration.
When STRICT_OPENSPEC applies and no existing change is available, create or request this scaffold:
openspec/changes/<change-id>/proposal.md
openspec/changes/<change-id>/design.md
openspec/changes/<change-id>/tasks.md
openspec/changes/<change-id>/ultra-bridge.mdKeep change and slice separate:
change is the specification and progress ledger unitslice is the implementation, verification, and commit unitUse this slice status vocabulary:
slice_0_not_openedslice_0_spec_readyslice_1_completedslice_2_in_progressslice_3_qa_pendingslice_4_doneDefault phases:
Intake -> Plan -> Dispatch -> Execute -> Review -> QA -> Deliver -> Retro
Required loopbacks:
Review -> Execute when the plan is valid but the work is wrongQA -> Execute when behavior is wrong but architecture is still validQA -> Plan when the failure exposes a planning or requirement flawEvery delivery must include:
final_deliverableorchestration_logvetter_reportcontrol_surface_usedcontrol_surface_used must state run_mode, OpenSpec use, bridge use, ledger use, contract validation use, slice DAG use, dynamic QA use, and skipped control surfaces with reasons.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.