mdr, the CLI
One file, Node 18 or newer, no dependencies. Installs an artifact at an exact version into your agent's directory and records its content hash in mdr.lock.
Connect an agent at modelranch.com
curl -fsSL https://staging.markdownregistry.com/install.sh | shPuts mdr in ~/.local/bin. Read it first: /mdr.mjs. Anonymous install counts: mdr add reports the artifact id and your agent type, never file contents or paths; MDR_TELEMETRY=0 turns that off.
Commands
mdr search <query> find artifacts mdr info <owner/repo/name> versions, audit, badge mdr add <owner/repo/name>[@version] install pinned, write mdr.lock (--agent claude|codex|cursor|opencode, --dir PATH, --force) mdr install install everything in mdr.lock at its pinned hash mdr outdated what moved upstream, with the audit grade of the new version mdr diff <owner/repo/name> [from] [to] line diff between two versions mdr update <owner/repo/name> move the pin to the latest version
The lockfile
{
"version": 1,
"registry": "https://staging.markdownregistry.com",
"entries": {
"anthropics/skills/pdf": { "artifact": "art_...", "label": "v1.4.2", "sha256": "...", "commit": "...", "path": ".claude/skills/pdf" }
}
}Questions
How do I install the mdr CLI?
Run curl -fsSL https://markdownregistry.com/install.sh | sh. It places a single dependency-free file that needs Node 18 or newer in ~/.local/bin. You can read the script and the CLI source before running either.
What is mdr.lock?
mdr.lock is the lockfile mdr writes next to your agent files. It records the artifact id, the chosen label, the exact SHA-256 hash and the source commit for every installed artifact, so mdr install reproduces the same bytes on any machine.
How do I update a pinned artifact?
Run mdr outdated to see what moved upstream and the audit grade of the new version, then mdr update owner/repo/name to move the pin. Nothing changes on disk until you update, so upstream edits never reach your agent silently.