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/remote)<a href="https://agentmods.dev/skills/jebel-quant/rhiza-claude/remote"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/remote.svg" alt="Measured on agentmods" 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.00051 | $0.02513 |
| Opus 5 | $0.00026 | $0.01256 |
| Sonnet 5 | $0.00010 | $0.00503 |
| Haiku 4.5 | $0.00005 | $0.00251 |
Grade A, and why
remote 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 7d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /remote in the current working directory's repo.
The gap this closes. /rhiza:quality files findings as issues, those issues become
branches, and the branches become requests that were green when they left. Local green
and origin green are different claims, and only the second one merges. A suite that
passes on a warm cache with the author's toolchain says nothing about a matrix leg on
another OS, a lockfile the runner resolves differently, a gate that exists only in the
workflow, or a network call that is rate-limited today.
This command asks the forge what actually happened, and then fixes what it finds. It is the only rhiza command that reads CI.
One rule outranks everything below: never make a check green by weakening it.
Deleting the failing test, lowering the threshold, narrowing the matrix, adding
continue-on-error or --ignore — each of those turns a red build into a green one
without changing what is broken, and the next person inherits both the defect and a gate
that will never mention it again. If the honest fix is out of reach, say so, leave the
build red, and report why. A red request is information; a falsely green one is not.
0. Preconditions
git rev-parse --is-inside-work-tree
uv run --python 3.12 --no-project python "${CLAUDE_PLUGIN_ROOT}/scripts/platform_cli.py" auth-status
${CLAUDE_PLUGIN_ROOT} resolves at runtime (keep the quotes); in a source checkout
it is empty, so fall back to plugin/scripts/platform_cli.py. The same substitution
applies to every script below.
auth-status distinguishes the two failures that look alike from here — no CLI
installed and a CLI that is not logged in — and it names which of gh/glab this
repo's origin calls for. Neither is something to work around: without it there is no
way to read CI, and guessing at the state of a build is worse than reporting that you
could not read it. Stop and say which of the two it was.
This command needs no .rhiza/ directory and no template. A repo that is not
rhiza-managed still has requests and still has CI, and all of this applies unchanged.
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.
- 7d ago First seen · 204 lines · 51 tokens per session scan A 24ee4fc490f5
remote is a skill published in the GitHub repository Jebel-Quant/rhiza-claude (4 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 2,513 once invoked, about $0.0003 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
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
merge-queue-readiness
Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.
precommit
Pre-commit checks — lint:fix -> build -> test.
precommit-fast
Quick pre-commit checks — lint:fix -> test.