openspec-ultra-bridge-v2 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited openspec-ultra-bridge-v2 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
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.
OpenSpec is the specification layer. Ultra remains the control plane.
This skill is a compatibility bridge for vNext users. The default public entry point is now $ultra-orchestrator, which invokes this bridge as needed.
Translate:
proposal.mddesign.mdtasks.mdultra-bridge.mdinto:
TaskManifestWorkPackage setchange as the default execution unit.STRICT_OPENSPEC, do not continue without change scaffold, slice status,JSON-ready planning artifacts, and ledger handoff.
ultra-bridge.md exists, treat it as the preferred mapping hint.TaskManifest and WorkPackageset.
ultra-planning or ultra-execution-control.For newly opened strict changes, initialize at minimum:
proposal.mddesign.mdtasks.mdultra-bridge.mdDefault status:
slice_0_spec_ready when the change is ready for implementationslice_0_not_opened only for unopened planned changesKeep change and slice separate:
change is the durable spec and progress nodeslice is the implementation and verification unitEvery bridge output should name:
change_idUse scripts/bridge_change.py to extract and materialize bridge artifacts from a real OpenSpec change directory.
../ultra-vnext-core/references/contracts.md~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.