harness-subagent

Scaffold and manage subagent definitions across provider configurations in agent-harness.

12|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/madebywild/agent-harness --skill harness-subagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-subagent
Source: https://github.com/madebywild/agent-harness/tree/main/.claude/skills/harness-subagent
Command: npx skills add https://github.com/madebywild/agent-harness --skill harness-subagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage subagent entities in the agent-harness workspace. Invoke this skill when a user wants to define, scaffold, apply, or remove a subagent across Claude Code, OpenAI Codex, or GitHub Copilot.

Core Features & Use Cases

  • Scaffold new subagent sources under .harness/src/subagents and register them in manifest.json
  • Generate provider-specific artifacts for Claude Code, Codex, and Copilot
  • Manage provider overrides and handoffs via override sidecars
  • Synchronize subagents across providers for consistent configuration

Quick Start

Scaffold a new subagent source and generate provider artifacts with a single command.

Frequently Asked Questions about harness-subagent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create subagents that work across Claude Code, Codex, and Copilot?

You can scaffold subagent sources in a canonical directory and generate provider-specific artifacts for Claude Code, OpenAI Codex, and GitHub Copilot. This ensures consistent subagent rendering and management across all configured providers.

What is a canonical subagent source format for managing multiple AI providers?

A canonical subagent source format stores definitions centrally under .harness/src/subagents. It uses override sidecars to apply provider-specific options, synchronizing configurations across different AI coding assistants.

How do I apply provider-specific overrides to a subagent definition?

You apply provider-specific options by using override sidecars alongside the canonical subagent source. This allows you to set specific configurations for Claude Code, Codex, or Copilot without altering the main definition.

Can I manage subagent configurations for GitHub Copilot using a centralized manifest?

Yes, you can register subagent sources in a manifest.json file and generate GitHub Copilot artifacts. This workflow synchronizes subagent configurations across providers from a centralized location.

Does this subagent scaffolding workflow require external dependencies?

No, scaffolding and managing subagent definitions across provider configurations requires no external dependencies. It operates entirely within the agent-harness workspace using source files and override sidecars.

Why synchronize subagent definitions across multiple AI coding providers?

Synchronizing subagents across providers ensures consistent behavior and configuration management. It prevents configuration drift between Claude Code, OpenAI Codex, and GitHub Copilot by using a single canonical source.