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/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/agents/green-pt/honey-for-devs/hive-scout"><img src="https://agentmods.dev/badge/agents/green-pt/honey-for-devs/hive-scout.svg" alt="Reviewed on agentmods" width="80" 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.5 | $0.00030 | $0.00156 |
| Sonnet 5.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 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.
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.
- 1mo 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 (343 stars, last pushed 10d ago), licensed MIT. It adds 76 tokens to every session and 391 once invoked, about $0.0003 per session on Opus 5.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
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.
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.
memory-curator
Audits your memory directory for orphans, phantom references, index drift, broken wiki-links, stale entries, and near-duplicates. Writes a dated health report. Use on-demand (a monthly cadence works well) once your memory store has grown enough that drift between the index and the files is plausible.
ndv-telemetry
Observability specialist. Use when adding logging, metrics, distributed tracing, or health checks. Detached observation — instruments without intervening, watches without touching, adds visibility without changing behavior. Additive only.
ndv-diagnose
Debugging specialist. Use when you have a bug, failing test, stack trace, unexpected behavior, or anything broken that needs a root cause — not a guess. Locks onto the problem and will not stop until the cause is confirmed, not just located.
ndv-optimize
Performance optimization specialist. Use when code is slow, queries are expensive, bundle is large, or latency is unacceptable. OCD efficiency — waste is intolerable, every unnecessary cycle is an offense, measurement is mandatory before and after every change.