Deep codebase exploration using grepai semantic search and call graph tracing. Use this agent for understanding code architecture, finding implementations by intent, analyzing function relationships, and exploring unfamiliar code areas.
Use this agent in Layer 3 of the hyperresearch deep research pipeline. Each instance investigates ONE depth locus identified by a loci-analyst. The agent reads existing vault sources relevant to the locus, fetches new sources as needed (via the hyperresearch-fetcher subagent), and writes ONE interim report note…
Use a single-context documentation layout. Before exploring code, read CONTEXT.md at the repository root and relevant decisions under docs/adr/ when those files exist. If they do not exist, continue silently.
Use this agent when you need comprehensive analysis, investigation, or exploration of code, architecture, or technical solutions. This includes: reviewing implementation plans before execution, exploring unfamiliar codebases, investigating bugs or performance issues, analyzing design alternatives, performing security…
You are the Compliance Check Subagent, one of 5 parallel subagents launched during /legal review. Your specific responsibility is Regulatory & Legal Compliance Verification, which accounts for 20% of the overall Contract Review Score. You determine whether the contract complies with applicable laws and regulations…
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and…
A highly advanced AI agent that functions as a master orchestrator for complex, multi-agent tasks. It analyzes project requirements, defines a team of specialized AI agents, and manages their collaborative workflow to achieve project goals. Use PROACTIVELY for comprehensive project analysis, strategic agent team…
Brunch work is tracked on Linear team FE, project brunch-agent. Linear is the shared record for team visibility, ownership, status, and links to implementation. GitHub pull requests are the review and landing record. The branch mission remains the authority for execution.
A coding-agent workflow for Hermes CN work that spans the Desktop and Core repositories. It requires both repositories to pass checks before code changes begin.
This document is a reference for implementing a new agent provider in Nimbalyst. It is the architectural counterpart to docs/AIPROVIDERTYPES.md (which is end-user / product oriented) and walks through every seam a new agent has to fit through: session start and resume, prompt handling, transcript output, tool calling…
The parameterized subagent the fleet spawns (references/fleet.md). One template, many briefs. Mirrors the discipline of the v1 agents: clear inputs, one job, a strict output contract, a safety envelope, and a length cap.
Use ONLY when explicitly requested by user or when invoked by a protocol in sessions/protocols/. DO NOT use proactively. Reviews code for security vulnerabilities, bugs, performance issues, and adherence to project patterns during context compaction or pre-commit reviews. When using this agent, you must provide files…
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
Generates a new, complete Claude Code sub-agent configuration file from a user's description. Use this to create new agents. Use this Proactively when the user asks you to create a new sub agent.
Agents are the core building blocks of the Video Agent system. They are responsible for processing input messages and generating output messages.
★not rated 1.5k 7mo agoA0 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: