Emit a structured per-vulnerabledep verdict (AUTOMERGEPATCH | WAITFORPATCH | MANUALREVIEW | ACCEPTRISK | WONTFIX) from composite risk + KEV + EPSS + reachability + chains + policy. Use after /scan when many SCA findings need triage, before invoking /fix --sca.
Apply remediation patches for individual security findings from /security-scan. Calls the deterministic MCP toolchain (synthesizefix → verifyfix → applyfix) — does NOT edit files directly. Reports back what the deterministic verifier observed.
Use this agent when the user wants to prepare a pull request, review changes before PR submission, generate PR descriptions, or validate that code changes are ready for merge. Examples:\n\n \nContext: User has finished implementing a feature and wants to create a PR.\nuser: "I'm done with the auth feature, prepare it…
Inline sub-agent that reviews one workshop file for accuracy against the latest gh-aw documentation and release notes, and returns a structured JSON verdict.
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.
Expert photography prompt engineer specializing in crafting detailed, evocative prompts for AI image generation. Masters the art of translating visual concepts into precise language that produces stunning, professional-quality photography through generative AI tools.
Focused implementation agent for a single issue. Receives issue context, delivers code changes and tests. Does not handle git, branches, commits, PRs, or board operations — the parent orchestrator owns those.
Expert code reviewer for the project. Proactively reviews code for quality, security, privacy invariants, performance, accessibility, and adherence to specs.
Testability quality specialist — reviews generated code for per-feature test-class mandate (parser→fuzz, payment→mutation, RPC→contract), real-deal-first testing, coverage thresholds, and AI feature eval coverage. Use when test plans or test code are authored or modified.
Generic stage executor for the stagent plugin. Launched by the main agent for any subagent-typed stage in a workflow. Self-resolves its stage context from state.md via subagent-bootstrap.sh — does NOT rely on the main agent's prompt for path / epoch / input data. Then follows the stage's canonical instructions file…
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…
Use this agent when code changes have been made and need architectural review before being committed or merged. This agent should be invoked after any significant code modification to ensure alignment with Meerkat's architecture and Rust idioms.\n\nExamples:\n\n- user: "I've added a new caching layer to meerkat-cli…
Use this agent when code has been written or modified in the Meerkat Rust project and needs to be reviewed for idiomatic Rust quality, correctness, and adherence to project design guidelines. This agent should be invoked after completing a meaningful code change — whether a new function, module, refactor, or bug fix …
20 3d agoA436 tokens
originalApache-2.0
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: