LogoAwesome Skills
  • Search
  • Category
  • Tag
  • Blog
LogoAwesome Skills
LogoAwesome Skills

Discover Open-Source Agent Skills for AI Coding Assistants

Product

  • Search
  • Category
  • Tag
  • Blog

Resources

  • Claude Skill Docs
  • Antigravity Skills Docs

Tools

  • Claude Code
  • OpenCode
  • Cursor
  • Codex
  • Antigravity

Company

  • Privacy Policy
  • Terms of Service
  • Sitemap

©2026 Awesome Skills. All rights reserved.

Privacy PolicyTerms
Back to Skills

qwen-agent

Delegate menial, well-scoped coding tasks to a cheap Qwen-backed subagent via the `claude-9arm` command instead of burning Claude tokens/quota. Use when the work is mechanical and low-risk — bulk renames, formatting, boilerplate, find-replace, grep-style search & summarization, reading/condensing logs or files, test/docstring/comment scaffolding, or running builds/linters/tests and reporting pass-fail. Also use when the user says "use qwen", "delegate this", "send it to 9arm/qwen", or "do this c

3,104stars419forksUpdated 8/14/2026
Productivity & Workflow#agents#productivity#code-generation#cli#automation

Security Assessment

Low Risk(85/100)

Detected risks:

Autonomous subagent with pre-approved tools(The skill spawns a headless subagent granted a pre-approved tool set that includes shell execution and file writing so it can run unattended without per-action approval., It optionally recommends adding a permission allow rule so the delegated command no longer prompts, and an edit-auto-accept mode, both of which reduce human oversight of a cheaper, less reliable model.)
Security Score85/100

About qwen-agent

qwen-agent is a skill for delegating menial, well-scoped coding tasks to a cheaper Qwen-backed subagent that runs inside a headless Claude Code instance invoked through the `claude-9arm` shell alias. The goal is cost control: keep expensive Claude reasoning for work that needs it and offload mechanical jobs — bulk renames, formatting, boilerplate, find-replace, grep-style search and summarization, log/file condensing, docstring and comment scaffolding, and running builds/linters/tests to report pass/fail.

The skill's core guidance is operational. Because the subagent inherits zero context from the current conversation, every delegated prompt must be fully standalone with absolute paths, explicit inputs/outputs, and acceptance criteria. It explains running the subagent headless with `-p` and scoping tool access with `--allowedTools Bash Read Edit Write Glob Grep` so the job finishes unattended, plus a lower-risk `--permission-mode acceptEdits` for edit-only work. It stresses sizing tasks to Qwen's 128k context window, splitting large jobs into bounded per-file/per-directory chunks, using absolute paths (since `cd` resets between Bash calls) or `--add-dir`, and a return contract covering text output, JSON parsing, and background/parallel runs. A workflow checklist ends with the essential rule: verify the cheaper model's output yourself before reporting success.

It targets developers and agent operators who want to reduce token spend on low-judgment work. The skill is explicit about what NOT to delegate — architecture, design, debugging judgment, security-sensitive edits, or anything needing conversation context. The main consideration is that it runs an autonomous subagent with pre-approved Bash and file-write tools, and optionally suggests a settings rule to suppress per-call permission prompts, which reduces human oversight of a less reliable model.

FAQ

When should I delegate a task to the Qwen subagent?

Only for menial, low-risk, self-contained work — renames, formatting, boilerplate, find-replace, search/summarize, and build/lint/test runs. Not for architecture, design judgment, debugging, or security-sensitive changes.

How is the subagent invoked?

Via the `claude-9arm` alias (Claude Code pointed at a Qwen model through the 9arm gateway), run headless with `-p` and an explicit `--allowedTools` list so it can complete work without stalling on approvals.

What is the biggest failure mode?

Vague prompts. The subagent has no conversation context, so every prompt must be standalone with absolute paths, explicit inputs/outputs, and acceptance criteria. It also has a 128k context window, so large jobs must be split into bounded chunks.

Do I need to check the results?

Yes. The workflow requires verifying the subagent's output yourself against the acceptance criteria before reporting success, since the cheaper model is less reliable.

Does it change my permission settings?

Optionally. It suggests adding a Bash allow rule for `claude-9arm` to stop repeated permission prompts, which is a convenience but reduces per-call oversight of the delegated runs.

Install qwen-agent

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

thananon/9arm-skills

Related Skills

threat-modeling-with-aws-security-agent

2,903

amazon-workspaces-agent-access

2,903

build-loop-codex

230

developing-ios-apps

1,477