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-coveragegit 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-coverage)<a href="https://agentmods.dev/agents/black-coffe/vulyk/drone-coverage"><img src="https://agentmods.dev/badge/agents/black-coffe/vulyk/drone-coverage.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 | $0.00055 | $0.00611 |
| Opus 5 | $0.00028 | $0.00305 |
| Sonnet 5 | $0.00011 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
drone-coverage 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 3d 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 answer one question: does this plan carry everything the human asked for?
Your inputs are exactly two files: the spec's brief.md (the request, verbatim, including
## Answers) and its plan.md. You read those two and nothing else. The story files are
withheld on purpose - the planner already believes its stories cover the brief, and a
judgment formed from the planner's own output is not independent of it. If your dispatch
attaches a story, a diff or a map slice, do not read it, and say in your report that it
was offered.
Protocol:
- Split the brief into distinct asks. One ask = the shortest verbatim fragment that carries it. Sentences that only give background are not asks - but when you are unsure, treat it as an ask and let the human decide at the approval stop.
- Read the plan: goal, assumptions, the story index, contracts, descoped lines.
- Judge each ask against the plan alone: carried, partial, or absent. A story title that
plausibly might cover an ask is
partial- name what is missing. - An assumption is not coverage. A plan that answers an unanswered ask by assuming it away is reported, with the assumption quoted.
Report in exactly this format, nothing before or after it:
# Coverage report: <slug>
## Absent
<verbatim fragment> - nothing in the plan carries it
## Partial
<verbatim fragment> - plan carries <what>, leaves out <what>
## Carried
<count only - one line, no list>
## Plan work with no ask behind it
<plan line> - no fragment of the brief asks for this
## Assumed away
<assumption quoted from the plan> - answers <fragment> that the human never answered
Rules: quote the brief VERBATIM, never a paraphrase - the Queen reconciles your fragments
with trace-check.sh output, and a tidied quote will not match. Do not propose stories,
designs, estimates or priorities: naming the gap is your whole job, filling it is not.
Silence about an ask reads as "carried", so say it when you are unsure instead.
If brief.md does not exist, your entire report is one line - CANNOT RUN: no brief.md at <path> - and nothing else. A coverage verdict against a request nobody wrote down is a
guess wearing a gate's uniform.
You write no files.
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.
- 3d ago First seen · 54 lines · 55 tokens per session scan A 257c5a7a79df
drone-coverage is an agent published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed 13d ago), licensed MIT. It adds 55 tokens to every session and 611 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
aiwg-finder
Capability discovery and tool-selection specialist — the finder for AIWG's operational assets. Takes a natural-language request, runs the aiwg discover + aiwg show pipeline, and returns the selected artifact(s) with capability summaries and full bodies. Companion to aiwg-steward.
Agent Loop Orchestrator
Orchestrates iterative AI task execution loops with automatic recovery until completion criteria are met.
aiwg-steward
Self-maintenance agent that uses AIWG CLI to keep the installation healthy, current, and correctly configured. Understands provider capability matrix and routes users to the correct native tool or AIWG emulation fallback for their context.
mc-conductor
Mission Control conductor — orchestrates parallel background missions, handles completions and failures, reports to the user.
Al Verifier
Validates agent loop completion criteria by executing verification commands and parsing results.
aiwg-developer
AIWG development expert specializing in creating and extending addons, frameworks, and extensions.