Borrowing it
Nothing to install: this file belongs to Black-coffe/vulyk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Black-coffe/vulyk/main/.claude/agents/drone-coverage.mdgit 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/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/black-coffe/vulyk/drone-coverage"><img src="https://agentmods.dev/badge/agents/black-coffe/vulyk/drone-coverage.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.00046 | $0.00639 |
| Opus 5.5 | $0.00018 | $0.00256 |
| Sonnet 5.5 | $0.00009 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
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 owner asked for?
Your inputs are two files: the spec's brief.md (the request verbatim, with ## Answers and
## Asks) and its plan.md. Read those two and nothing else. The story files are withheld on purpose:
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.
- Take the numbered asks from
brief.md's## Asks(1. <verbatim fragment>lines; a block of>lines alone is asks 1, 2, ... in order) as they are. If there is no## Asks, split the brief's blockquotes yourself: one ask is the shortest verbatim fragment that carries it, numbered 1..N in reading order; background sentences are not asks, and when unsure, count it as an ask and let the owner decide. - Read the plan: goal, assumptions, story index, contracts, descoped lines.
- Judge each ask against the plan alone: carried, partial or absent. A story title that 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
Ask <n>: <verbatim fragment> - nothing in the plan carries it
## Partial
Ask <n>: <verbatim fragment> - plan carries <what>, leaves out <what>
## Carried
<count only, one line>
## 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 Ask <n>: <fragment> that the owner never answered
Quote the brief verbatim: the Queen reconciles your fragments with trace-check.sh, and a tidied quote
does not match. <n> is the ask's number from ## Asks, or your own reading-order number when there
is none (say which). Propose no stories, designs or estimates: naming the gap is the whole job. Silence
about an ask reads as "carried", so say so when unsure.
If brief.md does not exist, your entire report is CANNOT RUN: no brief.md at <path>. 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 Changed · -10 tokens per session db8d0c60623c
- 13d ago Changed · +1 lines a50124f8fcbe
- 1mo ago Changed · -10 lines · -2 tokens per session cefcd0910401
- 1mo ago Changed · +1 lines 247404f9782e
- 1mo ago Changed · +6 lines · +3 tokens per session 975c5beb58f6
- 2mo 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 today), licensed MIT. It adds 46 tokens to every session and 639 once invoked, about $0.0002 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-31.
Other agents, from other repositories
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
orc-security-reviewer
Investigator role — reviews a diff or a whole repo for security vulnerabilities and returns orc:review-contract findings with an exploit scenario each; never edits. Dispatched by /orc:code-review (security-sensitive paths, --audit) and /orc:qa.
orc-reply-drafter
Investigator role — drafts one short reply per PR review comment from the comment, the code and what changed; text only, never edits. Used by /orc:address.
creo-cloudflare-cli
Cloudflare Wrangler expert for Workers, Pages, R2, D1, KV, deployments, and secrets management.
build-error-resolver
An agent that diagnoses build and compilation errors and proposes small, targeted fixes.
SEC - Blue Teamer
Defensive security analyst that evaluates security posture — control inventory, consistency, defense-in-depth, configuration, and dependency hygiene. The defensive counterpart to the red-teamer. Advisory only.