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/qa10devteam/behive/openclawnpx skills add qa10devteam/behive --skill openclawgit clone --depth 1 https://github.com/qa10devteam/behiveWhat 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.00033 | $0.00914 |
| Opus 5 | $0.00016 | $0.00457 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade B, and why
behive-research scanned grade B with 2 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 2d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
1. Start: `curl -X POST .../research -d '{"topic": "AI chip market NVIDIA AMD custom silicon 2025-2026", "scale": 30}'` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Verify: `curl http://localhost:8091/health` How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BeHive Deep Research
Run multi-source research missions that extract structured, scored claims from any topic. Returns verified intelligence — not text summaries.
Setup
BeHive must be running. Install and start:
pip install behive
cp .env.example .env # add your LLM API key
docker compose up -d
# OR: behive api start
Verify: curl http://localhost:8091/health
Operations
1. Start Research Mission
When the user asks to research a topic, deeply investigate something, or gather intelligence:
curl -s -X POST http://localhost:8091/research \
-H "Content-Type: application/json" \
-d '{"topic": "<USER_TOPIC>", "scale": 30, "depth": 3}'
Scale guide:
15= quick scout (2-3 min, ~50 claims)30= standard (5-10 min, ~200-500 claims)100= deep (15-30 min, ~800+ claims)300= exhaustive (45-90 min, ~2000+ claims)
Save the returned mission_id or job_id.
2. Check Progress
Poll every 30 seconds:
curl -s http://localhost:8091/research/<MISSION_ID>
Phases: scout → harvest → process → synth → done
Or stream real-time via SSE:
curl -N http://localhost:8091/research/<MISSION_ID>/events
3. Get Report
When status is done:
curl -s http://localhost:8091/research/<MISSION_ID>/report
Returns the full synthesized report with citations and quality metrics.
4. Search Knowledge
Search across all past missions:
curl -s "http://localhost:8091/search?q=<QUERY>&limit=20"
5. Knowledge Graph
Query entities and relationships:
curl -s "http://localhost:8091/graph/entities?limit=50"
curl -s "http://localhost:8091/graph/entity/<NAME>/relationships"
6. List Past Missions
curl -s http://localhost:8091/missions
Output Format
Claims are structured JSON with:
claim— the extracted factquality_score— 0.0 to 1.0 (only ≥0.55 enter the database)source_url— origin URLconfidence— model confidenceclaim_type— fact, statistic, quote, prediction, etc.evidence— supporting context
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.
- 2d ago First seen · 128 lines · 33 tokens per session scan B b2c29122a110
behive-research is a skill published in the GitHub repository qa10devteam/behive (143 stars, last pushed 19d ago), licensed MIT. It adds 33 tokens to every session and 914 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…