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/completions)<a href="https://agentmods.dev/skills/jebel-quant/rhiza-claude/completions"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/completions/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/completions"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/completions.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.00038 | $0.01152 |
| Opus 5 | $0.00019 | $0.00576 |
| Sonnet 5 | $0.00008 | $0.00230 |
| Haiku 4.5 | $0.00004 | $0.00115 |
Grade A, and why
completions 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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /completions. Goal: install the bundled make tab-completion for the
user's shell, so make <TAB> lists the targets of whatever project their shell is
sitting in.
Two things make this command unlike every other one here. Read both before you run anything.
- It writes outside the repo. The destinations are under
${XDG_DATA_HOME:-$HOME/.local/share}— the user's home, not the working tree. There is nothing to review in a PR afterwards and nothing agit checkoutundoes. That is why the user has to name this command: it is not model-invocable. - It is not repo-scoped at all. The completion is generic make completion — it
discovers targets by parsing the make database in the current directory — so it works
in every make project on the machine, rhiza-managed or not. Install it once per
machine, not once per repo. If the user asks you to run it "for this repo", say that
and install it once anyway; a second run is a no-op that reports
already up to date.
This replaces the make install-completions target the rhiza template used to sync into
every managed repo, where N repos each carried an identical copy of a script that
installs to one shared path. If the user's repo still has that target, either one works
today and they do the same thing — prefer this one, and say why.
Argument (optional): $ARGUMENTS — bash, zsh or both. Default both.
1. Work out which shell
Do not guess from $SHELL and install only that one. Installing an unused
completion file is inert; installing the wrong single one leaves the user with no
completion and no error. So:
$ARGUMENTSnames a shell → pass it through.$ARGUMENTSis empty →both, and say so in the report.
fish and anything else is unsupported. The script rejects it with argparse's own
message; relay that rather than improvising a fish completion.
2. Install
${CLAUDE_PLUGIN_ROOT} resolves at runtime (keep the quotes); in a source
checkout it's empty, so fall back to the repo-relative path
plugin/scripts/install_completions.py.
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.
- 11d ago First seen · 97 lines · 38 tokens per session scan A d72602f1a0c4
completions is a skill published in the GitHub repository Jebel-Quant/rhiza-claude (4 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,152 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
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
sync-check
Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs"…
gap-analyzer
Compares a CLI's implemented commands against its APP.md API map and traffic-analysis.json to find missing endpoints, incomplete CRUD, dead client methods, and priority gaps. Runs as the mandatory first step of /cli-anything-web:refine and as an optional pre-review scan in standards.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.