cross-host-rig-commands SKILL.md skillA
cross-host-rig-commands from mvschwarz/openrig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mvschwarz/openrig/cross-host-rig-commands@git:20261107.c5a2be5Pins git:20261107.c5a2be5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mvschwarz/openrig
- Path
skills/_canonical/core/cross-host-rig-commands/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261107.c5a2be5, committed Nov 7, 2026
- First version recorded
- Aug 26, 2026
- Size
- 5,939 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.
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
# Cross-host rig commands
Use a registered host address and the entry's declared transport. SSH entries
run a remote CLI through a single-hop shell; HTTP entries use the remote daemon.
These paths have different prerequisites and command coverage. Check the exact
command's help and the target installation before a consequential operation.
## Choose and inspect the destination
`rig host list` shows registered hosts. `rig host add --help` describes registry
writes; `rig host doctor --help` describes reachability checks. Inspect the
configured OpenRig home rather than assuming the default `~/.openrig/hosts.yaml`.
Registry changes affect later routing, so make them within the requested scope.
```yaml
hosts:
- id: test-vm
transport: ssh
target: test-vm.local
user: example-user
- id: remote-dev
transport: http
url: http://remote-dev.example:7433
bearer_env: REMOTE_RIG_TOKEN
```
The registry requires a hosts array, unique non-empty ids and a supported
transport. SSH needs a non-empty target; user and notes are optional. HTTP needs
a URL and accepts at most one of bearer_env or bearer_file. Omitting both is
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_iklonxuwahklzd2d/da0a31fa551a0602ff2ed11ce0729dcb68bc37e9d8f2867b94c48bdc754b22a2.json
Then /plugin install cross-host-rig-commands@markdownregistry-iklonxuwahklzd2d in Claude Code. It installs git:20261107.c5a2be5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/cross-host-rig-commands@sha256:da0a31fa551a0602The line at the top of this page pins the label git:20261107.c5a2be5, 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_iklonxuwahklzd2d)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mvschwarz/openrig/cross-host-rig-commands since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of cross-host-rig-commands from somewhere else? Ask it: where did my cross-host-rig-commands come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 7 versions of this file, between Aug 26, 2026 and Nov 7, 2026, about one every 12 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261107.c5a2be5 latest | 2026-11-07 | c5a2be5 | 5,939 B | A | view · diff |
| git:20261009.98f1cfc | 2026-10-09 | 98f1cfc | 5,546 B | A | view · diff |
| git:20260907.386e515 | 2026-09-07 | 386e515 | 5,376 B | A | view · diff |
| git:20260830.0ac75f4 | 2026-08-30 | 0ac75f4 | 8,916 B | A | view · diff |
| git:20260830.c08b556 | 2026-08-30 | c08b556 | 9,355 B | A | view · diff |
| git:20260826.4b9ec17 | 2026-08-26 | 4b9ec17 | 9,350 B | A | view · diff |
| git:20260826.bdc404f | 2026-08-26 | bdc404f | 8,886 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/cross-host-rig-commands/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (5939 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
mvschwarz/openrig · 8,889 stars · license Apache-2.0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iklonxuwahklzd2d GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/cross-host-rig-commands GET https://markdownregistry.com/api/v1/blob/da0a31fa551a0602ff2ed11ce0729dcb68bc37e9d8f2867b94c48bdc754b22a2
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.
More from mvschwarz/openrig
Every file in mvschwarz/openrig