SGLang is a framework for running inference for large language models and multimodal models, meaning it processes inputs to produce model outputs such as text or other media. It is used to serve and accelerate open AI models and related workloads.
Borrowing it
Nothing to install: this file belongs to sgl-project/sglang. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sgl-project/sglang/main/.agents/skills/ci-test-audit/SKILL.mdgit clone --depth 1 https://github.com/sgl-project/sglangWrote 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/sgl-project/sglang/ci-test-audit)<a href="https://agentmods.dev/skills/sgl-project/sglang/ci-test-audit"><img src="https://agentmods.dev/badge/skills/sgl-project/sglang/ci-test-audit/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/sgl-project/sglang/ci-test-audit"><img src="https://agentmods.dev/badge/skills/sgl-project/sglang/ci-test-audit.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.00064 | $0.00488 |
| Opus 5.5 | $0.00026 | $0.00195 |
| Sonnet 5.5 | $0.00013 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
ci-test-audit 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 1mo 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
CI / Test Audit
Audits what is already in test/, .github/ and scripts/ci/. For writing a new test see
write-sglang-test; for how the pipeline dispatches and
gates work see ci-workflow-guide.
How to use it
Read action-items.md first. It is a catalog of patterns that have been applied to this repo, each with a way to spot it and example PRs. The catalog is the substance of this skill; everything below is only scaffolding.
The user says what to audit -- a test group, a stage, a workflow file, or a complaint like "this suite is slow" -- and how thoroughly. Read that scope and decide which patterns apply.
An audit is only useful if it is specific. "This suite could be trimmed" is not a
finding; "TestFooLargePage is a strict subset of TestFooRetractLargePage, drop it"
is. Every finding needs the file, the pattern it matches, and what to do.
Reporting
Group findings by confidence in the claim, not by pattern id. Lead with the ones where the evidence is in the file you just read; keep the speculative ones separate and say what you would need to check. Skip anything you are not reasonably sure about -- a long list of maybes costs more to triage than it saves.
Propose, do not apply. Deleting a test, moving a registration to another stage, and changing a threshold are all decisions for the user. Land them as separate changes, since a trim and a threshold change fail for different reasons.
Keeping the catalog current
Example PRs age. When a pattern shows up in newer work, or a new pattern recurs, update
action-items.md: the pattern text should stay general, the examples are
replaceable evidence.
What ships with it
1 file 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.
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.
- 1mo ago First seen · 41 lines · 64 tokens per session scan A 4e9141cbd740
ci-test-audit is a skill published in the GitHub repository sgl-project/sglang (38,324 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 488 once invoked, about $0.0003 per session on Opus 5.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-09-19.
Other skills, from other repositories
ci-speedup
Speeds up CI and the merge path: finds where changes wait between push and deploy, then fixes the critical path, check placement, merge queue or post-merge checks with auto-revert, flaky tests, and deploy rate. Use when "CI is slow", "speed up CI", "do we need a merge queue", "main keeps going red", "flaky tests block…
e2e-testing-expert
Expert guide for End-to-End (E2E) testing with Playwright 1.50+, Clock API, ARIA snapshots, test fixtures, and Vitest 3+ / Panduan ahli pengujian E2E dengan Playwright 1.50+, Clock API, ARIA snapshots, dan Vitest 3+.
audit-harness
Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.
knowledge-engineering-quality-and-delivery
A project-wide quality and delivery workflow covering tests, release checks, builds, publishing, and bilingual documentation for Blade Code.
devtestops
A full-process testing and release checklist, written in Chinese, for software work from clarifying requirements through post-release monitoring. DevTestOps means linking development, testing, and operational checks across the whole delivery process.
verify
Pre-merge verification gate. Build, test, and lint must all pass before marking done or shipping.