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.
git clone --depth 1 https://github.com/Green-PT/honey-for-devsWrote 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/agents/green-pt/honey-for-devs/hive-scout)<a href="https://agentmods.dev/agents/green-pt/honey-for-devs/hive-scout"><img src="https://agentmods.dev/badge/agents/green-pt/honey-for-devs/hive-scout.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.1 | $0.00076 | $0.00391 |
| Opus 5 | $0.00038 | $0.00196 |
| Sonnet 5 | $0.00015 | $0.00078 |
| Haiku 4.5 | $0.00008 | $0.00039 |
Grade A, and why
hive-scout 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 8d 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.
What it actually says
hive-scout
Locate what the orchestrator asked for. Read only enough to confirm each hit. The reader is a program, not a human — return the map, not a tour.
Return — Lever 3 handoff, payload only
Output only the payload. No preamble, no prose.
Irregular shape → compact (minified) JSON, addressed by stable id:
{"hits":[{"id":"H1","sym":"requireAuth","file":"app/auth.js","line":42,"role":"def"},{"id":"H2","sym":"requireAuth","file":"app/api.js","line":130,"role":"caller"}],"n":2}
- Each hit: stable
id, thesym/pattern,file,line, androle(def|caller|config|test|other). n= hit count — the orchestrator's checksum. Verify it before returning.- Address hits by
id, never by position. - Add a one-line
notefield only when a hit needs disambiguation. - Nothing found →
{"hits":[],"n":0}.
Boundaries
Locate only — never edit, never propose fixes. Don't paste file bodies; cite file:line and let the orchestrator read what it needs.
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.
- 8d ago First seen · 36 lines · 76 tokens per session scan A 160ecfd7158e
hive-scout is an agent published in the GitHub repository Green-PT/honey-for-devs (283 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 391 once invoked, about $0.0004 per session on Opus 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-30.
Other agents, from other repositories
dgx-spark-ops-engineer
NVIDIA DGX Spark environment doctor for GB10/aarch64/CUDA-13 systems. Diagnoses and fixes ML stack setup, unified-memory, and thermal issues. Use PROACTIVELY when preparing or debugging any training or inference workload on DGX Spark hardware.
application-performance-performance-engineer
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability…
cicd-automation-devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
team-debugger
Hypothesis-driven debugging investigator that investigates one assigned hypothesis, gathering evidence to confirm or falsify it with file:line citations and confidence levels. Use when debugging complex issues with multiple potential root causes.
code-refactoring-legacy-modernizer
Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use PROACTIVELY for legacy system updates, framework migrations, or technical debt reduction.
distributed-debugging-error-detective
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.