Install command
Provided
Design and validate model routing strategies that reduce cost and latency while preserving output quality.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Not provided
Copy snippet
Provided
Prerequisites
3 to clear
Platforms
6 listed
Difficulty
79/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
3 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens, third-party handling.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
# Trigger
"Apply model routing cost/latency optimizer skill to this workflow."
# Required output
1) Current cost + latency baseline
2) Candidate routing policy (fast/default/high-quality tiers)
3) Quality regression checks and rollback triggers
4) Expected savings and SLO impactThis skill helps teams ship model routing policies that cut spend and latency without quietly degrading quality. It enforces baseline measurement, explicit quality gates, and safe rollback criteria so optimization decisions remain production-safe.
SKILL.md.SKILL.md content as reusable workflow instructions..gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported..cursor/rules/*.mdc adapter for project rules.Apply model routing cost/latency optimizer.
Output:
1) baseline cost/latency table,
2) routing policy with escalation rules,
3) quality guardrails,
4) before/after savings projection.
Issue: Savings improve but user quality drops
Fix: tighten escalation thresholds and reserve stronger models for high-impact tasks.
Issue: Latency improves but cost rises unexpectedly
Fix: inspect token bloat from prompts/context size and cap response/output tokens.
Issue: Routing policy is hard to explain
Fix: keep deterministic rules for first rollout, then add adaptive logic incrementally.
Treat tooling details as time-sensitive. Re-validate APIs, limits, pricing, auth models, and deployment flags immediately before implementation. If docs conflict with prior memory, follow current official docs and release notes.
Show that Model Routing Cost and Latency Optimizer Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/model-routing-cost-latency-optimizer)Model Routing Cost and Latency Optimizer Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
| Field | Design and validate model routing strategies that reduce cost and latency while preserving output quality. Open dossier | Official OpenAI skill that tells agents to use the OpenAI developer documentation MCP server first for API, Codex, Apps SDK, model-selection, and migration questions. Open dossier | Create portable Agent Skills, generate platform adapters, validate package metadata, and prepare PR-first HeyClaude submissions. Open dossier | Build repeatable eval suites that catch quality regressions in AI agent behavior before merge or release. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2026-04-10 | Package not verified | Package verified2026-06-02 | Package verified2026-04-10 |
| Source provenanceDiffers | Source-backed | Source-backed | No submission link | No submission link |
| SubmitterDiffers | — | JSONbored | — | — |
| Install risk | Review first | Review first | Low risk | Low risk |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | |
| Category | skills | skills | skills | skills |
| Source | first-party | source-backed | first-party | first-party |
| Author | JSONbored | OpenAI | JSONbored | JSONbored |
| Added | 2026-04-10 | 2026-06-05 | 2026-04-27 | 2026-04-10 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLIVS Code | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — | — |
| Safety notes | ✓Use this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them. Apply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows. | ✓The skill is read-only guidance; it does not call OpenAI APIs, create API keys, modify accounts, or execute code by itself. Do not use the skill as proof that a model, API parameter, entitlement, or product feature exists; it routes the agent to official docs so the answer can be verified. Keep model upgrade work narrow unless the user explicitly asks for SDK, auth, environment, or provider migration changes. | ✓Downloads and unzips a HeyClaude-maintainer-packaged skill archive into a local folder when using the install command. Produces public skill package and submission drafts; review generated files before opening a PR or sharing them. | ✓This skill produces automated release recommendations (merge, patch, or rollback) from eval scores; treat them as decision support and require human review before gating production releases or running suggested commands. |
| Privacy notes | ✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts. | ✓Documentation queries can reveal what product, API, model, migration, or customer workflow the user is researching. Avoid sending private prompts, customer data, secrets, internal repository names, or unreleased product plans through docs-search queries. Skill text, fetched docs, citations, and agent transcripts can persist in local logs or conversation history depending on the client. | ✓Does not require credentials and should only process public skill requirements, source URLs, and validation notes. Do not include private repository names, customer data, tokens, or unpublished operating details in generated skill packages. | ✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.