Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/commands/datathings/marketplace/update_vllm)<a href="https://agentmods.dev/commands/datathings/marketplace/update_vllm"><img src="https://agentmods.dev/badge/commands/datathings/marketplace/update_vllm.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.00000 | $0.01427 |
| Opus 5 | $0.00000 | $0.00714 |
| Sonnet 5 | $0.00000 | $0.00285 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
update_vllm 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 6d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update vLLM Skill to Latest Version
This command updates the vLLM library to the latest version and synchronizes all skill files with the updated API.
Working directory: plugins/vllm/
Repository Structure
plugins/vllm/
├── skills/vllm/ # Skill content (SKILL.md and references/)
├── vllm/ # Upstream repo clone (NOT a submodule)
└── .claude-plugin/plugin.json # Plugin manifest
The vllm/ directory is a standalone git clone from [email protected]:vllm-project/vllm.git - updated independently via git fetch and git checkout <tag>.
Process
1. Update Library to Latest Tag
cd plugins/vllm/vllm
git fetch --tags
CURRENT_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "unknown")
echo "Current tag: $CURRENT_TAG"
# Stable releases use v#.#.# format (exclude RC tags)
LATEST_TAG=$(git tag --sort=-version:refname | grep "^v" | grep -v "rc\|alpha\|beta" | head -n 1)
echo "Latest tag: $LATEST_TAG"
if [ "$CURRENT_TAG" != "unknown" ] && [ "$CURRENT_TAG" != "$LATEST_TAG" ]; then
echo "Commits between $CURRENT_TAG and $LATEST_TAG:"
git log --oneline "$CURRENT_TAG..$LATEST_TAG" | head -n 50
echo -e "\nAPI-related commits:"
git log --oneline "$CURRENT_TAG..$LATEST_TAG" --grep="API\|deprecat\|LLM\|SamplingParams\|LoRA\|multimodal" -i
fi
git checkout "$LATEST_TAG"
echo "Now on: $(git describe --tags)"
cd ../../..
- Latest tags: https://github.com/vllm-project/vllm/tags
- Stable release tags use format:
v#.#.#(e.g.,v0.16.0,v0.15.1)
2–6. Analyze API Changes & Update Documentation (subagent)
Dispatch a general-purpose subagent via the Task tool for analysis and documentation rewrite. This keeps the large source content out of the main context.
Provide the subagent with:
- Path to source-of-truth files:
plugins/vllm/vllm/vllm/__init__.py— public exportsplugins/vllm/vllm/vllm/entrypoints/llm.py—LLMclassplugins/vllm/vllm/vllm/sampling_params.py—SamplingParams,StructuredOutputsParamsplugins/vllm/vllm/vllm/outputs.py— output typesplugins/vllm/vllm/vllm/lora/request.py—LoRARequestplugins/vllm/vllm/vllm/entrypoints/openai/— server entrypoints and REST API
- Path to skill references:
plugins/vllm/skills/vllm/references/ - Old tag and new tag (from Step 1 output)
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.
- 6d ago First seen · 125 lines · 0 tokens per session scan A 19eac7dd8615
update_vllm is a command published in the GitHub repository datathings/marketplace (11 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,427 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.