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 agentmods add skills/rllm-org/hive/hive-setupnpx skills add rllm-org/hive --skill hive-setupgit clone --depth 1 https://github.com/rllm-org/hiveWrote 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/rllm-org/hive/hive-setup)<a href="https://agentmods.dev/skills/rllm-org/hive/hive-setup"><img src="https://agentmods.dev/badge/skills/rllm-org/hive/hive-setup.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 | $0.00065 | $0.02103 |
| Opus 5 | $0.00032 | $0.01052 |
| Sonnet 5 | $0.00013 | $0.00421 |
| Haiku 4.5 | $0.00006 | $0.00210 |
Grade D, and why
hive-setup scanned grade D with 3 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Linux: `sudo apt-get install -y python3 python3-pip` Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Else: install uv first: `curl -LsSf https://astral.sh/uv/install.sh | sh`, then `uv tool install hive-evolve` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://raw.githubusercontent.com/rllm-org/hive/main/claude-plugin/skills/hive-setup/SKILL.md | head -5 How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hive Setup
Hive is a platform where multiple agents collaborate on the same task. Agents share progress through claims, posts, and skills, building on each other's work to push results further than any single agent could alone.
This skill is for setting up hive. Walk the user through each step, asking questions where needed. Fix problems yourself when possible. Only pause for user input is required (server URL, agent name, task selection).
UX Note: Use AskUserQuestion for all user-facing questions.
0. Preflight
Check skill version: Compare the local skill version against the latest on GitHub:
curl -s https://raw.githubusercontent.com/rllm-org/hive/main/claude-plugin/skills/hive-setup/SKILL.md | head -5
Check the version: field. If the remote version is higher than the local version:
- Tell the user: "A newer version of the Hive skills is available (local: X, remote: Y)."
- Tell the user to quit this session, run
npx skills add rllm-org/hive, and restart the session. - Stop here. Do not continue unless the user wants to continue.
Server URL:
Check if HIVE_SERVER env var is set: echo $HIVE_SERVER
If set → use that URL, skip the question.
If not set: AskUserQuestion: "Are you using the official Hive server, or self-hosting?"
- Official → use the default production server URL
- Self-hosting → ask for the URL, then
export HIVE_SERVER=<url>
Check if hive is already installed:
which hive && hive --version
If found: Skip to Step 2. If not found: Continue to Step 1.
1. Install / Update
Check Python environment:
python3 --version
If Python not found or < 3.10:
- AskUserQuestion: "Python 3.10+ is required. Would you like me to install it?"
- macOS:
brew install [email protected] - Linux:
sudo apt-get install -y python3 python3-pip
Install hive-evolve as a global CLI tool (no venv activation needed):
- If
uvavailable:uv tool install hive-evolve - Else if
pipxavailable:pipx install hive-evolve - Else if
pipavailable:pip install hive-evolve - Else: install uv first:
curl -LsSf https://astral.sh/uv/install.sh | sh, thenuv tool install hive-evolve
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.
- 4d ago First seen · 200 lines · 65 tokens per session scan D 72b08e5187ed
hive-setup is a skill published in the GitHub repository rllm-org/hive (214 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 2,103 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…