Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Jebel-Quant/rhiza-claude --skill rhiza-updategit clone --depth 1 https://github.com/Jebel-Quant/rhiza-claudeWrote 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/rhiza-update)<a href="https://agentmods.dev/skills/jebel-quant/rhiza-claude/rhiza-update"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/rhiza-update/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/rhiza-update"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/rhiza-update.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.00048 | $0.03246 |
| Opus 5.5 | $0.00019 | $0.01298 |
| Sonnet 5.5 | $0.00010 | $0.00649 |
| Haiku 4.5 | $0.00005 | $0.00325 |
Grade A, and why
rhiza-update 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.
This is a copy
88% identical to update, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 Changed · +5 lines ad9fcad02ecd
- 23d ago First seen · 201 lines · 48 tokens per session scan A b39aa5e2dea5
rhiza-update is a skill published in the GitHub repository Jebel-Quant/rhiza-claude (6 stars, last pushed 7d ago), with no licence file. It adds 48 tokens to every session and 3,246 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to update, and is treated as a copy.
Other skills, from other repositories
loop-gh-pr
A recipe for a scheduled GitHub pull-request watcher. It checks open pull requests for new activity and prepares read-only review drafts without posting comments or merging anything.
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.
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.
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.
apply-fixes
Internal skill for commands. Apply a review's verified fixes to the working tree when nothing needs deciding - the --fix flag of /lets:check, /lets:review and /lets:handoff. Do not trigger on user conversation - only when one of those commands runs with --fix.
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.