A setup command for checking whether the Qwen Code command-line tool is installed and ready. It can also turn an optional review check on or off when the agent stops.

Use it to check Qwen Code, install it when needed, preserve authentication guidance, or enable or disable the stop-time review gate for a repository.

It makes the Qwen setup status clear and guides installation or authentication when the tool is missing or not connected.

setup — Command for Claude Code by josephyaduvanshi

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add josephyaduvanshi/qwen-companion

Claude Code

/plugin install qwen

Made for: Claude Code.

Or install qwen, the plugin that ships this one along with the rest of its 3 skills, 7 commands, 1 agent, 3 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/josephyaduvanshi/qwen-companion/setup/github.svg)](https://agentmods.dev/commands/josephyaduvanshi/qwen-companion/setup)

Your own site

<a href="https://agentmods.dev/commands/josephyaduvanshi/qwen-companion/setup"><img src="https://agentmods.dev/badge/commands/josephyaduvanshi/qwen-companion/setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/josephyaduvanshi/qwen-companion/setup"><img src="https://agentmods.dev/badge/commands/josephyaduvanshi/qwen-companion/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 317 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00018	$0.00317
Opus 5	$0.00009	$0.00159
Sonnet 5	$0.00004	$0.00063
Haiku 4.5	$0.00002	$0.00032

Measured 9d ago against content hash efdc011c2254, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

setup 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 9d 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.

plugins/qwen/commands/setup.md · 38 lines

What it actually says

Run:

node "${CLAUDE_PLUGIN_ROOT}/scripts/qwen-companion.mjs" setup --json $ARGUMENTS

If the result reports qwen: not found and npm is available:

Use AskUserQuestion exactly once to ask whether Claude should install Qwen Code now.
Put the install option first and suffix it with (Recommended).
Use these two options:
- Install Qwen Code (Recommended)
- Skip for now
If the user chooses install, run:

npm install -g @qwen-code/qwen-code

Then rerun:

node "${CLAUDE_PLUGIN_ROOT}/scripts/qwen-companion.mjs" setup --json $ARGUMENTS

If Qwen Code is already installed or npm is unavailable:

Do not ask about installation.

Output rules:

Present the final setup output to the user verbatim.
If Qwen is installed but not authenticated, preserve the guidance to run !qwen auth qwen-oauth or to configure an API key in ~/.qwen/settings.json.
If installation was skipped, present the original setup output.
Arguments like --enable-review-gate and --disable-review-gate toggle the optional stop-time review gate per repository.

Changes

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.

9d ago First seen · 38 lines · 18 tokens per session scan A efdc011c2254

Subscribe to this mod's changes

setup is a command published in the GitHub repository josephyaduvanshi/qwen-companion (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 317 once invoked, about $0.0001 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.

setup

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement