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-historygit 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-history)<a href="https://agentmods.dev/skills/jebel-quant/rhiza-claude/rhiza-history"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/rhiza-history/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-history"><img src="https://agentmods.dev/badge/skills/jebel-quant/rhiza-claude/rhiza-history.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.00054 | $0.02865 |
| Opus 5.5 | $0.00022 | $0.01146 |
| Sonnet 5.5 | $0.00011 | $0.00573 |
| Haiku 4.5 | $0.00005 | $0.00286 |
Grade A, and why
rhiza-history 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.
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.
- 9d ago First seen · 221 lines · 54 tokens per session scan A 2dc53c769898
rhiza-history is a skill published in the GitHub repository Jebel-Quant/rhiza-claude (6 stars, last pushed 4d ago), with no licence file. It adds 54 tokens to every session and 2,865 once invoked, about $0.0002 per session on Opus 5.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-10-21.
Other skills, from other repositories
implement-issue
Take a GitHub issue from planning to PR, resumable across clarification waits.
rememora-developer
Use this skill when working on Rememora development tasks such as picking approved tickets, planning implementations, writing code in isolated worktrees, running validation, and preparing pull requests. This is the Codex-facing equivalent of the Claude Code rememora-developer subagent.
gitlab-mr
GitLab merge request operations. ALWAYS use this skill when user wants to: (1) list merge requests, (2) view MR details, (3) create new MRs, (4) approve/merge MRs, (5) checkout MR branches, (6) add notes/comments, (7) rebase MRs.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.