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 detect-upstream-basegit 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/detect-upstream-base)<a href="https://agentmods.dev/skills/cohere-ai/vllm-skills/detect-upstream-base"><img src="https://agentmods.dev/badge/skills/cohere-ai/vllm-skills/detect-upstream-base/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/detect-upstream-base"><img src="https://agentmods.dev/badge/skills/cohere-ai/vllm-skills/detect-upstream-base.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.00336 |
| Opus 5 | $0.00036 | $0.00168 |
| Sonnet 5 | $0.00014 | $0.00067 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
detect-upstream-base 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 10d 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.
What it actually says
Detect Upstream Base Tag
Determine which upstream vllm tag the current branch is forked from.
Usage
Step 1: Ensure upstream remote
if ! git remote get-url upstream &>/dev/null; then
git remote add upstream [email protected]:vllm-project/vllm.git
fi
git fetch upstream --tags
Step 2: Detect v1
V1_BASE=$(git merge-base HEAD upstream/main)
V1=$(git describe --tags --abbrev=0 --match="v*" "$V1_BASE" 2>/dev/null)
If git describe fails (no reachable tag), fall back to the merge-base SHA:
V1=${V1:-$V1_BASE}
Step 3: Confirm with user
Present to user: "The current upstream base tag appears to be $V1. Is this correct, or would you like to specify a different tag?"
Wait for explicit confirmation before returning the value.
Output
The confirmed value of V1 (an upstream tag like v0.19.1 or a commit SHA).
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.
- 10d ago First seen · 48 lines · 72 tokens per session scan A 94f1d63048e3
detect-upstream-base 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 336 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.