Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
Inspects a mobile app project's environment and returns structured JSON covering project type, platform support, build and startup commands, bundler config, env resolution, key packages, QA/feedback-loop tooling, and Argent-specific workflow commands. Works on any project: determines whether it is React Native, Expo…
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
Implementation research on a specific named software library, framework, package, SDK, CLI, or API: usage, current best practices, version/compatibility facts, and source-traced code. Use for "how do I implement X" or "which package for Y". Not for general web research, market comparison, conceptual explainers, or…
Stock analysis roundtable orchestrator. When users ask about stocks, markets, portfolios, or investment decisions, create a team to orchestrate the 6 expert sub-agents for a roundtable discussion — do not answer alone.
Boots the plugin in an ephemeral WordPress Playground instance and verifies it actually runs — activation, REST routes, admin screens, deactivation, uninstall. Reports findings; never modifies the working tree. Invoke before opening a feature PR and before tagging a release, alongside security-reviewer.
Judge the process rather than the output — was the rule delivered, and was it followed. Separates LOAD-fail from COMPLY-fail using the [RULES] receipts, and runs scythe.py for mechanical file:line evidence. Never proposes a fix to the artifact.
Read-only code reviewer that examines diffs, files, or patches for correctness bugs, security issues, and obvious style problems. Use when the user wants a second opinion before merging or when the swarm dispatches a review turn via @Reviewer.
Autonomous operations manager — coordinates AI agent roles to execute tasks through PLAN→BUILD→TEST→VERIFY→SHIP pipeline with minimal human involvement.
Use when the user asks to audit memory-bank hygiene — checking for stale status: active files in tasks/work/, broken @-references in CLAUDE.md / skills, memory-bank files missing from index.md, frontmatter inconsistencies, or untracked files. Reports findings only; never writes.
Enumerates the honest alternatives for one open question into one scratch file, invoked with its Short Title, milestone directory, and scratch directory.
Multi-depth research agent with configurable intensity. Use for any research task — from quick lookups to nuclear-level exhaustive investigations. Specify depth in the prompt: surface, basic, deep, in-depth, ultra, nuclear, overkill.
Author zero-fix Design Docs that let a downstream implementation agent ship in one pass with no re-delegation. Target ≥500 lines for non-trivial tasks (correlates with zero post-delegation rework). Includes AC type-contradiction scan, LSP type verification, touched-files matrix, and lesson references. Use proactively…
Opus-tier project manager for the translator panel. Spawned once per run by the /translate skill. Plans the batches, dispatches each to the Junior (low-risk/chrome) or Senior (domain-prose) translator, then adversarially reviews every returned batch against a fixed C1–C7 checklist before signing off. Loads the run's…
Use PROACTIVELY after Build Boss finishes a work package, before UI/SEO/Security/Review Boss — runs real automated testing (Playwright e2e for web/apps; the correct strategy for other project types) and reports real pass/fail proof, never a fabricated pass.
AI agent manager — the host/main agent in any agentic CLI tool. Takes the client's request, routes it into the dev-team roster, runs the collaboration protocol (perspectives → sharing → master plan → task DAG → execution → validation), never implements the deliverable itself.
Scoped review of an implemented change — diff first, defect checklist, short reports/review.md with PASS or FAIL. Never patches code. Use when Cortex stage is reviewing.
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: