example-harness

Featured

Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/* example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming, repo-maintainer).

AI & Automation 599 stars 70 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# example-harness One-command scaffolding from the 18 **published** `@metaharness/*` example packages — the fastest path from a use-case to a working harness, no template/host flags to remember. Where [`create-harness`](../create-harness/) walks the full wizard, this skill maps a use-case straight onto a published npm wrapper. Each wrapper shells out to `metaharness@latest` with the correct `--template` + `--host` flags, so the result is byte-identical to the full CLI invocation. ## Install ```bash mkdir -p ~/.codex/skills/example-harness curl -fsSL https://raw.githubusercontent.com/ruvnet/agent-harness-generator/main/.codex/skills/example-harness/skill.toml \ -o ~/.codex/skills/example-harness/skill.toml ``` No MCP server needed — the wrapper packages run via `npx`. ## Use ``` /example-harness ``` Codex prompts for the package + a directory name, then runs: ```bash npx --yes @metaharness/<package>@latest <name> ``` ## The 18 packages **Host integrations** (scaffold a workspace wired for one runtime) | Package | Scaffolds | |---|---| | `@metaharness/claude-code` | Claude Code workspace + plugin | | `@metaharness/codex` | OpenAI Codex | | `@metaharness/hermes` | Hermes cli-config | | `@metaharness/pi-dev` | pi.dev AGENTS.md | | `@metaharness/openclaw` | OpenClaw `.openclaw/` | | `@metaharness/rvm` | RVM deployment partition | | `@metaharness/copilot` | VSCode / Copilot `mcp.json` | | `@metaharness/opencode` | OpenCode `.opencode/` | | `@metaharness/github-actions...

Details

Author
ruvnet
Repository
ruvnet/metaharness
Created
2 months ago
Last Updated
2 days ago
Language
TypeScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

create-harness

Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a vertical AI assistant for X".

599 Updated 2 days ago
ruvnet
AI & Automation Listed

init-harness

One-shot initialization of a parallel-terminal Claude Code build harness in a project - a git worktree and branch per terminal, phase checkboxes as the task queue, pinned model/effort per agent, mechanical git-tag gates, hardened read/gate/log hooks, and a SQLite agent-memory shard per terminal. Use when the user says "/init-harness", "init-harness", "initialize the harness", "set up the build harness", "scaffold this project's harness", "bootstrap the agent harness", or drops in a project-context.yml and asks to initialize. Also use when a project needs multi-terminal agent orchestration with gates, or when an existing harness must be verified or repaired (hooks not firing, guards not blocking, .agents drift). Do NOT use for adding a single agent or skill to an existing project.

1 Updated 3 weeks ago
M4NUSH7
AI & Automation Listed

harness-cli

Use when working with other agents or the harness from inside a runner-spawned task — messaging peers on the agentboard, spawning / driving / killing worker agent sessions, delegating one-shot tasks, moving files in or out of a task's worktree, notifying the human operator, or discovering live agents and topics. Also defines the agentboard conventions (handshake, reply topics, trust model). Reply delivery is asynchronous via the inbox hook — never block on wait/dispatch from an agent turn.

0 Updated today
on-keyday