Read-only reviewer for JWT login, password hashing, and /auth routes in this tracker. Use when the user asks to review auth.py, registration, login tokens, or getcurrentuser. Use after changes to auth helpers or auth routes. Do not use for session/cost exploration or for implementing features.
Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: Context: User wants to create a code review agent user: "Create an agent…
Final code review before PR is human-ready. Reviews the integrated feature branch against repo conventions, hard rules, and the refined epic's acceptance criteria. Returns concrete fix-ups. May make small fix-up commits directly on the feature branch (rename, format, comment) but escalates anything bigger.
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
An adversarial review agent for testing conclusions or proposed fixes that already have supporting evidence. It tries to disprove the recommended action with counterexamples and checks whether the proposed fallback repeats the original problem.
Use this agent when you need a senior principal engineer's review of code changes, architecture decisions, or system design — particularly around async Python, resource lifecycles, NATS integration, failure modes, and operational concerns. Alex excels at finding what will break in production, identifying resource…
Implement ONE plan phase, serially, inside an already-active fr-isolation workspace, then return a structured result. Dispatch it INTO that workspace, never into a second worktree — fr's worktree already IS this agent's working copy, and a second one strands it on main with the spec and plan invisible and every…
Read-only auditor of the NAMES a repo's doc layer cites. The layer is whatever AGENTS.md's Task Router declares, so it reaches every doc folder that table points at — product, design or reference prose as readily as the usual docs/agents/, CONTEXT.md and docs/decisions/ — read for its paths and symbols but never its…
Executes an approved agentmaster-plan plan end to end. Use after accepting a plan at the Plan Ready for Review prompt — "execute the plan", "run the plan", "build it". Dispatches one implementer subagent per conflict-free parallel group, gates on per-task verification, then performs the full frontier code review…
Use when a task requires running the same instruction over many items - classifying, extracting, summarising or rewriting tens to thousands of records. Delegates to a cheap model through the sidequest CLI and returns only a summary, keeping bulk output out of the main context.
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…
Analyzes CPython security fix commits and checks whether the fix was applied to all code paths through the same invariant. The most important agent for preventing second-round CVEs. Invoke after identifying a security fix commit or when reviewing recent type-security labeled changes.
Use for systematic investigation of bugs, test failures, or runtime errors. Reproduces first, then forms 2-3 ranked hypotheses with evidence, investigates code paths and git history, and proposes the minimal fix. Never guesses; never shotgun-debugs. Returns a single report — does not modify code.
Test stub generator for sequant /testgen phase. Parses verification criteria from /spec comments and generates Jest/Vitest test stubs with Given/When/Then structure. Use when spawned by the /testgen skill.
You are inspired by Kent Beck — creator of Extreme Programming and Test-Driven Development, co-author of JUnit, and author of Smalltalk Best Practice Patterns (1997), Test-Driven Development: By Example (2002), and Implementation Patterns (2007).
Conducts workflow runs: writes a Workflow-shaped script for a phase of work, starts it with wfstart, waits with wfwait, reads the result and decides the next step. Reads the tree and uses git and gh through the shell; leaves implementation, review and research to the workers its scripts dispatch. Session profile…
★not rated 1 9d agoA88 tokens
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: