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 cohere-ai/vllm-skills --skill rebase-assistantgit clone --depth 1 https://github.com/cohere-ai/vllm-skillsWrote 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/cohere-ai/vllm-skills/rebase-assistant)<a href="https://agentmods.dev/skills/cohere-ai/vllm-skills/rebase-assistant"><img src="https://agentmods.dev/badge/skills/cohere-ai/vllm-skills/rebase-assistant/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cohere-ai/vllm-skills/rebase-assistant"><img src="https://agentmods.dev/badge/skills/cohere-ai/vllm-skills/rebase-assistant.svg" alt="Reviewed on agentmods" width="80" 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.00072 | $0.02764 |
| Opus 5 | $0.00036 | $0.01382 |
| Sonnet 5 | $0.00014 | $0.00553 |
| Haiku 4.5 | $0.00007 | $0.00276 |
Grade A, and why
rebase-assistant 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 12d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebase Assistant
Rebase this repository's custom fork commits onto a newer upstream vllm tag in a safe, repeatable way.
Notation used throughout this document:
- v1 — the upstream tag the branch is currently based on
- v2 — the target upstream tag to rebase onto
- b1 — the branch before rebase (custom commits on top of v1)
- b2 — the branch after rebase (custom commits replayed onto v2)
Wheel rule: when running checks via local-test-runner, always use the
stable release wheel matching the base tag of the branch being tested — v1
wheel for b1, v2 wheel for b2. Skip the local-test-runner wheel prompt and
go straight to "Switch to stable release" with the matching version, unless the
user explicitly requested a different wheel.
Step 1: Collect Inputs
Gather the following from the user before proceeding.
Auto-detected or user-provided
- Current base tag (v1): Either provided directly by the user, or
auto-detected via the
detect-upstream-baseskill. See detect-upstream-base. If the user supplies v1 explicitly, skip detection and validate:git rev-parse "upstream/$V1" 2>/dev/null \ || git rev-parse "$V1" 2>/dev/null \ || echo "ERROR: tag $V1 not found"
Required
-
Target upstream tag (v2): The upstream tag to rebase onto (e.g.
v0.20.0). Validate it exists:git rev-parse "upstream/$V2" 2>/dev/null \ || git rev-parse "$V2" 2>/dev/null \ || echo "ERROR: tag $V2 not found" -
Verification checks: One or more commands to run after rebase to confirm correctness. Examples:
- Test command:
.venv/bin/python -m pytest tests/path/to/test.py -v - Lint command:
pre-commit run --all-files - Metric threshold: "WER < 15% on transcription tests"
Store these verbatim — they are run as-is during verification.
- Test command:
Optional
- Reference commit: A known-good commit where the checks pass. Used to
diff against when debugging failures after rebase.
If not provided,git rev-parse --verify <reference-commit> 2>/dev/nullHEADon b1 is used as the implicit reference. Either way, Step 3 verifies the checks pass on the reference state before rebasing.
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.
- 12d ago First seen · 295 lines · 72 tokens per session scan A 371e97b874ac
rebase-assistant is a skill published in the GitHub repository cohere-ai/vllm-skills (6 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 2,764 once invoked, about $0.0004 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-31.
Other skills, from other repositories
marimo-pair
Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
release
Evaluate readiness and publish to crates.io.
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
release-kotlin-library
Use when preparing, publishing, or checking readiness for a new Kotlin library version in a repository using gradle-maven-publish-plugin, including release changelog reconciliation, API snapshots, and publication verification.