Team Harness
Register the team-harness marketplace so one Markdown source for agents and skills syncs to Claude Code, Gemini CLI, and Codex CLI outputs from a shared build pipeline.
Overview
team-harness is a plugin marketplace for the Build phase that distributes a cross-platform harness so Claude Code, Gemini CLI, and Codex CLI share one Markdown-defined agent and skill source.
What is this marketplace?
- Single source agents/ and skills/ Markdown compiled via build parser → validator → assembler → renderer
- Ships dist targets for Claude (CLAUDE.md + plugin.json), Gemini (GEMINI.md + settings.json), and Codex (AGENTS.md + conf
- Bundled agent roles: designer, backend-dev, reviewer, pr-docs with matching skill packs including security deny-rules
- Claude Code registration via extraKnownMarketplaces pointing at github repo siontext/Harness-Marketplace
- npm install plus sync scripts after cloning ~/config/ai/harness style layout documented in README
- Marketplace lists 1 plugin in catalog ingest metadata
- README documents six skill directories and four named agent roles in the harness tree
Community signal: 3 GitHub stars.
What problem does it solve?
Solo builders using multiple AI CLIs waste time reconciling conflicting agent instructions and duplicated skill markdown across platforms.
Who is it for?
Indie teams-of-one who actively use Claude Code plus Gemini CLI or Codex CLI and want one repo-owned harness committed to dist/.
Skip if: Builders who only use a single editor agent with ad-hoc prompts and no appetite to maintain a Node build pipeline.
What do I get? / Deliverables
After clone, npm install, build, and marketplace registration, generated dist/ outputs keep designer, reviewer, and security skills aligned across Claude, Gemini, and Codex.
- Built dist/claude, dist/gemini, and dist/codex agent and skill trees ready to commit
- Registered team-harness marketplace plugin feeding unified designer, backend-dev, reviewer, and pr-docs personas
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Build agent-tooling is the first journey moment you need cross-platform harness files; everything earlier is optional until you standardize how agents work in your repo. Agent-tooling captures SSOT agents (designer, backend-dev, reviewer, pr-docs) and skills (coding-style, architecture, framework, git, security, project) rendered into dist/claude, dist/gemini, and dist/codex.
How it compares
Cross-platform harness generator marketplace, not a lone integration skill or hosted MCP server.
Common Questions / FAQ
Who is Team Harness for?
Developers standardizing agent personas and skills across Claude Code, Gemini CLI, and Codex CLI from one Harness-Marketplace repository.
When should I use Team Harness?
Use it when you are formalizing agent rules—architecture, git, security deny-rules—before scaling AI-assisted commits across multiple CLIs.
How do I add Team Harness to my agent?
Clone siontext/Harness-Marketplace, run npm install and the documented sync/build scripts, then add the Team Harness entry under extraKnownMarketplaces in ~/.claude/settings.json and install the plugin from the marketplace.