Home / jebel-quant / rhiza-claude · plugin/skills/status/SKILL.md · GitHub

status skillB

Name: status
Author: jebel-quant

status is agent-read markdown (skill) from jebel-quant/rhiza-claude: Report this repo's rhiza state — whether the config is valid, and what was actually synced. Read-only. Add --files for a tree of managed files, or --check for upstream drift..

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

You are running `/status` in the **current working directory's repo**.

**A repo's rhiza state has two halves, and this reports both:**

| half | file | question |
| --- | --- | --- |
| **config** | `.rhiza/template.yml` + repo structure | is what we'd sync *from* well-formed? |
| **sync** | `.rhiza/template.lock` | what was actually synced, and when? |

They can disagree in both directions, which is why reporting one without the other
misleads: a freshly `/init`-ed repo has a valid config and **no lock at all**, and a
long-synced repo can have a lock alongside a config someone has since broken by hand.

**This command is a thin wrapper around two bundled scripts** —
`plugin/scripts/validate.py` and `plugin/scripts/status.py`, both deterministic and stdlib-only (no
`rhiza` CLI, no PyYAML). Do **not** re-implement the parsing or gather fields
yourself; run them and relay the output.

Purely descriptive: it **reports; it does not score, fix, or file anything**.

Argument (optional): `$ARGUMENTS` — a path to the repo root to inspect; default is
the current directory.

## 1. Validate the config

`${CLAUDE_PLUGIN_ROOT}` resolves at runtime (**keep the quotes**); in a source
…

Read the whole file at its exact version.

How to install

Latest version

mdr add jebel-quant/rhiza-claude/status@git:20260805.c448d28

Exact content

mdr add jebel-quant/rhiza-claude/status@sha256:9eaf3ac2b321ff80

Pin 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_4g2uqvjq6i6eev7w.svg)](https://markdownregistry.com/a/art_4g2uqvjq6i6eev7w)

1 badge views in 30 days

Versions

version	committed	commit	size	audit
git:20260805.c448d28 latest	2026-08-05	c448d28	4,013 B	B	view

Audit of the latest version

B 16 of 17 checks passed. Deterministic, no model, same answer every run.

fail: Frontmatter declares a name
pass: Frontmatter block present
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4013 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

GitHub

jebel-quant/rhiza-claude · 4 stars · license MIT · pushed 2026-09-23 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_4g2uqvjq6i6eev7w
GET https://markdownregistry.com/api/v1/resolve?ref=jebel-quant/rhiza-claude/status
GET https://markdownregistry.com/api/v1/blob/9eaf3ac2b321ff8016d73aa443e9249e41c8d701eb771966c44d02005d3f1367

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.