github miqdadbadjuber/anti-slop v3.2.32
v3.2.32: Qwen Code joins the installer

one hour ago

Qwen Code joins the installer as the seventeenth agent. It keeps a project folder of its own, reads the shared .agents/skills folder at user level, and takes its session pointer in QWEN.md. No plugin door ships for it, so the installer and the skills directory are the routes.

A folder of its own, and a pointer

Qwen Code documents .qwen/skills/ for a project and ~/.qwen/skills/ at user level, and it also reads .agents/skills/ at both scopes. The installer writes .qwen/skills/ in a project and the shared ~/.agents/skills/ for a global install, so a global Qwen install joins the same folder Codex, Copilot, Kimi Code, Amp, DeepSeek Harness, Muse Code, Kilo Code, and the other shared-folder agents already use.

Qwen loads QWEN.md and AGENTS.md together, so the session pointer goes into QWEN.md: one block per file, even when another agent's install also writes AGENTS.md in the same project.

The installer now covers seventeen agents over eleven project folders.

No plugin door, and why

antislop ships no Qwen extension manifest, so Qwen Code has two routes: the installer, or the skills directory with its own agent flag.

npx skills add miqdadbadjuber/anti-slop -a qwen

The shipped frontmatter stays as it is. Qwen reads the allowedTools field and ignores an allowed-tools field written for another agent, so the shipped field is inert there and no second permission list is added. A per-agent grant list would be a second source of truth that drifts with every skill change.

What is verified, and what is not

The paths come from Qwen's own documentation, which states that personal skills live in ~/.qwen/skills/, project skills in .qwen/skills/, and that ~/.agents/skills/ and .agents/skills/ are read without configuration. The pointer was checked against a real install: a sandbox project and home, installed through the installer's own functions, then read by qwen-code 0.27.0 in a headless session. The always-on context measured 13,743 tokens without the pointer and 14,138 with it, and all six skills resolve in a live session.

This repository passes its fifteen checks and the installer smoke test, which covers the project target, the global target, the shared global folder, the written skills, the QWEN.md pointer, the folder check, and the named duplicate read. CI is green on Ubuntu, macOS, Windows, and the minimum Node version.

The one claim that rests on documentation rather than an observed test is the allowedTools behavior. The effect is that the shipped field does nothing under Qwen, which is the same outcome as a skill with no tool rules.

From community PR #69.

Updating

The installer route is unchanged:

npx antislop-ai --update

It replaces every antislop folder already on this machine at both scopes, keeps each folder's skill selection, and prints the release it replaced. A Qwen Code project installed before this release has no antislop folder yet, so run npx antislop-ai once and select Qwen Code. Skills load when a session starts, so start a new one afterwards.

The plugin doors are unaffected by this release. Each keeps its own copy and updates through its own manager.

Don't miss a new anti-slop release

NewReleases is sending notifications on new releases.