subagents plugins

by Archcore

Spec-driven development and context engineering for AI coding agents, backed by project context in Git.

by Archcore

Spec-driven development and context engineering for AI coding agents, backed by project context in Git.

by Konstantin Aristov

Show Codex subagents in disposable, non-focusing Herdr panes.

by Gustavo Meilus

Design, generate, and run multi-agent AI pipelines — scope-aware, multi-pipeline, spec-driven, write/review-isolated. Codex App/CLI target (Tier 1d: native parallel subagents, up to 6 concurrent).

by NYCU-Chung

An engineering team in a box for Claude Code. 12 specialized subagents (planner, fullstack-engineer, refactor-specialist, migration-engineer, frontend-designer, critic, vuln-verifier, debugger, db-expert, onboarder, tool-expert, web-researcher) plus 15 automation hooks (pre-commit secret scan, MCP health tracking, cost tracking, test runner, branch protection, large file warner, session summary, batch format, design quality, config protection, and more) wired by the P7/P9/P10 methodology with three red lines: closure discipline, fact-driven, exhaustiveness.

by Green-PT

Three reflexive levers that cut agent token cost — less code (YAGNI/stdlib-first), less prose, and denser agent-to-agent handoffs (ESON/compact-JSON). Plus on-demand satellites (review, eco, gain, compress) and a hive of read-only subagents that return compressed handoffs. Auto-intensity lite/full/ultra; correctness and safety-critical paths stay exact.

by Anton Babenko

Use when you want a delegated second opinion or implementation from GPT (Codex), Gemini, Grok (xAI), or OpenRouter (config-driven, 400+ models) - seven expert subagents (Architect, Plan Reviewer, Scope Analyst, Code Reviewer, Security Analyst, Researcher, Debugger) and bundled ask-gpt/ask-gemini/ask-grok/ask-openrouter/ask-all/consensus commands, advisory (read-only) or implementation (write; Grok and OpenRouter are advisory-only).

by gtapps

A personal assistant that lives in your project — memory-driven learning, daily rhythm, idle agency, and operational hygiene for Claude Code

by Lauri Gates

Task-focused agents for test, review, debug, docs, CI, security, refactoring, research, performance, and search-replace — with teammate and subagent role guidance

by thousandflowers

Measures what share of your agent's loaded context is ever actually invoked - skills, MCP servers, subagents, hooks, always-loaded prose - using evidence from your own session transcripts. Then prunes the dead weight, reversibly.

by Oleg

Compound V for Superpowers: triple parallel pre-flight (code archaeology + domain-expert advisor + library/doc validator — Context7 MCP when the session has it attached, WebSearch/WebFetch otherwise), disjoint file partitioning, manifest-driven multi-backend dispatch (Claude + headless Codex + Antigravity + Cursor workers), git-diff scope enforcement, crash-resumable runs, adaptive tier-based routing, epic mode for multi-feature builds, V-memory local-first semantic+lexical recall over docs/superpowers (opt-in pure-python embeddings + a deterministic recall→action bridge), and batched parallel dispatch (Opus default, Sonnet for narrow junior-task carve-out), plus /v:onboard — a project-onboarding command that builds a citation-verified knowledge base + AGENTS.md/CLAUDE.md bridge behind a human gate. Auto-intercepts three transitions: brainstorming → writing-plans → execution; a gated pre-brainstorm recon pass and batched elicitation are guidance the brainstorm follows, not enforced mechanisms.

by Alberto Leal

Install and maintain a "model routing" section in a project's CLAUDE.md that teaches Claude Code which model to use for which work, including delegating to GPT models via the Codex CLI. Use when adding model-picking guidance to CLAUDE.md, setting up Codex/GPT as a delegation target or fallback, or routing subagent and workflow tasks across models by cost, intelligence, and taste.

by Bersabel Tadesse

Four independent, provider-agnostic skills for product specification, code review, spec-driven implementation, and Moss change summaries.

by Bersabel Tadesse

Compatibility manifest for four independent Ottonomous skills: spec, review, build, and Moss change summary.

by Jake Selby

Skills, subagent roles, slash commands and an output style from the Agent Harness checkout, installable on their own.

by Patrick D'appollonio

Implement an agreed plan hands-free: worktrees and cheap executors under TDD with docs updated in the same diff, an item-by-item check against the plan, an adversarial review, and decisions kept where they belong.

by Patrick D'appollonio

Use premium models for judgment while delegating bounded, token-heavy work to cheaper subagents.

by nikitaCodeSave

Designs, bootstraps, audits, and extends a Claude Code harness — the .claude/ directory and root CLAUDE.md. Opinion: under a capable model, less harness yields more productivity.

by Victor Villegas

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

by Victor Villegas

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

by Victor Villegas

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

by Victor Villegas

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

by Victor Villegas

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.

by Victor Villegas

YAGNI enforcement at the harness level for real engineering work — nudges toward the simplest solution and gates against unnecessary dependencies, file sprawl, and unchecked build growth.