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 triage-issuegit 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/triage-issue)<a href="https://agentmods.dev/skills/aden-hive/hive/triage-issue"><img src="https://agentmods.dev/badge/skills/aden-hive/hive/triage-issue/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/triage-issue"><img src="https://agentmods.dev/badge/skills/aden-hive/hive/triage-issue.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.00000 | $0.01004 |
| Opus 5.5 | $0.00000 | $0.00402 |
| Sonnet 5.5 | $0.00000 | $0.00201 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
triage-issue 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- triage-issue-skill — 95% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Issue Skill
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
Trigger
User provides a GitHub issue URL or number, e.g.:
/triage-issue 1970/triage-issue https://github.com/adenhq/hive/issues/1970
Workflow
Step 1: Fetch Issue Details
gh issue view <number> --repo adenhq/hive --json title,body,state,labels,author
Extract:
- Title
- Body (the claim/bug report)
- Current state
- Labels
- Author
If issue is already closed, inform user and stop.
Step 2: Analyze the Claim
Read the issue body and identify:
- The core claim - What is the user asserting?
- Technical specifics - File paths, function names, code snippets mentioned
- Expected behavior - What do they think should happen?
- Severity claimed - Security issue? Bug? Feature request?
Step 3: Investigate the Codebase
For each technical claim:
- Find the referenced code using Grep/Glob/Read
- Understand the actual implementation
- Check if the claim accurately describes the behavior
- Look for related tests, documentation, or design decisions
Step 4: Evaluate Validity
Categorize the issue as one of:
| Category | Action |
|---|---|
| Valid Bug | Do NOT close. Inform user this is a real issue. |
| Valid Feature Request | Do NOT close. Suggest labeling appropriately. |
| Misunderstanding | Prepare technical explanation for why behavior is correct. |
| Fundamentally Flawed | Prepare critique explaining the technical impossibility or design rationale. |
| Duplicate | Find the original issue and prepare duplicate notice. |
| Incomplete | Prepare request for more information. |
Step 5: Draft Response
For issues to be closed, draft a response that:
- Acknowledges the concern - Don't be dismissive
- Explains the actual behavior - With code references
- Provides technical rationale - Why it works this way
- References industry standards - If applicable
- Offers alternatives - If there's a better approach for the user
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 · 146 lines · 0 tokens per session scan A 96b593f6bdf2
triage-issue is a skill published in the GitHub repository aden-hive/hive (11,119 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,004 tokens. 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-30.
Other skills, from other repositories
regex-expert
Regular expression expert for crafting, debugging, and explaining patterns.
sentry
Sentry error tracking and debugging specialist.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
ha-self-diagnosis
Self-understanding and issue reporting for Hope Agent itself. Use when the user asks how Hope Agent works internally, asks about its own source code/docs/runtime behavior, reports a bug/failure/slowness/crash, asks to diagnose logs, or asks to create/submit a GitHub issue for a bug, feature request, or improvement…
systematic-debugging
Systematic approach to diagnosing and fixing errors.