Autonomous debugging agent that uses IDE bridge debug and terminal tools. Sets breakpoints, evaluates expressions, inspects runtime state, and fixes bugs. Use when encountering test failures, runtime errors, or unexpected behavior.
Long-term codebase architectural health agent. Identifies God objects, circular dependencies, tightly coupled modules, and modularization opportunities using LSP import tree and call hierarchy analysis. Use for architecture audits, pre-refactor planning, or onboarding deep-dives.
Diagnose and resolve Robot Framework test failures, flaky tests, environment issues, and execution errors. Invoke when the user needs to analyze output.xml results, interpret error messages, debug locator failures, fix timing issues, or understand why a test suite is failing.
Dixon - The Detective 🔎. Debugging specialist who hunts root causes, not symptoms. Invoke when encountering errors, test failures, or unexpected behavior. Systematically isolates problems, proposes minimal fixes, and recommends prevention strategies.
Use to investigate Unity connection, compilation, console, scene-health, runtime-state, rendering, memory, or performance problems through Unity Biome MCP. Do not use to implement fixes.
Use when the user asks to inspect, control, or troubleshoot a running Bubbaloop deployment — node lifecycle (start/stop/restart/build), health checks, log reads, mission management, or scheduling tasks. Wraps the bubbaloop MCP server and enforces the discover-before-act discipline.
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development. Use proactively when needing to understand how a feature works before modifying or extending it.
Use this agent to audit error handling correctness in C extension code that calls the Python/C API.\n\n \nUser: Check the error handling in my C extension.\nAgent: I will run the error path scanner, prioritize missing NULL checks and return-without-exception findings, and review extension-specific error patterns like…
Advanced Pine Script parsing and AST generation expert that MUST BE USED PROACTIVELY for complex syntax analysis, parameter extraction, and validation rule creation. Specializes in parsing Pine Script code to extract parameters, identify syntax patterns, and generate structured representations for validation engines.
Full observer with 7 drift detection patterns + devil's advocate stance. Writes to .claude/observers/QUALITY.md and .claude/observers/ARCH.md. Thorough analysis for STANDARD/FULL scope tasks.
Use when quick reconnaissance is complete and an unfamiliar or risky bounded scope needs a read-only trace or thorough map of ownership, contracts, consumers, and unknowns.
A problem-analysis agent that turns an incomplete report into key facts and suggested investigation paths. Reports may come from users, product managers, developers, testers, error logs, or monitoring alerts.
Implement the minimal fix for a confirmed security finding with a working PoC. Creates a branch, edits source files, runs project tests if they exist, and commits. Does NOT open the PR. Invoke when a finding is in pocwritten state.
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! :).
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
25 10mo agoA68 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: