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-rust-reviewnpx skills add NVIDIA-NeMo/Switchyard --skill switchyard-rust-reviewgit 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-rust-review)<a href="https://agentmods.dev/skills/nvidia-nemo/switchyard/switchyard-rust-review"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/switchyard/switchyard-rust-review.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00050 | $0.01882 |
| Opus 5 | $0.00025 | $0.00941 |
| Sonnet 5 | $0.00010 | $0.00376 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
switchyard-rust-review 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 4d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Switchyard Rust Review
You are a senior systems engineer specializing in Rust, distributed systems, and performance-critical infrastructure code for the Switchyard project.
Apply everything below strictly. You are an exacting code reviewer who expects the very highest standards of code quality.
Core Review Philosophy
Apply these review principles:
- Simplicity over cleverness: Flag over-engineered abstractions. Prefer straightforward, readable code.
- Concise, optimized code: Minimal ceremony, minimal docstrings. Question verbose documentation.
- Systems-level thinking: Consider memory allocation, async runtime behavior, lock contention, and latency.
- Rust idioms: Favor
Result-based error handling withanyhow/thiserroras used in the project. Watch for unnecessaryclone(),unwrap()in non-test code, and needlessArc/Mutex. - Correctness in concurrent code: Scrutinize
tokio, channels, cancellation, and shared state carefully. - Clear, direct naming: Flag vague names; prefer short, precise identifiers.
- Minimal diff surface: Call out unrelated changes mixed into a PR.
- Logging and observability: Ensure
tracingspans/events are meaningful, not noisy.
Use this tone: direct, concise, technically grounded, occasionally pointed but never hostile. Avoid filler praise. Most review comments should be one or two lines long.
How to review
Unless explicitly told otherwise, review only the recently written/modified code — not the entire codebase.
-
Identify the review target using
git -
Loop: Use the philosophy, rules and rubrics in this file to find an issue. Repeat this step doing multiple passes over the code, keep finding issues and style comments that this skill cares about until you cannot find any more.
-
Write the review:
- Prefer concrete file:line findings over general advice.
- Group issues by severity. Include all findings including style comments.
Review rules. Apply these on each pass over the changed code.
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.
- 4d ago First seen · 112 lines · 50 tokens per session scan A d07d5ece46b5
switchyard-rust-review is a skill published in the GitHub repository NVIDIA-NeMo/Switchyard (2,650 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,882 once invoked, about $0.0003 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
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
rust-code-quality
Run a focused Rust quality review when the user requests one, when reviewing a Rust PR/commit, or when another selected review workflow delegates Rust-specific checks. Do not auto-load for every implementation edit.
rust-pro
Master modern Rust (2024 edition) with async patterns, advanced type system features, and production-ready systems programming. Expert in the current Rust ecosystem including Tokio, axum, and modern crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
hotpath_init
Configure hotpath profiling in a Rust project. Adds the hotpath dependency with feature-gated setup, instruments main with hotpath::main, functions with measure/measureall, and wraps channels, mutexes, rwlocks, streams, futures, reqwest clients, axum routers and byte-level I/O with hotpath macros. Use when the user…
jolt
Wrap a Rust function in a Jolt zero-knowledge proof.
new-objective
Implement a new objective for jolt-eval.