Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/nvidia-nemo/switchyard/switchyard-testing-cinpx skills add NVIDIA-NeMo/Switchyard --skill switchyard-testing-cigit clone --depth 1 https://github.com/NVIDIA-NeMo/SwitchyardWhat 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 | $0.00049 | $0.00672 |
| Opus 5 | $0.00024 | $0.00336 |
| Sonnet 5 | $0.00010 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
switchyard-testing-ci 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Switchyard Testing And CI
Read .github/workflows/ci.yml before claiming local CI equivalence. Select tests from the current
diff and symbol references rather than a static subsystem inventory.
Validation Matrix
| Change | Minimum trustworthy validation |
|---|---|
| Markdown or skill Markdown only | Parse skill frontmatter when applicable; git diff --check |
| Python implementation | Focused pytest, uv run ruff check ., uv run mypy switchyard |
| Broad Python or public API | Hermetic full pytest plus lint and mypy |
| One Rust crate | cargo fmt --all --check, workspace clippy, focused crate tests |
| Shared Rust/API/FFI | Rust workspace tests plus affected Python tests |
| Packaging, extras, top-level imports | The slim-install smoke commands from the current CI workflow |
| Live provider behavior | Focused integration test only after explicit authorization |
Standard Gates
Python pre-PR gate:
uv run ruff check .
uv run mypy switchyard
env -u OPENROUTER_API_KEY -u NVIDIA_API_KEY -u OPENAI_API_KEY \
-u ANTHROPIC_API_KEY uv run pytest tests/ -v -m "not integration"
Rust workspace gate:
cargo fmt --all --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
Use -o addopts= when the repository's pytest defaults would stop failure collection too early.
Run focused tests first, then broaden only when the changed contract or shared ownership warrants it.
Live Tests
Integration tests can spend money, require credentials, and contact real services. Never run them
as an automatic pre-PR step. Provision NVIDIA_API_KEY through the environment or a secret manager
before running the user-authorized path, and state which provider was called:
uv run pytest tests/e2e/<focused_test>.py \
-v -m integration -o addopts=
Skill Validation
Each retained skill must have YAML frontmatter with name and description:
uv run python - <<'PY'
from pathlib import Path
import yaml
for path in Path(".agents/skills").glob("*/SKILL.md"):
parts = path.read_text().split("---", 2)
data = yaml.safe_load(parts[1]) if len(parts) == 3 else None
if not isinstance(data, dict) or not data.get("name") or not data.get("description"):
raise SystemExit(f"{path}: missing name or description")
print("skill frontmatter is valid")
PY
git diff --check
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.
- 2d ago First seen · 81 lines · 49 tokens per session scan A 0f31639b1ec7
switchyard-testing-ci is a skill published in the GitHub repository NVIDIA-NeMo/Switchyard (2,650 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 672 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.