Detects file-loading paths that bypass sys.audit() hooks by using open() instead of io.opencode(), and shell-calling paths where validation occurs before template substitution. Invoke when scanning importlib, webbrowser, or venv.
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.
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).
Researcher agent. Handles deep investigation, information gathering, source triangulation, and synthesis. Use when asked to research, investigate, do technical/market research, comparative analysis, or "look into..." and "what's the current state of...?".
Local code reviewer and the designated reviewer for Codex-authored diffs. Use before any merge whenever the diff was authored by Codex (Codex never reviews its own work), Codex is unavailable, its quota window is exhausted, or the code must not leave the machine. Reviews the branch diff against its spec for…
"Is this correct?" — Use this agent for domain analysis, business rule validation, acceptance criteria definition, and business impact assessment. Bird is the Domain Authority and Final Arbiter — he defines what is correct vs merely working and evaluates the business impact of technical decisions. Use via /team for…
Use this agent when you need to actively test applications, APIs, infrastructure, or code for exploitable vulnerabilities. This agent thinks like an attacker and finds entry points before real attackers do. It complements the security-master agent through practical attack simulation. This agent should be used…
Build ROI-ranked, deduped backlogs from parallel repo analysis to GitHub issues on a Project board. 8-phase composite: discover (parallel) → rank → propose (approval gate) → spec → plan → issues → board → snapshot. Use when starting a new work session on a repo or when "what should I work on" needs a structured answer.
Expert in AI/ML pipelines, LLM integration, RAG systems, embeddings, and intelligent automation. Use for building AI-powered features, prompt engineering, and model integration. Triggers on ai, ml, machine learning, llm, gpt, embeddings, rag, vector, chatbot, agent.
Deep, sourced web-research engine. Confirms every datum with ≥2 independent sources, extracts verbatim quotes, flags contradictions and unknowns. Output: findings+provenance JSON artifact (written to file) + one-line return. Shared worker for ds-research and ds-brief.
Expert code quality reviewer for newly created/modified code. Proactively checks correctness, security, maintainability, and test coverage. Use proactively after code changes.
Coding agent via Codex CLI. Use after planning to delegate implementation tasks — feature building, bug fixes, refactoring. Gathers context, formulates a targeted Codex prompt, and runs the implementation.
Confidence-based code review specialist. Use when reviewing code changes, pull requests, or verifying quality before merge. Applies scoring threshold of 80+ to avoid noise.
Analyzes DevExperience history every 10 tasks. Identifies specific tasks needing correction, passes explicit task IDs to FixPlanner. Updates developer-addendum only (never overwrites developer.md).
Delegate to this subagent when you need changeset@2 artifacts produced from a git diff. Input is a git diff, optionally a linked spec@1, and optionally smith's criteriaevidence from the TDD run that produced this diff. A diff spanning multiple independent topics produces one changeset@2 per topic, never one bundled…
Use this agent when you want to eliminate code duplication across your codebase. Examples: Context: User has just written several similar functions and wants to clean up duplication. user: 'I just added these three validation functions that seem really similar' assistant: 'Let me use the code-deduplicator agent to…
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
Validates task files against task template and task-creator rules. Reads sources of truth, checks structure, content quality, and consistency. Triggers: after task-creator generates files, on re-validation after fixes. Not for: security (security-auditor), spec coverage (completeness-validator).
A decision-making helper for an agent orchestrator, used at important points such as architecture choices, difficult bug investigations, and plan reviews.
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
Standard implementation agent for well-specified tasks tagged [T1] — features from a clear spec, unit tests, documentation, renames, config changes, mechanical multi-file edits, straightforward bugfixes with a known repro. MUST BE USED for [T1] tasks.
★not rated 1
changed 9d agoA57 tokens
originalMIT
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: