Tsed CLI
tsedio/tsed
Scaffolds Ts.ED v8 projects and generates files with the Ts.ED CLI v7, through its MCP server (tools set-workspace, init-project, list-templates, get-template, generate-file) or the tsed binary…
Drift detection + apply for a scaffolded harness. An agent skill from ruvnet/metaharness.
Install Upgrade Harness
$ npx skills add ruvnet/metaharness --skill upgrade-harness -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ruvnet/metaharness upgrade-harness --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude-plugin/skills/upgrade-harness .claude/skills/upgrade-harness && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "upgrade-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/upgrade-harness into .claude/skills/upgrade-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-harness", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/upgrade-harnessType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ruvnet/metaharness --skill upgrade-harness -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ruvnet/metaharness upgrade-harness --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude-plugin/skills/upgrade-harness .agents/skills/upgrade-harness && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "upgrade-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/upgrade-harness into .agents/skills/upgrade-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-harness", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruvnet/metaharness --skill upgrade-harness -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ruvnet/metaharness upgrade-harness --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude-plugin/skills/upgrade-harness .cursor/skills/upgrade-harness && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "upgrade-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/upgrade-harness into .cursor/skills/upgrade-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-harness", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ruvnet/metaharness.git --path .claude-plugin/skills/upgrade-harness--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ruvnet/metaharness --skill upgrade-harness -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ruvnet/metaharness upgrade-harness --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude-plugin/skills/upgrade-harness .gemini/skills/upgrade-harness && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "upgrade-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/upgrade-harness into .gemini/skills/upgrade-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-harness", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ruvnet/metaharness upgrade-harnessInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ruvnet/metaharness --skill upgrade-harness -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude-plugin/skills/upgrade-harness .github/skills/upgrade-harness && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "upgrade-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/upgrade-harness into .github/skills/upgrade-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-harness", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruvnet/metaharness --skill upgrade-harness -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ruvnet/metaharness upgrade-harness --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude-plugin/skills/upgrade-harness .opencode/skills/upgrade-harness && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "upgrade-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/upgrade-harness into .opencode/skills/upgrade-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-harness", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
upgrade-harness- GitHub stars
- 694
- Token cost
- ~497 tokens
- SKILL.md length
- 151 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Drift detection + apply for a scaffolded harness. An agent skill from ruvnet/metaharness.
- Tasks that involve Project scaffolding
- SKILL.md covers What it does, Usage from Codex, Equivalent CLI and Lifecycle position, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve GitOps
What it does
Upgrade Harness is an agent skill from ruvnet/metaharness. Drift detection + apply for a scaffolded harness. Re-renders the template with the same vars, computes added/removed/changed file plan, and applies with Git-style conflict markers or .rej files. Default is dry-run.
Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Project scaffolding and GitOps. It works with Git and Model Context Protocol. The repository describes itself as: 🛠️ The meta-harness for AI agents — scaffold your own focused, branded agent harness with its own npx CLI, MCP server, memory, learning loop, and witness-signed releases. Works… The licence is MIT.
When your agent uses it
- Tasks that involve Project scaffolding
- Tasks that involve GitOps
Example prompts
- “/upgrade-harness”
What it can do on your machine
Read from SKILL.md and the folder at commit ea287d6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Upgrade Harness loads about 497 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 151 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ruvnet/metaharness at commit ea287d6, republished under its MIT licence (© ruvnet). 151 words, ~497 tokens.
Download SKILL.mdSave it as
.claude/skills/upgrade-harness/SKILL.md (or your agent's skills folder).- name
- upgrade-harness
- description
- Drift detection + apply for a scaffolded harness. Re-renders the template with the same vars, computes added/removed/changed file plan, and applies with Git-style conflict markers or .rej files. Default is dry-run.
upgrade-harness
Codex skill: drift detection + apply for a scaffolded harness.
What it does
Re-renders the template that produced the harness against the current generator version, using the same vars the original scaffold used. Computes a 3-bucket plan:
| Bucket | Meaning |
|---|---|
| added | upstream template now has files the harness doesn't |
| removed | upstream template no longer has files the harness does |
| changed | upstream and harness differ; sub-classified clean vs conflict |
A clean change means the harness's version equals the original generation — apply safely. A conflict means the user edited the file post-scaffold; the apply step writes either Git-style inline markers or a .rej sidecar for manual merge.
Usage from Codex
/upgrade-harness # dry-run on cwd
/upgrade-harness path=./my-harness
/upgrade-harness path=./my-harness apply=true
/upgrade-harness path=./my-harness apply=true conflict=rejEquivalent CLI
harness upgrade ./my-harness # dry-run
harness upgrade ./my-harness --apply # apply, inline conflicts
harness upgrade ./my-harness --apply --conflict=rej # apply, .rej sidecarsLifecycle position
scaffold (create-agent-harness)
↓
edit (you)
↓
upgrade (this skill) <- catches up to the latest template
↓
sign / verify / publishExit codes
| Code | Meaning |
|---|---|
| 0 | No drift OR clean apply (no conflicts) |
| 1 | Unresolved conflicts after apply, OR not a generated harness, OR template missing |
| 2 | Bad --conflict= value |
CI workflows can gate on exit 1 to flag unresolved conflicts.
© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude-plugin/skills/upgrade-harness of ruvnet/metaharness.
Open the folder on GitHubat commit ea287d6
Compare with similar skills
Upgrade Harness next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Upgrade Harness this skillruvnet/metaharness | 694 | — | ~497 | Automated safety check: Pass | MIT | |
| Tsed CLItsedio/tsed | 3.1k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Brain Bootstrapmindmuxai/brain.md | 566 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Zizkadb Dev SetupZIZKA-AI-SL/ZizkaDB | 125 | — | ~535 | Automated safety check: Notes | Custom licence | |
| Releasetractorjuice/arc-kit | 2.3k | — | ~3k | Automated safety check: Pass | Custom licence | |
| Zizkadb ReleaseZIZKA-AI-SL/ZizkaDB | 125 | — | ~399 | Automated safety check: Pass | Custom licence |
Similar skills
Brain Bootstrap
mindmuxai/brain.md
Seed a freshly-scaffolded brain with real project knowledge — on an existing (brownfield) project read the code, docs, and git log to draft the six root pages and capture key historical decisions…
Zizkadb Dev Setup
ZIZKA-AI-SL/ZizkaDB
Set up and start the local ZizkaDB development stack. An agent skill from ZIZKA-AI-SL/ZizkaDB.
Release
tractorjuice/arc-kit
Cut a new ArcKit release — bump versions in lockstep, regenerate non-Claude formats, validate plugin/marketplace agreement, tag, and push to standalone repos.
Zizkadb Release
ZIZKA-AI-SL/ZizkaDB
Bumps versions, runs pre-push verification, and publishes ZizkaDB SDK and MCP packages.
GitHub
swarmclawai/swarmclaw
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.
More from ruvnet/metaharness
All 14 skills in this repoCreate Harness
ruvnet/metaharness
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.
Compare Harnesses
ruvnet/metaharness
Diff two scaffolded harnesses (ADR-031). An agent skill from ruvnet/metaharness.
Diag Harness
ruvnet/metaharness
Kernel-version skew check (ADR-027). An agent skill from ruvnet/metaharness.
Example Harness
ruvnet/metaharness
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…
Oia Manifest
ruvnet/metaharness
Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture.
Repo Genome
ruvnet/metaharness
7-section readiness scorecard for a LOCAL repo. An agent skill from ruvnet/metaharness.
Related
Works with
Categories
Questions about Upgrade Harness
What does Upgrade Harness do?
Drift detection + apply for a scaffolded harness. An agent skill from ruvnet/metaharness. Upgrade Harness is an agent skill from ruvnet/metaharness. Drift detection + apply for a scaffolded harness.
When should I use Upgrade Harness?
Upgrade Harness fits situations like: tasks that involve Project scaffolding; tasks that involve GitOps.
How do I install Upgrade Harness in Claude Code?
Run `npx skills add ruvnet/metaharness --skill upgrade-harness -a claude-code`. Or copy the skill folder (.claude-plugin/skills/upgrade-harness in ruvnet/metaharness) into .claude/skills/upgrade-harness in your project. Claude Code loads it when a task matches its description.
How do I install Upgrade Harness in Codex?
Run `npx skills add ruvnet/metaharness --skill upgrade-harness -a codex`. Or copy the skill folder (.claude-plugin/skills/upgrade-harness in ruvnet/metaharness) into .agents/skills/upgrade-harness in your project. Codex loads it when a task matches its description.
Can I use Upgrade Harness in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/metaharness --skill upgrade-harness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/upgrade-harness, .gemini/skills/upgrade-harness, .github/skills/upgrade-harness and .opencode/skills/upgrade-harness in your project.
What does Upgrade Harness need to run?
SKILL.md names no scripts, command-line tools or credentials: Upgrade Harness is instructions for the agent only.
Does Upgrade Harness access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Upgrade Harness safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Upgrade Harness use?
Upgrade Harness is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Upgrade Harness use?
About 497 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Upgrade Harness?
Skills that share tags, products or a category with Upgrade Harness: Tsed CLI (tsedio/tsed, 3.1k stars), Brain Bootstrap (mindmuxai/brain.md, 566 stars), Zizkadb Dev Setup (ZIZKA-AI-SL/ZizkaDB, 125 stars) and Release (tractorjuice/arc-kit, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Upgrade Harness?
ruvnet (a GitHub user) maintains it in ruvnet/metaharness, which has 694 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.
Source: ruvnet/metaharness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.