Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Jebel-Quant/rhiza-claude/plugin install rhizaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jebel-quant/rhiza-claude/status)<a href="https://agentmods.dev/skills/jebel-quant/rhiza-claude/status"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jebel-quant/rhiza-claude/status"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.01026 |
| Opus 5 | $0.00020 | $0.00513 |
| Sonnet 5 | $0.00008 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
checkout it's empty, so fall back to the repo-relative path.
uv run --python 3.12 --no-project python "${CLAUDE_PLUGIN_ROOT}/scripts/validate.py" $ARGUMENTS
It checks more than the file: that the target is a git repo, that it has the expected
language-specific structure (a pyproject.toml is required for Python), that
template.yml exists and parses, and that its fields are present and well-typed. It
exits non-zero on any of those failing — that's its contract as a gate, so it stays
usable in CI. Here, treat a failure as a finding to report, not a reason to
stop: still run step 2, because a broken config alongside a good lock is exactly the
situation worth surfacing. Lead the report with the validation failure.
If there's no template.yml at all, the repo isn't rhiza-managed. Say so and point at
/rhiza:init; skip step 2.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 87 lines · 40 tokens per session scan A 9eaf3ac2b321
status is a skill published in the GitHub repository Jebel-Quant/rhiza-claude (4 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,026 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
detect-task
Internal skill for commands. Detect the active task (any tracker adapter) from the task-state file / git branch name. Do not trigger on user conversation - only when commands need task detection.
loop-bb-pr
A command that prepares a repeating check for a Bitbucket pull request. A pull request is a request to review and merge code changes into a project.
take-task
A workflow for claiming a tracker task and preparing the development branch for it. It verifies the task, marks it as in progress, checks for uncommitted changes, and handles branch setup according to the task state.
session-boundary
Internal skill for commands. Resolve and VALIDATE this branch's session boundary - the ref a session's commit range is measured from - and report how much it can be trusted. Do not trigger on user conversation; only when a command needs the session range.
commit
A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.