Autopus-ADK is of the agents, by the agents. for the agents. Multi-model orchestration (consensus/pipeline/debate/fastest). Architecture-as-Code, Lore decision tracking, SPEC/EARS engine.
Command
A command for deployment verification that runs a build, end-to-end tests, and browser health checks. End-to-end tests check a complete user flow across the application rather than only one small part.
Command
A command that runs a full development cycle in sequence: planning, execution, and synchronization.
Command
A diagnostic command for checking whether the development harness is installed correctly and whether its platform connections are wired up.
Command
A bug-fixing command that focuses on reproducing a problem and making the smallest suitable code change.
Command
A code-implementation command that builds features from a SPEC document, a written description of the intended behavior and requirements.
Command
A command wrapper for creating goals and checking, completing, or handing off their status. It can also preserve a selected model and variant.
Command
An idea-brainstorming command that uses discussion across multiple AI providers and ICE scoring, a way to rank ideas by impact, confidence, and ease.
Command
A command that quickly summarizes a codebase’s structure, entry points, and dependencies. Entry points are the files or commands where execution begins.
Command
A command that analyzes a codebase and produces a SPEC, implementation plan, and acceptance criteria. Acceptance criteria are checks that define when the work is done.
Command
QAMESH project QA mesh — plan, run, report, and publish deterministic QA evidence.
Command
A code-review command that evaluates changed code against the TRUST 5 criteria.
Command
A security-audit command that checks the scope of code changes using the OWASP Top 10, a commonly used list of major web-application security risks.
Command
A command that analyzes a codebase and creates project context documents, including ARCHITECTURE.md and files under .autopus/project.
Command
A command that shows the current SPEC status for a project and its submodules. A SPEC is a written description of requirements and implementation work.
Command
A documentation-synchronization command for updating the specification, change log, and other documentation after implementation.
Command
A command that runs end-to-end tests, which check complete user or system flows, from scenarios written in a scenarios.md file.
Command
A harness-update command that detects the current repository or metadata workspace and refreshes its available harness components.
Command
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
Command
A command that traces the reason behind a project decision through Lore, SPEC, and ARCHITECTURE documents.
Command
A command router that sends each `/auto` request to one specific helper, such as setup, testing, planning, or review.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: