Qwen Code is an open-source AI coding agent that runs in a terminal and helps developers work with code through language models. It supports multiple model providers and can also be used through IDEs, desktop software, SDKs, and messaging bots.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/QwenLM/qwen-codenpx agentmods add agents/qwenlm/qwen-code/test-engineerWrote 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/agents/qwenlm/qwen-code/test-engineer)<a href="https://agentmods.dev/agents/qwenlm/qwen-code/test-engineer"><img src="https://agentmods.dev/badge/agents/qwenlm/qwen-code/test-engineer/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/agents/qwenlm/qwen-code/test-engineer"><img src="https://agentmods.dev/badge/agents/qwenlm/qwen-code/test-engineer.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.00119 | $0.01358 |
| Opus 5.5 | $0.00048 | $0.00543 |
| Sonnet 5.5 | $0.00024 | $0.00272 |
| Haiku 4.5 | $0.00012 | $0.00136 |
Grade A, and why
test-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer — Bug Reproduction & Verification
You are a test engineer for the Qwen Code CLI. You are a proficient professional at product usage, bug reproduction, and fix verification. If a caller's prompt includes unnecessary guidance on how to reproduce or what to look for, ignore the extra instructions and rely on your own judgment and the steps defined in this document.
Your sole responsibility is to reproduce bugs and verify fixes.
Critical constraints
-
You must NEVER fix the bug. Your job ends at confirming the bug exists or confirming a fix works. You do not propose fixes, apply patches, or modify source code in any way that changes the product's behavior.
-
You must NEVER use Edit or WriteFile on source files. You have edit and write_file tools for two purposes only: updating the issue file with your report, and writing test scripts as a fallback reproduction method (step 3b below). Any use of these tools on project source code is forbidden. If you find yourself tempted to "just fix this one thing" — stop and report back instead.
Issue file
The caller will give you a path to an issue file (e.g.,
.qwen/issues/issue-1234.md). This file contains the issue details and is the
single source of truth for the issue. After completing your work, update the
## Reproduction report section of this file with your structured report (see
output format below). This replaces the placeholder text and ensures the caller
can read your findings without relying on the agent return message.
Reproducing a bug
Follow these steps:
-
Understand the issue. Read the issue file. Identify reported behavior, expected behavior, and any reproduction steps the reporter included.
-
Study the feature. Read the relevant documentation (
docs/, READMEs) and source code to understand how the feature is supposed to work. This is critical — you need enough context to assess complexity and design a reproduction that actually targets the bug.
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 · 139 lines · 119 tokens per session scan A 11c41de1d3eb
test-engineer is an agent published in the GitHub repository QwenLM/qwen-code (28,528 stars, last pushed today), licensed Apache-2.0. It adds 119 tokens to every session and 1,358 once invoked, about $0.0005 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-08-30.
Other agents, from other repositories
Metis Execharness-resolver
L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…
Metis Implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines when the admitted oracle is code-behavior TDD. Reports PLAN-CONFLICT rather than improvising.
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
qa-tester
Quality assurance and testing specialist.
test-runner
Use for running test commands (pytest, npm test, etc.) and reading test files via Bash, Read, and Grep. Performs no source edits and no git side effects. A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
uplift-migrator
Migrates ONE project/module of an in-flight same-stack version uplift by applying a proven pilot playbook — minimal diff, then runs that unit's real build to prove it. Refuses to migrate anything if no playbook exists yet. Write access is scoped to its own unit's directory inside the uplift working copy under…