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.

changes - Skill - OpenSmartRoute

Name: changes
Author: forgegod

Imported from forgegod/talaria-of-mercury (docs/changes/AGENTS.md). Install upstream with npx skills add forgegod/talaria-of-mercury --skill changes. Copyright stays with the author.

Change records

Purpose

Own repository-tracked implementation progress for requested changes without becoming a second source of current product behaviour.

Ownership

Path	Owns
`README.md`	Change lifecycle, status vocabulary, required metadata, and authoring template.
`active/CHG-*.md`	The single implementation-progress authority for an active material change.
`archive/CHG-*.md`	Completed or cancelled implementation receipts; never current-behaviour authority.
`reviews/CHG-<number>/`	Optional CHG-owned review assets and design notes, retained at a stable path after closure.

Local Contracts

Tickets request change; a CHG record owns its repository implementation status, phases, verification gates, and evidence.
Every CHG names its external request, affected CAP IDs, baseline, and executable phase gates.
Only planned, in-progress, or blocked records belong in active/; only done or cancelled records belong in archive/.
Both directories contain only flat CHG record files. Review packages belong in reviews/CHG-<number>/ with a review-only README linked from the owning CHG; see README.md for labeling, retention, and removal rules.
Review Markdown is link-checked but never parsed as a CHG. Packages are not a second progress authority and cannot replace CAP wireframes.
A CHG is complete only after affected CAPs and tests describe the merged behaviour. Archive it rather than using it to describe the repository.
The optional externally installed phase-workflow skills operate on the CHG phase table; they do not create a second mutable progress authority. Skill source and distribution are owned by the dedicated skills repository, not this tree.

Work Guidance

Create one CHG for a material change before implementation begins. Keep it small enough for a coherent vertical slice; use explicit dependencies when splitting is necessary.
Update phase state and evidence only after the corresponding gate passes.
Do not duplicate ticket discussion, capability prose, or ADR rationale in a CHG. Link the authoritative artifact.
Use phased-plan-overview to select active work, phased-plan-execution for one phase, and phased-plan-refactoring only for a verified split or resequencing.
Read README.md before creating, splitting, completing, or archiving a CHG.
Before visual work, read the product DOX and wireframe child if present. Include canonical generation/rendering and review-package retention in the relevant phase and closeout gates.

Verification

Run node scripts/check-product-records.mjs and the CHG phase gate.

Child DOX Index

No child DOX documents. Parent contract: ../AGENTS.md; current product behaviour: ../product/AGENTS.md.

Install changes 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": "forgegod-talaria-of-mercury-changes", "kind": "skill", "name": "changes", "description": "Own repository-tracked implementation progress for requested changes without becoming a second source of current product behaviour.", "publisher": "forgegod", "version": "1.0.0", "capabilities": { "domains": [ "coding", "data_analysis" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Own repository-tracked implementation progress for requested changes without becoming a second source of current product behaviour." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/forgegod/talaria-of-mercury", "path": "docs/changes/AGENTS.md", "ref": "8b640c8bf8303da2a122f58009f9822680cf7f7b", "url": "https://github.com/forgegod/talaria-of-mercury/blob/8b640c8bf8303da2a122f58009f9822680cf7f7b/docs/changes/AGENTS.md", "key": "forgegod/talaria-of-mercury/docs/changes/AGENTS.md" } }, "instructions": "# Change records\n\n## Purpose\n\nOwn repository-tracked implementation progress for requested changes without becoming a second source of current product behaviour.\n\n## Ownership\n\n| Path | Owns |\n| ------------------ | ---------------------------------------------------------------------------------- |\n| `README.md` | Change lifecycle, status vocabulary, required metadata, and authoring template. |\n| `active/CHG-*.md` | The single implementation-progress authority for an active material change. ", "cost": { "context_tokens": 746 } }

changes

About

Change records

Purpose

Ownership

Local Contracts

Work Guidance

Verification

Child DOX Index

Install changes 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

Use it

Manifest

Reviews