Qoder joins the installer and becomes the tenth plugin door. The installer writes Qoder's own skill folder and the AGENTS.md pointer it already reads, and .qoder-plugin/plugin.json loads the same six skills through Settings > Plugins. A new repository check makes sure no future door can ship unnamed in the single file.
A folder of its own, and a pointer
Qoder documents .qoder/skills/ for a project and ~/.qoder/skills/ at user level, so the installer writes those paths rather than the shared .agents/skills/ folder. Qoder also loads AGENTS.md as project rules, which is where the session pointer goes on a project install.
The installer now covers sixteen agents over ten project folders.
The plugin door
.qoder-plugin/plugin.json points at the same skills/ folder as the other doors. Qoder imports a plugin from a local folder, so the plugin route is a clone of this repository and an import in Settings > Plugins.
The plugin was imported into Qoder 0.5.11 at user scope. The registry listed antislop@local 3.2.31 as enabled, the cache held the manifest and all six skill folders, and a fresh session found all six skills by name with the core loading without error.
npx antislop-ai --update now names an installed Qoder plugin copy too, read from Qoder's own registry, so the update is reported next to the other doors.
The door list that fell behind
The single file antislop.md names every plugin door and its update command by hand. It still said seven after Qoder was added, so Qoder now appears there and the count is eight.
A new check in scripts/check-repo.mjs compares that list against the plugin doors the installer knows about, including the count in prose, so the same drift cannot ship again. The repository check is now fifteen checks.
What is verified, and what is not
This repository passes its own fifteen checks, and CI is green on Ubuntu, macOS, Windows, and the minimum Node version. The installer smoke test passes.
The skill paths, the AGENTS.md rule file, and the user-level folder come from Qoder's own documentation. The plugin manifest is not in the public documentation: its path and fields come from the plugin-creator specification bundled with Qoder 0.5.11, and the live import above is what confirms them.
The import ran through Qoder's installer API, which performs the same validation, install, and enable transaction the Plugins page uses. The Plugins card itself was not captured, because the app does not expose that window; the registry, the cache layout, and the fresh-session output are the evidence.
From community PR #67.
Updating
The installer route is unchanged:
npx antislop-ai --updateIt replaces every antislop folder already on this machine at both scopes and prints the release it replaced. A Qoder project installed before this release has no antislop folder yet, so run npx antislop-ai once and select Qoder.
The plugin keeps its own copy under Qoder. To update it, pull the clone and import the same folder again in Settings > Plugins. Skills load when a session starts, so start a new one afterwards.