harness-reinstall SKILL.md skillA
harness-reinstall from smars-bin-hu/copilot-agentic-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add smars-bin-hu/copilot-agentic-harness/harness-reinstall@git:20261102.d95f023Pins git:20261102.d95f023 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- smars-bin-hu/copilot-agentic-harness
- Path
.github/skills/harness-reinstall/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261102.d95f023, committed Nov 2, 2026
- First version recorded
- Oct 20, 2026
- Size
- 5,285 bytes
- Repository stars
- 3
- License
- Apache-2.0
After the user got a new copy of the harness (an upgrade, a fresh clone), carry what only their machine holds from the old copy to the new one: tasks, reports, goals, .harness/runtime (which session holds which task, the logs, the repository map cache), *.override.json, the knowledge base. Nothing is overwritten; doctor runs after. Use when the user types /harness-reinstall, or says upgrade the harness, reinstall, new copy, moved the harness, lost my tasks, the board shows nothing after…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Reinstall: carry the old copy over to the new one `harness reinstall --from <old copy>` copies what git does not keep from the old copy to this one: the person's tasks, reports, goals, `.harness/runtime/`, `*.override.json` and the knowledge base. The old copy is not changed. Your part is one question, a dry run the user reads, and the check after. ## When to Use This Skill - The user has a new copy of the harness (an upgrade, a fresh clone, a new folder) and an old one with their work. - After a hand copy that missed something: the board shows nothing for a task, a chat no longer finds its task, a report has no time, the repository map is gone. **Who starts it: auto.** The dry run only reads. The copy itself only a person at a terminal can run, so you cannot go too far. No task is opened for it: it is upkeep of the harness. ## Step-by-Step Workflows 1. **Ask for one thing: the full path of the old copy** (the folder that holds `.harness/` and `AGENTS.md`). It must be a different folder from this repository. 2. **Dry run.** Run `harness reinstall --from "<path>" --json`. Nothing is written. Show the user, short: …
Read the whole file at its exact version.
How to install
mdr add smars-bin-hu/copilot-agentic-harness/harness-reinstall@sha256:2d2af96015048867The line at the top of this page pins the label git:20261102.d95f023, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jigdlfkheyniezhv)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 20, 2026 and Nov 2, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261102.d95f023 latest | 2026-11-02 | d95f023 | 5,285 B | A | view · diff |
| git:20261102.9aa7feb | 2026-11-02 | 9aa7feb | 5,180 B | A | view · diff |
| git:20261030.99fa246 | 2026-10-30 | 99fa246 | 5,182 B | A | view · diff |
| git:20261020.16293b1 | 2026-10-20 | 16293b1 | 4,940 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5285 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
smars-bin-hu/copilot-agentic-harness · 3 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jigdlfkheyniezhv GET https://markdownregistry.com/api/v1/resolve?ref=smars-bin-hu/copilot-agentic-harness/harness-reinstall GET https://markdownregistry.com/api/v1/blob/2d2af960150488672f48d9e30a04e0164ebd28caa749630609e436a33b19cd3d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.