Switchyard is a model-routing library and proxy that chooses which language model should handle each LLM request, based on factors such as cost and task suitability. It is for developers running LLM applications who want to route calls through existing gateways, custom harnesses, or a standalone proxy while retaining OpenAI and Anthropic client compatibility. The catalogue add-ons are workflows for operating or integrating Switchyard with coding agents and gateways.
Borrowing it
Nothing to install: this file belongs to NVIDIA-NeMo/Switchyard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NVIDIA-NeMo/Switchyard/main/.agents/skills/switchyard-docs/SKILL.mdgit clone --depth 1 https://github.com/NVIDIA-NeMo/SwitchyardWrote 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/nvidia-nemo/switchyard/switchyard-docs)<a href="https://agentmods.dev/skills/nvidia-nemo/switchyard/switchyard-docs"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/switchyard/switchyard-docs/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/nvidia-nemo/switchyard/switchyard-docs"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/switchyard/switchyard-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00410 |
| Opus 5.5 | $0.00019 | $0.00164 |
| Sonnet 5.5 | $0.00010 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
switchyard-docs 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 1mo 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.
What it actually says
Switchyard Documentation
The published site is the subset of docs/ selected by mkdocs.yml. Strict MkDocs warnings fail
CI, so fix warnings rather than weakening validation.
Source Of Truth
| Concern | File |
|---|---|
| Navigation, exclusions, theme | mkdocs.yml |
| Source-link rewriting | mkdocs_hooks.py |
| Local commands | docs/Makefile |
| Build, preview, deployment | .github/workflows/docs.yml |
| Documentation dependencies | pyproject.toml docs group |
Workflow
- Decide whether a new page is public. Public pages go in
nav; internal notes go inexclude_docs. - Match the surrounding file naming and documentation style.
- Use relative links. For repository files outside
docs/, use paths relative to the Markdown file and letmkdocs_hooks.pyproduce the source URL. - Verify public examples use supported public imports and current CLI syntax.
- Run the strict build:
cd docs
make publish
CI Constraints
- Keep the docs workflow path-filtered.
- Keep default permissions read-only and grant write access only to deployment jobs.
- Keep PR previews limited to same-repository pull requests.
- Do not use
pull_request_targetto run untrusted documentation code with write permissions. - Build once and pass the
site/artifact to preview and deployment jobs. - Preserve
keep_files: trueso a main deployment does not remove PR previews.
Common strict-build fixes are direct: add or remove a missing nav entry, repair the relative link, or explicitly exclude an internal page. Do not disable strict mode.
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.
- 1mo ago First seen · 47 lines · 48 tokens per session scan A 9e7e77db9859
switchyard-docs is a skill published in the GitHub repository NVIDIA-NeMo/Switchyard (3,459 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 410 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…