35,518 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
A project-governance method for taking a new or existing product toward a production-ready minimum viable product (MVP). It provides planning levels, decision records, risk tracking, audits, and reusable templates for solo developers or small teams.
Main-agent planning trio (/ac:plan, /ac:execute, /ac:wisdom) with autonomous execution mode plus setup, init, commit commands and skill, agent, command, rule, CLAUDE.md creator skills. Two hooks back the workflow: SessionStart for twin-skill and resume, PreCompact for state preservation.
★not rated 2 4mo agoA
tokens not measured
originalMIT
Installable Claude Code plugin packaging a document-driven delivery SOP, dual-model collaboration protocol, pluggable review MCP bridge (codex | claude | manual), tiered subagents, skills, and doc scaffolding. Install, then run /sop-init to adopt the workflow in any repo.
★not rated 2
changed 6d agoA
tokens not measured
originalMIT
A planning skill for connecting related business-page nodes. It combines links within a page, relationships between pages, and feature points into connection units for later agent work.
Shared catalog of specialized Crew roles, design/writing crafts, project standards and crew.json. Claude Code commands and Codex skills use the same canonical procedures, with host-specific hook adapters.
★not rated 2
changed 6d agoA
tokens not measured
originalMIT
A bounded autonomous feature-development workflow in which Claude orchestrates implementation and Codex independently enhances, plans, and reviews the work.
★not rated 2 3mo agoA
tokens not measured
originalMIT
Multi-turn planning system for creating high-quality implementation designs. Two AI agents (Architect and Reviewer) collaborate through iterative refinement until consensus.
Structured feature planning workflow: interrogate the developer with hard, codebase-informed questions until requirements are crystal clear, then produce PLAN.md and DECISIONS.md. Use when planning a feature, designing a feature, "how should we build this", "let's plan", "I want to build X", or any request that needs…
Orchestration harness for iterative delivery. Runs a Plan→Implement→Evaluate→Analyze loop with locked rubric, failure routing, optional cron scheduling, and trace emission for skill evolution. Pure orchestration — no domain knowledge. Auto-detects delivery vs workflow improvement. Plans parallel implementation lanes…
Orquestador principal de la arquitectura multi-agente. Descompone tareas en dominios, rutea a leads especializados, maneja fast-lane para respuestas directas, y sintetiza resultados de múltiples agentes. Se activa cuando el usuario quiere usar el sistema multi-agente completo.
Command: /boss.plan Purpose: Create a factory plan from a specification, orchestrating pre-defined agents through dependency stages Agent: Boss (Human coordination agent).
Guide the user through a comprehensive spec-driven development workflow for feature requirements gathering and implementation planning based on $ARGUMENTS using the specware tool.
Write project specifications (SPECIFICATIONS.md) intended for AI implementation: a staged, decision-centric process where the user arbitrates every decision — intake and exploration, structured drafting under the must/should/facts contract, cold subagent review rounds, premise challenges of foundational decisions, and…
Use whenever designing, reviewing, refactoring, or evolving the STRUCTURE of a codebase — module boundaries, layering, where new code should live, naming a package or service, an architecture-worthy decision, or auditing existing structure. Triggers on phrases like "design the architecture", "where should this live"…
A setup guide for starting Vibe Code, a project evaluation tool, in either a new folder or an existing code project. It checks the project, asks setup questions, creates initial files, and can import its history.
Staged orchestration for genuinely multi-stage builds — stage map, warm implementer / fresh adversarial verifier, witnessed-red TDD, re-verify on every change. Builds on the always-on operating discipline in /.claude/CLAUDE.md (verify by re-execution, [confirmed]/[inferred] labeling, cost/blast gating), which applies…
Domain-Driven Design end to end — strategic subdomain classification and context mapping, tactical pattern choice, and implementation conventions for aggregates, value objects, and events.
Inception wizard (50 questions, 9 categories) creating CLAUDE.md, speckit constitution, design system, and project brief. Use when starting a new project, brainstorming an idea, or bootstrapping a repo. Triggers: new project, inception, bootstrap.
Orchestrate projects too large or complex for one reliable agent context. Use only when explicitly invoked to define correctness before implementation, decompose work into bounded features for fresh workers, externalize shared state, and drive independent milestone validation until the mission passes or reaches a…
Complete CLI reference for hopper: lode management, waiting, diagnostics, status reporting. Covers external coordination and in-lode usage. TRIGGER: hop implement, hop submit, hop list, hop wait, hop lode, hop project, hop config: creating a scope, checking lode status, reviewing lode output.
★not rated 2
changed 5d agoA67 tokens
AGPL-3.0
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: