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 commands/strands-rl/strands-sglang/run-unit-testsgit clone --depth 1 https://github.com/strands-rl/strands-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/commands/strands-rl/strands-sglang/run-unit-tests)<a href="https://agentmods.dev/commands/strands-rl/strands-sglang/run-unit-tests"><img src="https://agentmods.dev/badge/commands/strands-rl/strands-sglang/run-unit-tests.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.00218 |
| Opus 5 | $0.00000 | $0.00109 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
run-unit-tests 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 6d 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
Run unit tests in an isolated temporary venv created with uv (mimics CI).
Steps:
- Create a temporary venv at
/tmp/strands-sglang-test-venvusinguv venv /tmp/strands-sglang-test-venv --python 3.12 -q - Install the package with dev dependencies:
uv pip install -e . --group dev --python /tmp/strands-sglang-test-venv/bin/python -q - Run linting:
/tmp/strands-sglang-test-venv/bin/ruff check src/ && /tmp/strands-sglang-test-venv/bin/ruff format --check src/ - Run unit tests:
/tmp/strands-sglang-test-venv/bin/python -m pytest tests/unit/ -v --tb=short $ARGUMENTS
IMPORTANT: Never use the active shell's python/pytest — it may point to a different venv. Always use the temporary venv's python.
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.
- 6d ago First seen · 10 lines · 0 tokens per session scan A 85c61db4f23a
run-unit-tests is a command published in the GitHub repository strands-rl/strands-sglang (78 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 218 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-30.
Other commands, from other repositories
write-tests
Generate comprehensive test coverage for existing code.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test
Generate comprehensive tests.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
unit-test
Write / run the unit tests for the feature. (AIDLC Unit Test phase) Usage: /unit-test.