What is openspec-ultra-bridge-v2?

A compatibility bridge between OpenSpec, a system for storing long-lived software specifications, and Codex Ultra’s execution workflow. It converts OpenSpec change files into task and work-package records for review, testing, tracking, and delivery.

Use it when a repository contains OpenSpec proposal, design, or task files. It prepares those files for Ultra planning or execution while preserving review, quality checks, and ledger tracking.

It lets teams keep durable specifications and history without losing the execution controls used to dispatch and verify work. It also provides a structured handoff from planning documents to implementation.

openspec-ultra-bridge-v2 — Skill for Codex by keithhegit

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.

Any agent

npx skills add keithhegit/ultra-orchestration --skill openspec-ultra-bridge-v2

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge-v2/github.svg)](https://agentmods.dev/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge-v2)

Your own site

<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge-v2"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge-v2/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge-v2"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge-v2.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 603 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00077	$0.00603
Opus 5	$0.00039	$0.00302
Sonnet 5	$0.00015	$0.00121
Haiku 4.5	$0.00008	$0.00060

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

Security

Grade A, and why

openspec-ultra-bridge-v2 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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/bridge_change.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/openspec-ultra-bridge-v2/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenSpec Ultra Bridge V2

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.

What This Skill Does

Translate:

proposal.md
design.md
tasks.md
optional ultra-bridge.md

into:

TaskManifest
WorkPackage set
bridge notes for review and QA

Bridge Rules

Do not let OpenSpec replace Ultra's execution ledger or review gates.
Prefer one bounded change as the default execution unit.
Use OpenSpec for durable spec memory and archive history.
Use Ultra for dispatch, retries, review, QA, and delivery.
In STRICT_OPENSPEC, do not continue without change scaffold, slice status, JSON-ready planning artifacts, and ledger handoff.

How To Use

Point the bridge at an OpenSpec change directory.
Read the proposal, design, and task assets.
If ultra-bridge.md exists, treat it as the preferred mapping hint.
Normalize the change into a reviewable TaskManifest and WorkPackage set.
Hand off those outputs to ultra-planning or ultra-execution-control.

Required Change Scaffold

For newly opened strict changes, initialize at minimum:

proposal.md
design.md
tasks.md
ultra-bridge.md

Default status:

slice_0_spec_ready when the change is ready for implementation
slice_0_not_opened only for unopened planned changes

Slice Contract

Keep change and slice separate:

OpenSpec change is the durable spec and progress node
Ultra slice is the implementation and verification unit

Every bridge output should name:

change_id
current slice status
next slice
owned paths
review targets
QA targets
blockers for status sync or archive

Script

Use scripts/bridge_change.py to extract and materialize bridge artifacts from a real OpenSpec change directory.

What ships with it

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

10d ago First seen · 87 lines · 77 tokens per session scan A c9ac878e22b4

Subscribe to this mod's changes

openspec-ultra-bridge-v2 is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 603 once invoked, about $0.0004 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.

Building agents Planning agent-skills orchestration-framework spec-coding spec-driven-development

gsd-plan-review-convergence

Cross-AI plan convergence - replan until review concerns are resolved.

open-gsd/gsd-core · 21 tokens

gsd-ns-manage

Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.

open-gsd/gsd-core · 16 tokens

gsd-audit-milestone

Audit milestone completion against original intent before archiving.

open-gsd/gsd-core · 17 tokens

gsd-validate-phase

Retroactively audit and fill Nyquist validation gaps for a completed phase.

open-gsd/gsd-core · 19 tokens

spec-kitty-charter-doctrine

Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…

Priivacy-ai/spec-kitty · 135 tokens

spec-kitty-spdd-reasons

Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…

Priivacy-ai/spec-kitty · 118 tokens

openspec-ultra-bridge-v2