agentmods.dev

openspec-ultra-bridge

openspec-ultra-bridge is a skill for Codex from keithhegit/ultra-orchestration. It costs 67 tokens per session (1,317 once invoked), scanned A, original, Apache-2.0.

A translator between OpenSpec documents and a controlled engineering workflow. OpenSpec is a change-based way to record a proposal, design, and task list before implementation.

In plain words
What is it for?
Use it when a project has OpenSpec proposal.md, design.md, or tasks.md files and needs to run the change through the Ultra-Orchestrator process.
Why use it?
It lets a repository keep its specification history while turning those documents into tracked execution work with review, testing, and risk checks.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: $skill-name invocation.

not rated 6repo 4mo ago A scan 67 tokens original Apache-2.0

Good fit Use it when a project has OpenSpec proposal.md, design.md, or tasks.md files and needs to run the change through the Ultra-Orchestrator process.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/keithhegit/ultra-orchestration/openspec-ultra-bridge
View source ↗ keithhegit/ultra-orchestration keithhegit.github.io
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
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 openspec-ultra-bridge

README.md
[![agentmods](https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge/github.svg)](https://agentmods.dev/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge)
Your own site
<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge/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.

agentmods 80×15 button for openspec-ultra-bridge

Your own site · 80×15
<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/openspec-ultra-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,317 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.01317
Opus 5 $0.00034 $0.00659
Sonnet 5 $0.00013 $0.00263
Haiku 4.5 $0.00007 $0.00132

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

Security

Grade A, and why

openspec-ultra-bridge 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 9d 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/openspec-ultra-bridge/SKILL.md · 193 lines

How it starts

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

OpenSpec Ultra Bridge

Treat OpenSpec as the spec source-of-truth and Ultra-Orchestrator as the execution control plane.

This bridge is part of the mainline strict control plane. It is normally invoked by $ultra-orchestrator; users should not need to call it manually.

Priority

Absorb OpenSpec advantages without weakening the existing Ultra-Orchestrator architecture.

Prioritize these four advantages first:

  1. Persistent spec assets
  2. Change-based workflow
  3. Archive discipline
  4. Spec-first task decomposition input

Do not let this bridge replace Ultra's state machine, review, QA, risk vetter, safety guard, or execution ledger ownership.

Purpose

Use this skill to translate between:

  • OpenSpec change artifacts
  • Ultra-Orchestrator execution artifacts

The bridge must not replace OpenSpec. It must map OpenSpec artifacts into Ultra execution objects and map Ultra review and QA feedback back into OpenSpec update suggestions.

Inputs

Expect one or more of these OpenSpec artifacts:

  • proposal.md
  • design.md
  • tasks.md
  • spec delta artifacts
  • change metadata such as change-id

Optionally consume these Ultra-side artifacts:

  • TaskManifest
  • WorkPackage
  • AgentResult
  • RunOutput
  • ExecutionLedger summary

Produce

Generate these Ultra-side artifacts when possible:

  • TaskManifest
  • WorkPackage
  • change-id <-> task-id mapping notes
  • archive gate readiness notes

Generate these OpenSpec-side feedback outputs when possible:

  • task refinement suggestions
  • design update suggestions
  • failure-context updates
  • archive blocking reasons

Mapping rules

  • Map change-id to TaskManifest.id.
  • Map proposal summary to goal.
  • Map design constraints to constraints.
  • Map OpenSpec task dependencies to dependencies.
  • Map task acceptance criteria or spec delta checks to success_criteria and acceptance_checks.
  • Map affected components or files to owned_paths.

Orchestration rules

  • Preserve OpenSpec as the spec source-of-truth.
  • Preserve Ultra-Orchestrator as the orchestration source-of-truth.
  • Do not rewrite OpenSpec artifacts into Ultra-native storage unless the user explicitly asks for that migration.
  • Prefer artifact-driven handoff over conversation-history handoff.
  • Treat archive as gated by Ultra review, QA, and risk decisions.
  • Use OpenSpec as a higher-quality frontend for planning, not as a replacement for dispatch, review, or QA.

Read the full file on GitHub · 193 lines

Files

What ships with it

6 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. 9d ago First seen · 193 lines · 67 tokens per session scan A 147fb6f5289f

Subscribe to this mod's changes

openspec-ultra-bridge is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,317 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.

Building agentsPlanningagent-skillsorchestration-frameworkspec-codingspec-driven-development
Related

Other skills, from other repositories

gsd-plan-review-convergence

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

open-gsd/gsd-core · 21 tokens

gsd-audit-milestone

Audit milestone completion against original intent before archiving.

open-gsd/gsd-core · 17 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-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