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 shen-shanshan/vllm-dev-skills --skill infx-bench-script-generatorgit clone --depth 1 https://github.com/shen-shanshan/vllm-dev-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/shen-shanshan/vllm-dev-skills/infx-bench-script-generator)<a href="https://agentmods.dev/skills/shen-shanshan/vllm-dev-skills/infx-bench-script-generator"><img src="https://agentmods.dev/badge/skills/shen-shanshan/vllm-dev-skills/infx-bench-script-generator/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/shen-shanshan/vllm-dev-skills/infx-bench-script-generator"><img src="https://agentmods.dev/badge/skills/shen-shanshan/vllm-dev-skills/infx-bench-script-generator.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.00000 | $0.01516 |
| Opus 5.5 | $0.00000 | $0.00606 |
| Sonnet 5.5 | $0.00000 | $0.00303 |
| Haiku 4.5 | $0.00000 | $0.00152 |
Grade A, and why
infx-bench-script-generator 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 27d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
InferenceX 本地 Benchmark 脚本生成器
根据一个 InferenceX srt-slurm 单机 recipe(xxx.yaml)+ 一个 override variant,生成三份在
本地 GPU 服务器上手动跑 AgentX benchmark 的脚本(不依赖 Slurm / srt-slurm / GitHub Actions)。
输入(缺失项向用户确认,路径可留空走默认)
- recipe 路径(如
dsv4/vllm/mi355x-fp4-mtp/agentic.yaml,相对于 InferenceX 仓库的inferencex-e2e/benchmarks/single_node/srt-slurm-recipes/,或绝对路径) - override 名(如
override_tp8_c56、override_dep8_c64;也接受base) - 是否采集 torch profiler trace:
off(默认)/prefill(一个完整 prefill step)/decode(一个完整 decode step) - 模型权重 host 路径(留空 = server 脚本在容器内下载,存 named volume)
- InferenceX 仓库 host 路径(留空 = client 脚本在容器内 clone)
- trace 数据集 host 路径(留空 = 挂载 host
~/.cache/huggingface,复用缓存与 HF token) - 测试结果 host 目录(留空 = named volume 挂到
/logs,即 InferenceX 默认结果位置)
工作流程
-
读 recipe 并自检:读目标 yaml,确认 override 存在;需要 schema/merge 规则细节时读
references/recipe-schema.md(含 dsv4 mi355x 的 worked example)。 -
运行生成器(产物由脚本确定性生成,不要手写这三个文件):
python3 <skill_dir>/scripts/gen_bench_scripts.py \ --recipe <recipe 绝对路径> --override <override 名> \ [--model-path <host 路径>] [--repo-path <host 路径>] \ [--trace-path <host 路径>] [--results-dir <host 路径>] \ [--profile off|prefill|decode] \ --out-root <skill_dir>/outputsPyYAML 缺失时报错,先
python3 -m pip install pyyaml。 -
复核生成产物(
outputs/<recipe路径以_分隔>_<override>/):variant.json/variant.env与三份脚本一致(server args 与roles.agg.args、 client env 与benchmark.env、CONC 与 variant 一致);01_docker_run.sh中没有任何-e环境变量(env 全部在 02/03 脚本内);03_run_client.sh里IS_AGENTIC=1等必须先于source runtime_settings.sh, 功耗开关(ENABLE_AGENTX_POWER=0等)必须在 source 之后。 核对领域细节时读references/server-runbook.md与references/client-runbook.md。
-
汇报:三份脚本的路径、容器名,以及执行顺序:
1. bash outputs/<文件夹>/01_docker_run.sh # host 上起容器 2. docker exec -it <容器名> bash /infx-scripts/02_start_server.sh 3. docker exec -it <容器名> bash /infx-scripts/03_run_client.sh
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/templates/01_docker_run.sh.tmpl 1.0 KB
- assets/templates/02_start_server.sh.tmpl 2.1 KB
- assets/templates/03_run_client.sh.tmpl 2.6 KB
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_dep8_c64/01_docker_run.sh 1.6 KB runs code
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_dep8_c64/02_start_server.sh 4.4 KB runs code
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_dep8_c64/03_run_client.sh 3.2 KB runs code
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_dep8_c64/variant.env 907 B
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_dep8_c64/variant.json 3.6 KB
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_tp8_c56/01_docker_run.sh 1.6 KB runs code
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_tp8_c56/02_start_server.sh 3.3 KB runs code
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_tp8_c56/03_run_client.sh 2.8 KB runs code
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_tp8_c56/variant.env 802 B
- outputs/dsv4_vllm_mi355x-fp4-mtp_agentic_override_tp8_c56/variant.json 3.2 KB
- references/client-runbook.md 4.2 KB
- references/recipe-schema.md 3.3 KB
- references/server-runbook.md 4.2 KB
- scripts/gen_bench_scripts.py 15 KB runs code
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.
- 27d ago First seen · 71 lines · 0 tokens per session scan A 0f7b7fa8cfce
infx-bench-script-generator is a skill published in the GitHub repository shen-shanshan/vllm-dev-skills (22 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,516 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-09-29.
Other skills, from other repositories
moai-ref-secops
DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning, Kubernetes RBAC hardening, container-escape defense, runtime threat detection, OWASP API Top 10 operational defense, WAF…
memstack-deployment-docker-setup
Use this skill when the user says 'Docker', 'Dockerfile', 'docker-compose', 'containerize', 'docker-setup', or needs to containerize an application with optimized Docker images and compose configurations. Do NOT use for serverless or static site deployments.
containerization-assistant
Generate Dockerfiles, Docker Compose configurations, and Kubernetes manifests for containerizing applications. Use when: (1) Creating Dockerfiles for Node.js, Python, Java, Go, or other applications, (2) Setting up multi-service environments with Docker Compose, (3) Generating Kubernetes deployments, services, and…
vibe-service-health-dashboard
Queries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.
supply-chain-attack-recon
External recon for software supply-chain attack surface — package-namespace squatting candidates, dependency-confusion vulnerabilities, GitHub Actions injection openings, container image registry exposure, SBOM mining, internal-package-name leakage, and CI/CD configuration exposure. Reconnaissance and identification…
performing-container-image-hardening
This skill covers hardening container images by minimizing attack surface, removing unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure production-ready images.