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 agentmods add skills/graycodeai/starling/mdc-vllmnpx skills add GrayCodeAI/starling --skill mdc-vllmgit clone --depth 1 https://github.com/GrayCodeAI/starlingWhat 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 | $0.00030 | $0.02160 |
| Opus 5 | $0.00015 | $0.01080 |
| Sonnet 5 | $0.00006 | $0.00432 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
mdc-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 2d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vLLM Best Practices
vLLM is the gold standard for high-throughput LLM inference. Adhere to these guidelines to maximize performance, ensure reproducibility, and maintain robust LLM services.
1. Environment & Installation
Always use isolated conda environments and pin vLLM to your CUDA version. This prevents binary incompatibilities and ensures reproducible deployments.
❌ BAD:
# Unreliable global install, prone to CUDA/PyTorch mismatches
pip install vllm
✅ GOOD:
# For NVIDIA GPUs (CUDA 12.1 is default, check vLLM docs for current default)
conda create -n vllm_env python=3.10 -y
conda activate vllm_env
pip install vllm==0.5.2 # Pin the exact version in requirements.txt
# For NVIDIA GPUs (CUDA 11.8 specific version, e.g., v0.4.0)
conda create -n vllm_cu118 python=3.10 -y
conda activate vllm_cu118
export VLLM_VERSION=0.4.0
export PYTHON_VERSION=310
pip install https://github.com/vllm-project/vllm/releases/download/v${VLLM_VERSION}/vllm-${VLLM_VERSION}+cu118-cp${PYTHON_VERSION}-cp${PYTHON_VERSION}-manylinux1_x86_64.whl --extra-index-url https://download.pytorch.org/whl/cu118
- Action: Ensure
requirements.txtexplicitly listsvllm==X.Y.Z. - Hardware: Target GPUs with compute capability ≥ 7.0 (V100, A100, H100, etc.).
2. Code Organization & Structure
Separate inference logic from data preprocessing and business logic. Use a modular approach for clarity and testability.
❌ BAD:
# main.py - monolithic script, hard to test or scale
from vllm import LLM, SamplingParams
# ... data loading, preprocessing, model init, inference, postprocessing ...
✅ GOOD:
# llm_service/inference_engine.py
from vllm import LLM, SamplingParams
from typing import List
class InferenceEngine:
def __init__(self, model_path: str, **kwargs):
"""Initializes the vLLM engine with specified model and configurations."""
self.llm = LLM(model=model_path, **kwargs)
self.sampling_params = SamplingParams(temperature=0.7, top_p=0.95, max_tokens=256)
def generate(self, prompts: List[str]) -> List[str]:
"""Generates responses for a list of prompts using configured sampling parameters."""
outputs = self.llm.generate(prompts, self.sampling_params)
return [output.outputs[0].text for output in outputs]
# llm_service/main.py (or API endpoint, e.g., with FastAPI)
from .inference_engine import InferenceEngine
from typing import Dict
def serve_llm_request(request_data: Dict) -> Dict:
"""Handles an incoming LLM request, orchestrating preprocessing, inference, and postprocessing."""
# 1. Preprocessing (e.g., validate input, format prompt from request_data)
prompts = [request_data["text"]] # Simplified example
# 2. Inference
# Model path and parallelism should be loaded from config, not hardcoded here
engine = InferenceEngine(model_path="mistralai/Mistral-7B-Instruct-v0.2",
tensor_parallel_size=2) # Explicitly configure parallelism
results = engine.generate(prompts)
# 3. Postprocessing (e.g., format output for API response, add metadata)
return {"generated_text": results[0]}
- Action: Define
LLMengine parameters explicitly (e.g.,tensor_parallel_sizefor distributed inference).
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.
- 2d ago First seen · 196 lines · 30 tokens per session scan A 67eed9657446
mdc-vllm is a skill published in the GitHub repository GrayCodeAI/starling (2 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 2,160 once invoked, about $0.0002 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
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
security-review
Review trust boundaries, auth/authz, injection, secrets, filesystem/network exposure, dependencies, and exploitability without pretending a shallow lint is an audit.