Router Service Platform Change
Developmentrouter-service-platform-changeRouter Service Platform Change is an Agent Skill for development published in the vllm-project/semantic-router repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Modifies router-side API, authz, memory, provider, storage, or runtime service modules outside config, decision, selection, and extproc plugin chains. Use when changing apiserver endpoints, authz or rate-limit policy code, memory or response storage flows, provider adapters, or other router service-platform modules.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vllm-project/semantic-router/blob/HEAD/tools/agent/skills/router-service-platform-change/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/router-service-platform-change, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Router Service Platform Change
Trigger
- Change router-side API, service, storage, provider, or support modules outside config, decision, selection, and extproc plugin chains
- Change apiserver, authz, rate-limit, memory, response API, storage, or provider-adapter behavior
Workflow
- Read change surfaces and module boundaries for the affected service layer
- Modify the router-side service or API seam and identify whether profile-owned behavior changed
- Run
make agent-report ENV=cpu CHANGED_FILES="..."to verify surface alignment - Run
make agent-ci-gate CHANGED_FILES="..."to validate the affected constraints - Update any impacted local or CI E2E expectation when the changed module is profile-owned
Gotchas
- These modules are not generic fallback territory anymore; if the change is in this surface, keep the service contract explicit instead of hand-waving it as cross-stack glue.
- Storage, authz, and API seams often look local in code but still change E2E behavior through response-api, memory, or authz-rbac profiles.
Must Read
Standard Commands
make agent-report ENV=cpu CHANGED_FILES="..."make agent-ci-gate CHANGED_FILES="..."make agent-feature-gate ENV=cpu CHANGED_FILES="..."
Acceptance
- Router-side service modules, API seams, and affected validation paths stay aligned
- Profile-owned behavior changes update the relevant local or CI E2E expectation