Agent Claude Code
Use when adding security scanning to a CI/CD pipeline — configures SAST, DAST, dependency scanning, and container scanning. Part of the cicd-pipeline harness.
100 production-grade multi-agent harnesses for GitHub Copilot CLI
This repository also configures its own agents. See what harness-100-copilot tells them →
Agent Claude Code
Use when adding security scanning to a CI/CD pipeline — configures SAST, DAST, dependency scanning, and container scanning. Part of the cicd-pipeline harness.
Agent Claude Code
Use when performing architecture review of code — evaluates design patterns, SOLID principles, dependency management, and coupling. Part of the code-reviewer harness.
Agent Claude Code
Use when performing performance review of code — analyzes algorithmic complexity, memory usage, concurrency issues, and database query efficiency. Part of the code-reviewer harness.
Agent Claude Code
Use when synthesizing multi-domain code review findings into a final prioritized report. Reads outputs from style-inspector, security-analyst, performance-analyst, and architecture-reviewer. Part of the code-reviewer harness.
Agent Claude Code
Use when performing security review of code — identifies vulnerabilities, injection risks, authentication flaws, and data exposure. Part of the code-reviewer harness.
Agent Claude Code
Use when performing code style review — inspects conventions, formatting, naming, readability, and consistency. Part of the code-reviewer harness.
Agent Claude Code
Use when analyzing legacy codebases to document undocumented code, identify anti-patterns, map dependencies, and detect tech debt hotspots. Part of the legacy-modernizer harness.
Agent Claude Code
Use when performing final review of a legacy modernization plan — validates completeness, identifies gaps across all prior outputs, and produces a go/no-go decision with conditions. Part of the legacy-modernizer harness.
Agent Claude Code
Use when creating a modernization roadmap for a legacy system — produces prioritized migration phases, technology selection rationale, and a strangler fig implementation strategy. Part of the legacy-modernizer harness.
Agent Claude Code
Use when producing incremental refactoring recommendations for a legacy system — provides before/after code examples, dependency injection introduction, interface extraction, and test harness installation guidance. Part of the legacy-modernizer harness.
Agent Claude Code
Use when assessing migration risks for a legacy modernization project — identifies breaking changes, business continuity risks, and testing coverage gaps. Part of the legacy-modernizer harness.
Agent Claude Code
Use when designing API gateway and service mesh configuration — defines routing rules, load balancing algorithms, circuit breakers, rate limiting, and observability for a microservice system. Part of the microservice-designer harness.
Agent Claude Code
Use when designing data architecture for microservices — defines per-service database topology, CQRS/Event Sourcing strategy, saga patterns for distributed transactions, and eventual consistency contracts. Part of the microservice-designer harness.
Agent Claude Code
Use when creating Kubernetes deployment plans for microservices — produces Helm chart structures, resource limit configurations, HPA policies, PodDisruptionBudgets, and GitOps workflow definitions. Part of the microservice-designer harness.
Agent Claude Code
Use when performing domain-driven design analysis — models bounded contexts, aggregate roots, domain events, and context maps for a microservice system. Part of the microservice-designer harness.
Agent Claude Code
Use when designing individual microservices from a domain model — defines service boundaries, API contracts, data ownership, and inter-service communication patterns. Part of the microservice-designer harness.
Agent Claude Code
Use when writing end-to-end tests for user journeys — generates Playwright or Cypress tests using Page Object Model, data-testid selectors, and fixture patterns to cover critical user flows. Part of the test-automation harness.
Agent Claude Code
Use when writing integration tests for databases, external APIs, or service boundaries — generates tests using test containers, API contract testing, and transaction rollback patterns. Part of the test-automation harness.
Agent Claude Code
Use when reviewing a completed test suite — assesses coverage gaps, detects flaky test patterns, scores test quality, and produces a final actionable report. Part of the test-automation harness.
Agent Claude Code
Use when planning a comprehensive test strategy — analyzes tech stack, existing coverage, and risk factors to define test pyramid allocation, coverage targets, and testing priorities. Part of the test-automation harness.
Agent Claude Code
Use when writing unit tests for a codebase — generates isolated unit tests using AAA pattern, defines mocking strategy, and maximizes code coverage for individual functions and classes. Part of the test-automation harness.
Agent Claude Code
Use when creating a prioritized action plan from a completed incident postmortem — produces prevention tasks, runbook updates, monitoring improvements, and follow-up owners with due dates. Part of the incident-postmortem harness.
Agent Claude Code
Use when quantifying the impact of an incident — calculates SLO violations, error budget burn rate, MTTR, customer impact tiers, and business cost. Part of the incident-postmortem harness.
Agent Claude Code
Use when reconstructing an incident timeline — correlates logs, alerts, and on-call notes to produce a precise chronological sequence of events. Part of the incident-postmortem harness.
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: