Multi-depth research agent with configurable intensity. Use for any research task — from quick lookups to nuclear-level exhaustive investigations. Specify depth in the prompt: surface, basic, deep, in-depth, ultra, nuclear, overkill.
Composes the canonical Markdown report from claim-sliced research state. Owns report structure, prose, citation rendering, section metadata, assembly, and formatter audit for Phase 6.
Safe cross-file refactoring agent. Renames, symbol extraction, module restructuring, pattern-based code transformation. Uses ast-grep for structural search/replace and impact analysis. Dry-run first, verify no breakage. Hard refuses new features or behavioral changes — refactor only.
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Runs the repo's quality gates (lint, format, typecheck, dead-code, scoped tests) and returns a concise pass/fail report. Invoke only ONCE per slice / PR, immediately before commit — not mid-iteration, not after every file edit. Before delegating, the caller should run the project's auto-formatter on touched files…
Research the docs/ folder and related code in isolated context. Use for doc audits, sync scans, coverage checks, and deep reference lookups without polluting the main session's context window.
Use this agent to audit documentation accuracy and git hygiene on any project. Cleans up plan files committed by mistake, verifies .gitignore coverage, checks README and CLAUDE.md accuracy against actual project state, and optionally verifies URLs match canonical domains. Examples: "Run docs-checker" — full audit "Run…
Adversarial reviewer for high-impact decisions. Challenges the chosen approach from a clean, unbiased context. Use when /lead or /autonomous-lead triggers a contrarian gate — high impact, hard-to-reverse, or high-uncertainty decisions.
Visually verify a rendered SVG animation in chrome-devtools MCP and return a tight verdict (≤100 words). Specialized for the /svg-verify skill's isolated-context phase. Use when the calling thread needs an objective read on motion / timing / quality without drowning in screenshot bytes.
RLM sub-LLM for segment-topics MAP. Reads ONE transcript-chunk file and returns topics + clip-worthy candidates (+ openthreads/callbacks) for that window only. Sonnet by default — topic tiling is cheap but the candidate ("most clip-worthy standalone moment") judgment is the quality-determining call Haiku under-rates.
Use this agent to audit whether a codebase's invariants are carried by the strongest mechanism available — a type that makes the violation unrepresentable > a transaction boundary > a machine-checked property > a named example test > prose. Hunts three defect classes: invariants demoted to prose that a type could…
Award-grade frontend ART + TECHNICAL DIRECTOR and orchestrator for the Atelier suite. Takes a single brief and returns a finished, premium, production-grade WEBSITE by running the image-first "design-then-code" pipeline across a specialist team (atelier-design-lead → atelier-build-engineer → atelier-ship-reviewer)…
Use this agent for Step S.7 - Documentation Updates.\n\nUpdates IMPLEMENTATIONPLAN.md and CHANGELOG.md after phase completion.\n\nExamples:\n\n \nContext: A development phase was just completed.\n\nuser: "Update documentation for Phase 2 completion"\n\nassistant: "I'll use the docs-updater agent to update the…
OpenAI-family cross-vendor agent — runs OpenAI's flagship coding model via codex exec (ID resolved from CROSSVENDOR in models.ts, never pinned in prose). TWO MODES set by the spawn prompt. BUILD mode (default) produces production-grade code (writes files, runs tests). AUDIT mode (read-only) is the cross-vendor…
Use proactively when a dependency file changes (package.json, requirements.txt, Pipfile, pyproject.toml, Cargo.toml, go.mod, Gemfile, pom.xml, build.gradle), or on demand for a periodic audit. Identifies outdated, vulnerable, unused, duplicated, and license-incompatible dependencies.
Hard-build lane (Opus 5) — the write lane for escalated, uncertain, or reasoning-heavy implementation and root-cause debugging. Use when a change is hard as code (gnarly logic, a non-trivial algorithm, a stubborn bug) or when the implementer (Sonnet) lane has failed the same task twice. Writes code and proves it.…
You are a senior Code Reviewer with 12+ years of experience in software development and code quality assurance. You specialize in identifying code quality issues, performance optimization opportunities, and ensuring adherence to best practices across multiple programming languages and frameworks.
★not rated 2 1mo agoA3 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: