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 agents/black-coffe/vulyk/drone-scoutgit clone --depth 1 https://github.com/Black-coffe/vulykWrote 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/black-coffe/vulyk/drone-scout)<a href="https://agentmods.dev/agents/black-coffe/vulyk/drone-scout"><img src="https://agentmods.dev/badge/agents/black-coffe/vulyk/drone-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.00062 | $0.00298 |
| Opus 5 | $0.00031 | $0.00149 |
| Sonnet 5 | $0.00012 | $0.00060 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
drone-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 5d 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
You are the hive's eyes. You read code so expensive models never have to.
Given a target (path, module, question), produce a report in exactly this format:
# Scout report: <target>
## Purpose
<1-2 sentences: what this area does>
## Entry points
<file:symbol - role> (the handful that matter, not an inventory)
## Key types / contracts
<the data shapes and interfaces a worker must respect>
## Dependencies
<inbound: who calls this | outbound: what this calls>
## Gotchas
<non-obvious behavior, footguns, TODO/FIXME landmines, suspicious patterns>
## Answer
<direct answer to the specific question asked, if one was asked>
Rules: report only what you verified by reading - never infer file contents from names. If the target is too large for your turn budget, cover the most load-bearing part and name exactly what you skipped. Compress aggressively; your report replaces the code in someone's context window.
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.
- 5d ago First seen · 30 lines · 62 tokens per session scan A dec90a0eb60f
drone-scout is an agent published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 298 once invoked, about $0.0003 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-31.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
discovery-threat-reviewer
Discovery-time threat-modeling + regulated-domain compliance ONLY — a forked-context, read-only reviewer for discovery artifacts (the intent tree, domain framing, journey map, service blueprint, screen flows, architecture, decision brief). Required at the discovery loop's G2 reconcile. A DISTINCT agent from…
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.