dispatching-exact-ocx-models

Injects and verifies exact OCX model routes when dispatching Agent or Workflow workers.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Codeseys-Labs/agentic-sdlc --skill dispatching-exact-ocx-models-codeseys-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatching-exact-ocx-models
Source: https://github.com/Codeseys-Labs/agentic-sdlc/tree/main/plugin/skills/dispatching-exact-ocx-models
Command: npx skills add https://github.com/Codeseys-Labs/agentic-sdlc --skill dispatching-exact-ocx-models-codeseys-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a conductor has already chosen an exact OCX model route, dispatching it incorrectly is easy: generated agent types ignore placeholder model arguments, namespaced provider IDs can silently fall through to the default provider and get billed to the wrong upstream, and a healthy response is not proof the requested model actually ran. This Skill enforces a verify-then-admit discipline so no unverified dispatch enters the production handoff. ## Core Features & Use Cases - Exact route injection: Selects the correct injection surface for generated ocx-* agent types, Workflow agent() calls, and namespaced provider IDs, refusing placeholder or prompt-prose model claims. - Pre-dispatch catalog verification: Checks a namespaced ID's provider prefix against the live gateway catalog (ccodex models) before dispatch, since the gateway fails open onto the default provider rather than failing closed. - Post-run identity verification: Correlates requests with gateway attribution (ocx observe logs --jsonl) via requestId, treating routeKind: "default-provider" as an alarm and refusing to accept unverified receipts. - Use Case: A conductor resolves muse/muse-spark-1.2-contributor for a worker. Before spawning, the Skill confirms the muse prefix is live in the gateway catalog, dispatches with the exact ID and effort, then reads attribution to confirm the observed provider and model match the assignment. ## Quick Start Load the model-tier-rightsizing skill first to resolve an exact route, then ask the agent to dispatch that resolved assignment to a worker and verify the run against gateway attribution before accepting the result.

Frequently Asked Questions about dispatching-exact-ocx-models

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I dispatch an exact model to an agent worker without it being silently substituted?

Inject the exact model ID and effort through the real injection surface: the generated agent type's pinned route or the Workflow agent() call's model argument, never prompt prose. Then verify identity from gateway attribution, not from the request or response label.

How do I verify which model actually ran on the opencodex gateway?

Read the attribution stream with `ocx observe logs --jsonl` and correlate by requestId. The resolvedModel, provider, and routeDecision.routeKind fields carry identity; a prompt echo or response-body model label is not proof of the route.

Why does a request with an unknown provider prefix not fail on the OCX gateway?

The gateway router computes the prefix, finds no matching provider, and forwards the model string to the default provider instead of failing closed. The request is billed to the wrong upstream, so check the prefix against the live catalog before dispatching.

Does this skill choose which model tier to use for a task?

No. Tier selection belongs to the model-tier-rightsizing skill, which must run first and produce a resolved RuntimeAssignment. This skill only consumes that resolved route and makes it dispatchable with verification.

What happens when the dispatched model identity cannot be verified?

The result is discarded and the dispatch stops, or the assignment's predeclared fallback is used. No result may enter the production handoff without a verified receipt; the skill returns a refusal or SeedProposal naming the missing capability.