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
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 QwenLM/qwen-code --skill simplifygit 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/simplify)<a href="https://agentmods.dev/skills/qwenlm/qwen-code/simplify"><img src="https://agentmods.dev/badge/skills/qwenlm/qwen-code/simplify/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/qwenlm/qwen-code/simplify"><img src="https://agentmods.dev/badge/skills/qwenlm/qwen-code/simplify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00063 | $0.01113 |
| Opus 5.5 | $0.00025 | $0.00445 |
| Sonnet 5.5 | $0.00013 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
simplify 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify Recent Changes
You are running a structured cleanup workflow over recent code changes. Your goal is not just to comment on the code, but to safely improve it.
Step 1: Identify the review scope
Determine which files and changes to review.
- First inspect the current git state.
- If there are staged changes, review against
HEADso both staged and unstaged tracked changes are included. - Otherwise review the current uncommitted diff.
- If there is no git diff, fall back to
git ls-files --modified --others --exclude-standardso the scope respects.gitignore(this keeps build output,node_modules, and other ignored paths out of the cleanup). - If that is still empty, fall back to files edited in this conversation.
- If you still cannot identify a meaningful scope, stop and tell the user there are no recent changes to simplify.
Preferred commands:
git diff --name-onlygit diff --staged --name-onlygit diff HEAD --name-onlygit diffgit diff HEADgit status --short
Use git diff HEAD whenever staged changes exist. Otherwise use git diff.
Step 2: Launch three review passes in parallel
Use the agent tool and launch all review passes in a single response so they run concurrently. Set subagent_type: "general-purpose" and run_in_background: false on every call — each pass must return its findings inline. Do NOT fork them: never set subagent_type: "fork". A fork runs fire-and-forget and never returns its findings, so there would be nothing to aggregate in Step 3. Each pass must receive the same review scope and diff command. These passes are read-only: each one inspects and reports findings only and must not modify files — all edits happen later in Step 4.
Keep each review prompt short and focused. Do not paste the full diff into the prompt. Tell each pass to read the diff itself and inspect only files relevant to its findings.
Pass 1: Code Reuse Review
Look for opportunities to reduce duplication and reuse existing 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.
- 1mo ago First seen · 124 lines · 63 tokens per session scan A 739a6293f0c3
simplify is a skill published in the GitHub repository QwenLM/qwen-code (28,528 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 1,113 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-08-30.
Other skills, from other repositories
agentic-code-review
Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review
Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or…
simplify
Improve clarity and reduce needless complexity after behavior is understood; preserve behavior and keep cleanup separate from correctness fixes.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.