Use this agent when performing brownfield analysis on an existing codebase, onboarding to a new project, generating codebase documentation, or understanding legacy code. Examples: Context: The user wants to understand an existing codebase they are joining or inheriting. user: "I need to understand this existing…
Create, refine, and push reusable skills to the SkillNote registry. Use when repeated instructions are detected, user says "create a skill", "save this pattern", "turn this into a skill", or during session retrospective.
Product-technical alignment reviewer. Spawned in a tmux pane via OpenAI Codex CLI with zero inherited context. Cross-provider isolation (GPT-5.5 vs Lead's Claude) layered on top of zero context inheritance. Reads product-spec and tech-spec independently to verify the technical approach actually implements what the…
Use this agent when you need to verify code quality after writing or modifying code. This includes running TypeScript type checking to catch type errors before committing. The agent should be called after completing a logical chunk of code implementation.\n\nExamples:\n\n \nContext: User has just finished implementing…
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Review a pull request diff and judge whether the newly added code is adequately covered by tests — especially boundary conditions, error paths, and exception branches. Output a short "covered / uncovered" table with specific line-level gaps. Use this agent on PRs that add behavior. It supplements Codex / CodeRabbit…
Queries NotebookLM notebooks in Chrome to extract responses. Use when the orchestrating skill provides a NotebookLM URL and question. The notebooklm-manager skill resolves notebook names to URLs before invoking this agent.
Review a generated report for narrative coherence, internal contradictions, and unsupported assumptions — with no access to source data or analysis context. Delegated by the report generation workflow as an optional quality gate.
Festival task execution specialist. Use when working through festival tasks, marking completion, committing with traceability, managing task state (completed/blocked/reset), and advancing through sequences. Follows the fest next → work → complete → commit loop.
Festival planning specialist. Use when creating new festivals, designing phase/sequence/task structure, choosing festival and phase types, scaffolding from plans, and validating festival structure. Expert in the Festival Methodology hierarchy and naming conventions.
Festival is files and two CLIs the agent loop actually touches: fest and camp, installed and kept current by a third tool, festival. It works with any agent that can run shell commands and read files, which is nearly all of them. There is no plugin to install for the core loop: the agent runs fest next, reads the task…
Meta-agent that decomposes tasks, delegates to specialized agents, and maximizes parallel execution. Use for complex multi-step tasks requiring coordination.
Companion to calibration-contract.md, which governs the base statistical scorer. The semantic layer (feature semantic, crate crates/argot-rules-semantic/) calibrates itself separately at fit time; this file records the invariants a contributor must not break.
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences.
★not rated 47 12d agoA40 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: