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.
npx skills add KyongSik-Yoon/opsx-omc-bridge --skill deploygit clone --depth 1 https://github.com/KyongSik-Yoon/opsx-omc-bridgeWrote 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.
[](https://agentmods.dev/skills/kyongsik-yoon/opsx-omc-bridge/deploy)<a href="https://agentmods.dev/skills/kyongsik-yoon/opsx-omc-bridge/deploy"><img src="https://agentmods.dev/badge/skills/kyongsik-yoon/opsx-omc-bridge/deploy/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.
<a href="https://agentmods.dev/skills/kyongsik-yoon/opsx-omc-bridge/deploy"><img src="https://agentmods.dev/badge/skills/kyongsik-yoon/opsx-omc-bridge/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00088 | $0.02205 |
| Opus 5 | $0.00044 | $0.01103 |
| Sonnet 5 | $0.00018 | $0.00441 |
| Haiku 4.5 | $0.00009 | $0.00220 |
Grade A, and why
deploy 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.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec → OMC Deploy Bridge
Bridge skill that hands off complex OpenSpec planning artifacts to OMC team or ralph mode. Automatically determines the optimal execution strategy by running a preflight pass, resolving the canonical execution context, and analyzing task structure.
When to use
- tasks.md has 4 or more tasks
- Work is divided into multiple phases
- Changes span multiple domains (frontend + backend, DDL + service + tests, etc.)
- Refactoring requiring iterative verification until completion
Execution flow
Step 1: Identify target change
Scan for active changes, same as quick.
ls -d openspec/changes/*/tasks.md 2>/dev/null | grep -v archive
If multiple changes exist, ask the user to select one.
Step 2: Preflight and validate artifacts
Complex work requires the full artifact set and a clear execution context:
CHANGE_DIR="openspec/changes/<change-name>"
MISSING=""
test -f "$CHANGE_DIR/proposal.md" || MISSING="$MISSING proposal.md"
test -f "$CHANGE_DIR/design.md" || MISSING="$MISSING design.md"
test -f "$CHANGE_DIR/tasks.md" || MISSING="$MISSING tasks.md"
# Check for delta specs
ls "$CHANGE_DIR/specs/" 2>/dev/null | head -1 || MISSING="$MISSING delta-specs"
- If tasks.md or design.md is missing, stop and guide user to run
/opsx:continueor/opsx:ff - If delta specs are missing, warn but proceed (not all changes require deltas)
- If a compacted execution brief exists, treat it as the primary implementation handoff and use the full artifacts as supporting evidence
Preferred compacted brief candidates:
ls "$CHANGE_DIR"/implementation-brief.md \
"$CHANGE_DIR"/brief.md \
"$CHANGE_DIR"/context.md \
"$CHANGE_DIR"/handoff.md 2>/dev/null | head -1
Preflight checklist:
- Resolve the canonical artifact set for the change
- Detect whether a compacted brief is available
- Confirm tasks.md is current and still reflects pending work
- Identify phase boundaries and obvious dependency edges
- Mark phases that are safe to parallelize internally
- Surface any ambiguity before delegating to OMC
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.
- 9d ago First seen · 265 lines · 88 tokens per session scan A 1d305b4e1623
deploy is a skill published in the GitHub repository KyongSik-Yoon/opsx-omc-bridge (4 stars, last pushed 6mo ago), licensed MIT. It adds 88 tokens to every session and 2,205 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…