OpenHive is a runtime for groups of specialized AI agents that collaborate on long-running business processes. A persistent lead agent, called the Queen, creates and coordinates worker agents while the system manages state, recovery, observability, costs, and human oversight. The catalogue entries provide agent skills, instructions, and integrations for working with this harness.
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 aden-hive/hive --skill writing-hive-skillsgit clone --depth 1 https://github.com/aden-hive/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/aden-hive/hive/writing-hive-skills)<a href="https://agentmods.dev/skills/aden-hive/hive/writing-hive-skills"><img src="https://agentmods.dev/badge/skills/aden-hive/hive/writing-hive-skills/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/aden-hive/hive/writing-hive-skills"><img src="https://agentmods.dev/badge/skills/aden-hive/hive/writing-hive-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 33 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 44 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00063 | $0.02355 |
| Opus 5.5 | $0.00025 | $0.00942 |
| Sonnet 5.5 | $0.00013 | $0.00471 |
| Haiku 4.5 | $0.00006 | $0.00235 |
Grade A, and why
hive.writing-hive-skills scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `allowed-tools` | Experimental. Space-separated pre-approved tools, e.g. `Bash(curl:*) Bash(jq:*) Read` | How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operational Protocol: Writing Hive Skills
Hive agents discover skills by scanning several roots, in precedence order:
<project>/.hive/skills/— project, Hive-specific<project>/.agents/skills/— project, cross-client~/.hive/skills/— user, Hive-specific~/.agents/skills/— user, cross-client- Framework defaults shipped in
core/framework/skills/_default_skills/
Each skill is a directory containing a SKILL.md. At startup, only the frontmatter name + description of every skill is loaded; the body is loaded only when the agent activates the skill. Design for that.
Choosing where to put a new skill
- Colony-scoped (via
write_skillinside colony mode): when the skill is the operational protocol a single colony needs — its API auth, DOM selectors, DB schema, task-queue conventions — do NOT place it under~/.hive/skills/or<project>/.hive/skills/yourself. Those roots are SHARED and every colony on the machine will see it. Instead, once you're inside the colony (post-fork), callwrite_skill(skill_name, skill_description, skill_body, skill_files?)and the skill is materialized under~/.hive/colonies/<colony_name>/skills/<skill-name>/where only that colony's workers discover it. See the subsection below. - Project-scoped: put under
<project>/.hive/skills/when the skill is tied to that codebase's APIs, conventions, or infra and multiple agents in the project should share it. - User-scoped: put under
~/.hive/skills/when the skill is reusable across projects for this machine/user and all agents should see it. - Framework default: add under
core/framework/skills/_default_skills/AND register inframework/skills/defaults.py::SKILL_REGISTRYonly when the skill is a universal operational protocol shipped with Hive. Default skills use thehive.<name>naming convention and includetype: default-skillin metadata.
Colony-scoped skills via write_skill
A colony-scoped skill is one that belongs to exactly ONE colony — e.g. it encodes the HoneyComb staging API the honeycomb_research colony polls, or the LinkedIn outbound flow the linkedin_outbound_campaign colony runs. Writing such a skill at ~/.hive/skills/ or <project>/.hive/skills/ leaks it to every other colony, which will then see it at selection time.
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 First seen · 181 lines · 63 tokens per session scan A 7b21e27f7e83
hive.writing-hive-skills is a skill published in the GitHub repository aden-hive/hive (11,122 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 2,355 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
yoagent
Use when building, extending or upgrading an agent on the yoagent Rust crate. Maps each job (tools, policies, verifiers, budgets, sub-agents, plugins from other ecosystems, retries, structured output, tests) to the yoagent feature for it, with tips, pitfalls and what changed per version.
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
Vizra ADK Tool Creation
Build custom tools for Vizra ADK agents - includes patterns for database, API, file, and email tools.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
Vizra ADK Workflows
Orchestrate complex multi-agent workflows - sequential, parallel, conditional, and loop patterns.
Vizra ADK Agent Creation
Create AI agents with Vizra ADK - includes patterns for customer service, data analysis, and content generation agents.