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.
git 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/rules/cohere-ai/vllm-skills/skill-edit-checklist)<a href="https://agentmods.dev/rules/cohere-ai/vllm-skills/skill-edit-checklist"><img src="https://agentmods.dev/badge/rules/cohere-ai/vllm-skills/skill-edit-checklist.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.00316 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
skill-edit-checklist 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 8d 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
Skill Edit Checklist
Before and after modifying any skill, read the skills overview README.md
(at skills/README.md in the vllm-skills source repo, or
.cursor/skills/README.md after installation) and follow the Change Impact
table:
| If you change… | Also review… |
|---|---|
| install-vllm | local-test-runner (env setup steps) |
| local-test-runner | rebase-assistant (Step 3 b1 gate, Step 6 b2 verification) |
| detect-upstream-base | rebase-assistant (Step 1 v1 detection), auto-rebase (Step 1) |
| rebase-assistant | auto-rebase (Step 4 rebase invocation, Step 5 summary fields) |
| auto-rebase | (no downstream dependents) |
Required Steps
- Read the skills
README.mdto see the full dependency graph. - Propagate any interface changes (parameter names, step numbering, output format) to all downstream skills listed in the table above.
- Update the README itself if you add, remove, or rename a skill, change the dependency graph, or alter shared notation.
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.
- 8d ago First seen · 29 lines · 0 tokens per session scan A 8efe60c785df
skill-edit-checklist is a cursor rule published in the GitHub repository cohere-ai/vllm-skills (6 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 316 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.