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 qingye-lab/rootloom --skill setup-rootloomgit clone --depth 1 https://github.com/qingye-lab/rootloomWrote 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/qingye-lab/rootloom/setup-rootloom)<a href="https://agentmods.dev/skills/qingye-lab/rootloom/setup-rootloom"><img src="https://agentmods.dev/badge/skills/qingye-lab/rootloom/setup-rootloom/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/qingye-lab/rootloom/setup-rootloom"><img src="https://agentmods.dev/badge/skills/qingye-lab/rootloom/setup-rootloom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.01224 |
| Opus 5.5 | $0.00035 | $0.00490 |
| Sonnet 5.5 | $0.00017 | $0.00245 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
setup-rootloom 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 1mo 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up Rootloom Personal Core
Resolve this Skill directory and use its deterministic setup script.
Choose a preset
python3 <skill-dir>/scripts/setup_rootloom.py list-components
| Preset | Result |
|---|---|
skills-only |
Plugin Skills only; the project-guidance Hook is disabled |
guidance |
Global working agreement plus read-only project-context Hook |
personal |
Guidance plus optional Autonomy; recommended and default |
Exact capabilities are global-policy, project-context, and autonomy.
autonomy always includes global-policy because the Rules intentionally defer authorization mode and scope to that guidance. Legacy engineering and command-safety inputs remain compatibility aliases but are not recommended names.
Optional global layer
codex plugin add rootloom@rootloom completes the plugin installation. It exposes Rootloom Skills without writing global guidance, command Rules, setup state, or review gates. Stop there for the lowest-cost experience.
Only when the user explicitly wants cross-project guidance, the project-guidance Hook, or command Rules, inspect and install an optional preset:
python3 <skill-dir>/scripts/setup_rootloom.py plan --preset personal
python3 <skill-dir>/scripts/setup_rootloom.py install --preset personal
python3 <skill-dir>/scripts/setup_rootloom.py status
apply remains a compatibility/expert command. Prefer install for the first setup and upgrade after the Codex plugin snapshot has been refreshed.
The personal preset manages only:
~/.codex/AGENTS.md;~/.codex/rules/rootloom.rules;~/.codex/.rootloom/components.json;~/.codex/.rootloom/state.json, a pending transaction journal, and a simple backup manifest.
Setup is serialized by an ordinary local lock, refuses symlinked or user-owned targets, stages the complete target set before publishing a transaction journal, resumes interrupted staged work before the next mutating setup or rollback operation, writes each file atomically, and preserves original content and mode for rollback. Recovery refuses a target changed after interruption and does not claim hostile shared-filesystem locking.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +4 lines e6b15b8ebce0
- 1mo ago First seen · 94 lines · 87 tokens per session scan A 9c2d1119758f
setup-rootloom is a skill published in the GitHub repository qingye-lab/rootloom (10 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 1,224 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
readiness
Use when the user wants to analyze, audit, or assess their codebase for AI agent readiness. Also use for "readiness report", "how ready is my project", "analyze my codebase", "audit my repo", "check my setup", or "what should I improve".
template-comprehensive-assessment
Full checkout audit for the Research Project Template — tests, architecture, docs, manuscript, pipeline. USE WHEN user asks for comprehensive assessment, full repo review, health check across projects, audit everything, or pre-merge sanity sweep for template exemplars — even without naming docs/prompts or a skill. Not…
pr-sweep
Review every open PR with the code-reviewer agent and an adversarial review, apply the findings, and merge each one once CI is green. Use when asked to ship, sweep, or merge open PRs.
slop-check
LLM-judge slop & erosion scan of a diff, mirroring SlopCodeBench. Scores code on Erosion (verbosity, dead branches, redundant structure accumulated under iterative change) and Verbosity (unnecessary complexity), then reports per-category findings weighted toward code that EXTENDS existing modules. Use after…
agentic-code-review
Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.