vLLM Semantic Router is a programmable routing layer that chooses or combines language models for each request in a system using multiple models and types of computing infrastructure. It helps teams route inference by signals such as user preferences, application policies, quality, cost, latency, privacy, and safety requirements. The catalogue skills and instructions support configuring and operating this model-routing system.
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 skills add vllm-project/semantic-router --skill release-opsgit clone --depth 1 https://github.com/vllm-project/semantic-routerWrote 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/vllm-project/semantic-router/release-ops)<a href="https://agentmods.dev/skills/vllm-project/semantic-router/release-ops"><img src="https://agentmods.dev/badge/skills/vllm-project/semantic-router/release-ops.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.1 | $0.00041 | $0.00599 |
| Opus 5 | $0.00020 | $0.00300 |
| Sonnet 5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
maintainer-release-ops 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 7d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer Release Ops
Trigger
- Use when release planning needs milestone structure, release issue creation, or blocker coordination
- Use when the maintainer asks for milestone health or a release-focused brief
- Use
maintainer-issue-pr-managementfor day-to-day intake, labels, titles, acceptance, and stale-work triage
Required Surfaces
maintainer_ops
Stop Conditions
- GitHub writes are requested but the generated action payload has not been reviewed by the maintainer
- A public issue, PR, or comment body would include private infrastructure details or AI/tool attribution
Workflow
- Read the active release plan and maintainer policy.
- Run
maintainer_board.py syncto refresh local state, orbriefto use the latest snapshot. - Run
release-reportwhen an active release plan exists, then compare plan tasks, milestone issues, and PR blockers before proposing work. - Review accepted milestone work and release blockers.
- Generate proposed actions only; do not mutate GitHub by default.
- Apply actions only after maintainer confirmation.
Must Read
- tools/agent/docs/maintainer-ops.md
- tools/agent/maintainer-policy.yaml
- .prowlabels.yaml
- .github/PULL_REQUEST_TEMPLATE.md
Standard Commands
python3 tools/agent/scripts/maintainer_board.py sync --milestone "<name>"python3 tools/agent/scripts/maintainer_board.py briefpython3 tools/agent/scripts/maintainer_board.py release-report --release-plan tools/agent/docs/plans/RELEASE_PLAN.md --writepython3 tools/agent/scripts/maintainer_board.py create-issues --release-plan tools/agent/docs/plans/RELEASE_PLAN.md --dry-run
Gotchas
- Milestone assignment is a release commitment and requires accepted work; there is no separate candidate state label.
- Close-candidate PRs should get an explicit grace-period comment before close unless the maintainer asks for immediate closure.
- The generated board is local and gitignored; do not link to local board paths from public GitHub artifacts.
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.
- 7d ago First seen · 68 lines · 41 tokens per session scan A 8c09ee2fe72d
maintainer-release-ops is a skill published in the GitHub repository vllm-project/semantic-router (5,600 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 599 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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.