Read-only search agent for broad fan-out searches - when answering means sweeping many files, directories, or naming conventions and you only need the conclusion, not the file dumps. It reads excerpts rather than whole files, so it locates code; it doesn't review or audit it. Specify search breadth - "medium" for…
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
Mechanical execution of fully-specified work - pattern-based refactors and renames, writing tests that follow existing conventions, documentation updates, bulk multi-file edits from an explicit spec, running test suites and fixing trivial failures. Use when the task needs no design decisions; give it a complete spec…
Read-only reconnaissance. Use for any search, lookup, or "where/how is X" question that requires no judgment - locating files, symbols, usages, config values, or summarizing how something works across a codebase. Returns concise findings with file:line references. Cheapest way to gather facts; prefer it over reading…
Security-sensitive implementation and analysis - authentication/authorization, secrets handling, crypto usage, input validation, hardening, dependency vulnerability triage, security-relevant code review. Use for ANY task where the word "security" applies, instead of executor or the main session.
Fresh-context adversarial verification of completed work. Use after any non-trivial change, before reporting it done - give it the claimed outcome and the diff/paths, and it independently tries to refute the claim by exercising the code, running tests, and probing edge cases. Returns CONFIRMED or REFUTED with…
Read-only fresh-context review of one stable Plan envelope or execution slice before approval. Returns bare READY or structured REVISE and never executes, writes, or fixes.
Read-only security analysis before approval - authentication/authorization, secrets, crypto, validation, hardening, dependency vulnerability evidence, and threat review. Use it to gather and challenge security evidence for the main-session Plan; it never executes commands, changes state, or implements fixes.