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 docs-audit-and-refreshgit 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/docs-audit-and-refresh)<a href="https://agentmods.dev/skills/qwenlm/qwen-code/docs-audit-and-refresh"><img src="https://agentmods.dev/badge/skills/qwenlm/qwen-code/docs-audit-and-refresh.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.00069 | $0.00813 |
| Opus 5 | $0.00034 | $0.00407 |
| Sonnet 5 | $0.00014 | $0.00163 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
docs-audit-and-refresh 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 7d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Audit And Refresh
Overview
Audit docs/ from the repository outward: inspect the current implementation,
identify documentation gaps or inaccuracies, and update the relevant pages. Keep
the work inside docs/ and treat code, tests, and current configuration
surfaces as the authoritative source.
Read references/audit-checklist.md before a broad audit so the scan stays focused on high-signal areas.
Workflow
1. Build a current-state inventory
Inspect the repository areas that define user-facing or developer-facing behavior.
- Read the relevant code, tests, schemas, and package surfaces.
- Focus on shipped behavior, stable configuration, exposed commands, integrations, and developer workflows.
- Use the existing docs tree as a map of intended coverage, not as proof that coverage is complete.
2. Compare implementation against docs/
Look for three classes of issues:
- Missing documentation for an existing feature, setting, tool, or workflow
- Incorrect documentation that contradicts the current codebase
- Stale documentation that uses old names, defaults, paths, or examples
Prefer proving a gap with repository evidence before editing. Use current code and tests instead of intuition.
3. Prioritize by reader impact
Fix the highest-cost issues first:
- Broken onboarding, setup, auth, installation, or command flows
- Wrong settings, defaults, paths, or feature behavior
- Entirely missing documentation for a real surface area
- Lower-impact clarity or organization improvements
4. Refresh the docs
Update the smallest correct set of pages under docs/.
- Edit existing pages first
- Add new pages only for clear, durable gaps
- Update the nearest
_meta.tswhen adding or moving pages - Keep examples executable and aligned with the current repository structure
- Remove dead or misleading text instead of layering warnings on top
5. Validate the refresh
Before finishing:
- Search
docs/for old terminology and replaced config keys - Check neighboring pages for conflicting guidance
- Confirm new pages appear in the right
_meta.ts - Re-read critical examples, commands, and paths against code or tests
- Verify bundled skill doc indices still match the current
docs/tree. Theqc-helperbundled skill (packages/core/src/skills/bundled/qc-helper/SKILL.md) maintains a hardcoded table mapping topics to doc file paths. If you added, moved, renamed, or removed a page underdocs/users/, that table must be updated to match. Check the Features and Configuration tables in the SKILL.md against the actual files indocs/users/features/anddocs/users/configuration/. Other bundled or project skills may also reference doc paths — search fordocs/users/across.qwen/skills/andpackages/core/src/skills/bundled/to catch them.
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.
- 7d ago First seen · 96 lines · 69 tokens per session scan A dc961ab12463
docs-audit-and-refresh is a skill published in the GitHub repository QwenLM/qwen-code (27,673 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 813 once invoked, about $0.0003 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
agent-manager
Run a fleet of AI coding agents as live tmux sessions with agent-manager. Use when a developer is running more than one coding agent, needs to see which one is working or blocked, wants to spawn another on an independent task, or wants to review an agent's diff without leaving the terminal.
agent-manager-reference
Query agent-manager.dev's reference API and MCP server for documentation, the coding CLIs it manages, the tools its MCP server exposes, and the current release. Use instead of scraping the website's HTML.
sls-dashboard-builder
A tool for creating and modifying importable JSON dashboards for Alibaba Cloud SLS, a service for searching and monitoring logs. It maps checked queries and analysis needs to dashboard charts.
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
loongsuite-pilot-ops
Skill "loongsuite-pilot-ops" from alibaba/loongsuite-pilot, covering loongsuite-pilot-ops, quick start, todo: add quick start commands and usage.
proactive-agent
Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer, Autonomous Crons, and battle-tested patterns. Part of the Hal Stack 🦞.