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/qwenlm/qwen-code/e2e-testingnpx skills add QwenLM/qwen-code --skill e2e-testinggit clone --depth 1 https://github.com/QwenLM/qwen-codeWrote 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/qwenlm/qwen-code/e2e-testing)<a href="https://agentmods.dev/skills/qwenlm/qwen-code/e2e-testing"><img src="https://agentmods.dev/badge/skills/qwenlm/qwen-code/e2e-testing.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 | $0.00094 | $0.02117 |
| Opus 5 | $0.00047 | $0.01059 |
| Sonnet 5 | $0.00019 | $0.00423 |
| Haiku 4.5 | $0.00009 | $0.00212 |
Grade A, and why
e2e-testing 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 3d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Testing Guide
How to run the Qwen Code CLI end-to-end — from building the bundle to inspecting raw API traffic. Use when unit tests aren't enough and you need to verify behavior through the full pipeline (model API → tool validation → tool execution).
Setup
Which binary to use
- Reproducing bugs: use the globally installed
qwencommand — this matches what the user ran when they filed the issue. - Verifying fixes: build first (
npm run build && npm run bundle), then runnode dist/cli.js— this tests your local changes. - Runtime-only checks (fastest):
npm run dev -- "<prompt>" <flags>— runs TS source via tsx, no build. Usebuild && bundle+node dist/cli.jsonly when the shipped artifact itself matters. (<qwen>below can benpm run dev --.)
Running against a real model
Headless auth comes from ~/.qwen. Force a known-good model with --auth-type +
--model:
<qwen> "your prompt" --auth-type openai --model deepseek-v4-flash \
--approval-mode yolo --output-format json
Gotcha: --model alone won't switch providers — --auth-type (openai/anthropic/qwen-oauth/gemini/vertex-ai) does. Omit it and the run falls back to the default provider and dies
on its missing key.
Isolating runtime artifacts
QWEN_RUNTIME_DIR=<dir> redirects qwen's runtime output — tmp/, debug/,
and projects/<sanitized-cwd>/... (chat recordings, auto-memory, history) —
into <dir> instead of ~/.qwen. Config (settings.json, OAuth tokens,
commands/) still reads from ~/.qwen, so real auth and provider config
work without any setup.
Use when repeated test runs would clutter your real chat history or auto-memory. Skip when the bug you're reproducing depends on the user's actual history or runtime state — that is the repro.
QWEN_RUNTIME_DIR=/tmp/test-1/runtime <qwen> "prompt" ...
Run modes
Headless Mode
Run the CLI non-interactively with JSON output (<qwen> = qwen or
node dist/cli.js per above):
What ships with it
5 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.
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.
- 3d ago First seen · 240 lines · 94 tokens per session scan A 35430d4c5d72
e2e-testing is a skill published in the GitHub repository QwenLM/qwen-code (27,559 stars, last pushed yesterday), licensed Apache-2.0. It adds 94 tokens to every session and 2,117 once invoked, about $0.0005 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-30.
Other skills, from other repositories
dev-testing
测试规范 — 单元测试/集成测试/API测试/E2E测试四类覆盖标准与触发条件.
dev-scenario-test
场景测试子类型规范 — 端到端/集成测试 + artillery 负载测试.
playwright
Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…