Use this agent to gather codebase context for prompt transformation. Explores relevant files, finds similar implementations, identifies patterns to reference, and discovers tech stack constraints. Returns actionable context that makes transformed prompts specific to THIS codebase, not generic advice. Context: User…
Deep researcher — spawn to conduct thorough web research on the problem domain, save raw sources, and write structured findings. Use proactively when starting a new task, when scores plateau, or when the team needs fresh ideas from literature.
Clean-room tester that runs one realistic task using only an installed skill as documentation, then reports what it did. Invoked by the /skills:validate command; do not delegate ordinary work to it.
★not rated 1.1k▲
+71
changed 3d agoA44 tokens
originalMIT
Use this agent when the user needs to understand open-source libraries, find implementation details in codebases, locate specific source code with GitHub permalinks, research the history or context behind code changes, or get authoritative answers backed by actual code evidence. This agent excels at navigating large…
Interactive guide for building custom Claude Code Agents and subagents. Asks straightforward questions, generates enhanced YAML frontmatter with tools/model/color/field/expertise, creates agent .md files, validates format, and helps install to .claude/agents/ or /.claude/agents/. Use when user wants to build workflow…
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
Read-only search agent for broad fan-out searches - when answering means sweeping many files, directories, or naming conventions and you only need the conclusion, not the file dumps. It reads excerpts rather than whole files, so it locates code; it doesn't review or audit it. Specify search breadth - "medium" for…
Use this agent when you need comprehensive full-stack engineering expertise, particularly for server-side development, system architecture, DevOps, and infrastructure tasks. Examples include: (1) Designing and implementing scalable server architectures using languages like Node.js, Python, Go, Java, or Ruby; (2)…
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.
Subconscious subagent that surfaces cross-disciplinary structural parallels from the Vestige memory graph. Invoked by the preflight-swarm.sh UserPromptSubmit hook (Pre-Cognitive Triad v2.3 "Thalamus"). Fresh context, Haiku 4.5, Vestige MCP tool access. Outputs a single XML block or EMPTY.
Read-only code locator. Returns file:line table for "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Output is caveman-compressed so the main thread eats 60% fewer tokens than vanilla Explore. Refuses to suggest fixes.
CONTRIBUTOR TOOL - Orchestrates plugin validation against latest Claude Code documentation. Spawns parallel validation subagents per component type, compresses results via context-supervisor, generates compatibility report. Use proactively when running /docs-check. NOT distributed as part of the plugin - only…
Reviews a finished Impeccable build against its direction contract, the approved comp, and the chosen world's quality bar, returning an ordered list of material fixes.
Decomposes a confirmed GDD + ROADMAP into the current tag's artifact set — PLAN.md, STRUCTURE.md, SCENES.md, DESIGN.md, TOC.md, plus appends new rows to the cross-tag ASSETS.md (and optionally project.godot tweaks). Owns sub-stage 1c of /gm-gdd. Returns only a short summary so the lead's context stays lean.
★not rated 555▲
+1
changed 1mo agoA87 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: