How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

linker - Skill - OpenSmartRoute

Name: linker
Author: ContextUnity

Imported from ContextUnity/contextunity-forge-mcp (src/engine/linker/AGENTS.md). Install upstream with npx skills add ContextUnity/contextunity-forge-mcp --skill linker. Copyright stays with the author.

Cross-File Linker (`src/engine/linker/`)

The linker resolves cross-file Reference targets, module imports, callable contracts, and manifest-driven framework edges from the extracted SemanticCatalog and FlowStore without mutating language AST state. Keep resolution phases modular (interner, semantic_context, resolution, contracts, framework_relations) and operate strictly on compact typed sidecars and SymbolId/PathId handles. Do not embed language-specific syntax heuristics that belong in ../languages/ or framework rules that belong in declarative .toml manifests, and do not re-parse source files or mutate Node.details JSON DOMs during linking passes.

Maintain sub-second linking by interning file paths once per file rather than per node and indexing hot lookup tables (by_id, flows, named_bindings, module_exports, component_scopes) directly by SymbolId/PathId without secondary string-to-ID hash lookups in inner loops. Precompute file-level import masks and language dependency contexts before parallel Rayon passes instead of locking shared caches (Mutex/RwLock) or splitting path strings inside per-reference resolution. Allocating temporary String keys for lookup probes, cloning Node or serde_json::Value payloads across phases, or scanning full catalog tables linearly is strictly forbidden.

Install linker and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "contextunity-contextunity-forge-mcp-linker", "kind": "skill", "name": "linker", "description": "The linker resolves cross-file `Reference` targets, module imports, callable contracts, and manifest-driven framework edges from the extracted `SemanticCatalog` and `FlowStore` without mutating language AST state. Keep resolution phases modular (`interner`, `semantic_context`, `resolution`, `contracts`, `framework_relations`) and operate strictly on compact typed sidecars and `SymbolId`/`PathId` handles. Do not embed language-specific syntax heuristics that belong in [`../languages/`](../languages/) or framework rules that belong in declarative `.toml` manifests, and do not re-parse source files or mutate `Node.details` JSON DOMs during linking passes.", "publisher": "ContextUnity", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "The linker resolves cross-file `Reference` targets, module imports, callable contracts, and manifest-driven framework edges from the extracted `SemanticCatalog` and `FlowStore` without mutating language AST state. Keep resolution phases modular (`interner`, `semantic_context`, `resolution`, `contracts`, `framework_relations`) and operate strictly on compact typed sidecars and `SymbolId`/`PathId` handles. Do not embed language-specific syntax heuristics that belong in [`../languages/`](../languages/) or framework rules that belong in declarative `.toml` manifests, and do not re-parse source files or mutate `Node.details` JSON DOMs during linking passes." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/ContextUnity/contextunity-forge-mcp", "path": "src/engine/linker/AGENTS.md", "ref": "f2c5364e7b5532d32794172c14ec38f47a849686", "url": "https://github.com/ContextUnity/contextunity-forge-mcp/blob/f2c5364e7b5532d32794172c14ec38f47a849686/src/engine/linker/AGENTS.md", "key": "ContextUnity/contextunity-forge-mcp/src/engine/linker/AGENTS.md" } }, "instructions": "# Cross-File Linker (`src/engine/linker/`)\n\nThe linker resolves cross-file `Reference` targets, module imports, callable contracts, and manifest-driven framework edges from the extracted `SemanticCatalog` and `FlowStore` without mutating language AST state. Keep resolution phases modular (`interner`, `semantic_context`, `resolution`, `contracts`, `framework_relations`) and operate strictly on compact typed sidecars and `SymbolId`/`PathId` handles. Do not embed language-specific syntax heuristics that belong in [`../languages/`](../languages/) or framework rules that belong in declarative `.tom", "cost": { "context_tokens": 344 } }

linker

About

Cross-File Linker (`src/engine/linker/`)

Use it

Install linker and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews

About

Cross-File Linker (src/engine/linker/)

Use it

Install linker and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews

Cross-File Linker (`src/engine/linker/`)