version-control skillA
version-control is agent-read markdown (skill) from gke-labs/kube-agents: Read and change a hosted repository through forge-neutral verbs. Version control here is abstracted — remote operations go through vcs.py, local operations use a credential-free VCS binary on a working copy that vcs.py puts on disk. Covers history, file modes, proposals and issues, so no forge CLI is needed..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# version-control - remote operations through vcs.py, local operations with git Version control here is **abstracted**. Everything is one of two things, and getting an operation into the right half is most of using this skill. **Remote operations — anything that crosses the network or spends a credential.** These go through `scripts/vcs.py`, which speaks to a broker in another container. Only the broker holds the credential; nothing here does. The remote verbs are exactly these: `capabilities`, `clone`, `publish`, `proposal create|list|view|comment`, `issue create|list|view|comment`. **Local operations — everything else.** `clone` unpacks a real working copy onto this filesystem and prints its `path`. Inside it, use the local git, which is `/opt/vcs/libexec/git`. Call it by that path, or through a variable you export once — `export G=/opt/vcs/libexec/git`, then `$G log`, `$G show`, `$G blame`, `$G grep`, `$G diff`, `$G status`, `$G branch`, `$G commit`, `$G ls-files --stage` — and every read works as you expect. Do **not** define a shell alias for it: each command you run here arrives in a fresh non-interactive shell, which never expands aliases, so an aliased `git` …
Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/version-control@git:20260915.aacf05fmdr add gke-labs/kube-agents/version-control@sha256:d196c23a9c29fa16Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ptt67lttnmde6lt5)
1 badge views in 30 days
Versions
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 (12858 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
gke-labs/kube-agents · 64 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ptt67lttnmde6lt5 GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/version-control GET https://markdownregistry.com/api/v1/blob/d196c23a9c29fa16243889747f9ff6d96944f3249edbf8c7fb2db76a900a2a32
Your agent 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.