Agent Claude Code
Use when analyzing the root cause of an incident — applies 5 Whys and Fishbone (Ishikawa) methodology to determine underlying systemic causes. Part of the incident-postmortem 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 analyzing the root cause of an incident — applies 5 Whys and Fishbone (Ishikawa) methodology to determine underlying systemic causes. Part of the incident-postmortem harness.
Agent Claude Code
Use when designing cloud infrastructure architecture — produces multi-region topology, VPC/subnet design, security zone layout, and cost estimation framework. Part of the infra-as-code harness.
Agent Claude Code
Use when reviewing completed infrastructure-as-code for cost optimization, resource right-sizing, compliance checking, and production readiness. Part of the infra-as-code harness.
Agent Claude Code
Use when creating Kubernetes manifests for application deployment — generates Deployments, Services, Ingress, RBAC, namespaces, HPA, and resource quotas. Part of the infra-as-code harness.
Agent Claude Code
Use when hardening cloud infrastructure security — applies IAM least privilege, network policies, encryption at rest/transit, Pod Security Standards, and secrets management. Part of the infra-as-code harness.
Agent Claude Code
Use when creating or reviewing Terraform infrastructure code — generates module structure, resource definitions, remote state configuration, and workspace-per-environment pattern. Part of the infra-as-code harness.
Agent Claude Code
Use when designing the data ingestion layer — configures source connectors, schema registry, change data capture (CDC) patterns, watermarking for late data, and exactly-once semantics. Part of the data-pipeline harness.
Agent Claude Code
Use when designing a data pipeline architecture — selects batch vs streaming approach, chooses technology stack, defines SLA tiers, and produces the overall data flow design. Part of the data-pipeline harness.
Agent Claude Code
Use when configuring data quality monitoring — sets up Great Expectations suites, defines data contracts, configures column-level lineage tracking, and implements alerting for data quality failures. Part of the data-pipeline harness.
Agent Claude Code
Use when implementing ETL/ELT transformation logic — creates dbt models (staging/intermediate/mart), Spark jobs, incremental processing patterns, and data quality rules at the transformation layer. Part of the data-pipeline harness.
Agent Claude Code
Use when performing static code security analysis (SAST) — identifies injection flaws, authentication issues, cryptographic misuse, hardcoded secrets, and OWASP Top 10 vulnerabilities at the source code level. Part of the security-audit harness.
Agent Claude Code
Use when reviewing security configuration — checks for secrets exposure, TLS settings, IAM policies, firewall rules, Docker/Kubernetes security posture, and cloud service hardening. Part of the security-audit harness.
Agent Claude Code
Use when performing software composition analysis (SCA) — audits third-party dependencies for CVEs, evaluates license compatibility, and identifies supply chain risks including dependency confusion and transitive vulnerabilities. Part of the security-audit harness.
Agent Claude Code
Use when synthesizing security audit findings into a comprehensive report — aggregates threat model, code analysis, dependency, and configuration findings; applies CVSS scoring; produces a prioritized remediation plan and executive summary. Part of the security-audit harness.
Agent Claude Code
Use when performing threat modeling for a codebase or system — applies STRIDE methodology, identifies attack surfaces, maps trust boundaries, and produces a structured threat model. Part of the security-audit harness.
Agent Claude Code
Use when optimizing backend API performance -- reduces API response latency, identifies and fixes N+1 queries, implements Redis caching strategies, and right-sizes connection pools. Part of the performance-optimizer harness.
Agent Claude Code
Use when optimizing frontend performance — improves Core Web Vitals (LCP, INP, CLS), reduces JavaScript bundle size, implements lazy loading, optimizes images, and configures CDN caching. Part of the performance-optimizer harness.
Agent Claude Code
Use when tuning infrastructure performance parameters -- configures Kubernetes HPA/VPA, CDN cache hit ratio, database connection pooling (PgBouncer), auto-scaling warm-up strategies, and resource limits. Part of the performance-optimizer harness.
Agent Claude Code
Use when validating performance improvements and producing a final performance assessment -- compares before/after metrics, calculates ROI, defines performance budgets, and provides SLO recommendations. Part of the performance-optimizer harness.
Agent Claude Code
Use when identifying performance bottlenecks in an application or system -- profiles CPU, memory, I/O, and network usage to produce a baseline metrics report and prioritized bottleneck map. Part of the performance-optimizer harness.
Agent Claude Code
Use when configuring CI/CD pipelines for an open source project — sets up GitHub Actions workflows for testing, releasing, and automating semantic versioning. Part of the open-source-launcher harness.
Agent Claude Code
Use when building the community and launch plan for an open source project — creates issue templates, PR templates, discussion forums config, roadmap, and first-good-issue labeling strategy. Part of the open-source-launcher harness.
Agent Claude Code
Use when defining the open source strategy for a project — selects the appropriate license, governance model, and competitive positioning. Part of the open-source-launcher 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: