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 skills/floor/vlist/coverage-gapsnpx skills add floor/vlist --skill coverage-gapsgit clone --depth 1 https://github.com/floor/vlistWhat 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.00018 | $0.00377 |
| Opus 5 | $0.00009 | $0.00188 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
coverage-gaps 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 today.
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
Find Coverage Gaps
Identify untested code in the vlist project.
Instructions
-
Determine scope:
- If
$ARGUMENTSnames a feature (e.g.,grid,async), run coverage for that feature's tests - If
$ARGUMENTSnames a file path, run coverage for tests covering that file - If no arguments, run full coverage
- If
-
Run coverage:
- Scoped:
bun test --coverage test/features/$ARGUMENTS/ 2>&1orbun test --coverage $ARGUMENTS 2>&1 - Full:
bun test --coverage 2>&1
- Scoped:
-
Parse the coverage output and report:
- Files with less than 100% line coverage, sorted worst-first
- For each gap, read the source file and identify which functions/branches are likely uncovered
- Suggest specific test cases that would close the gaps
-
Output format:
## Coverage Gaps ### src/features/async/feature.ts — 87% lines - `handleLoadError()` (lines 45-62) — no test for error path - Suggested test: "should handle adapter rejection gracefully" ### src/rendering/renderer.ts — 92% lines - `recycleElement()` (lines 120-128) — pool-full branch untested - Suggested test: "should discard element when pool is at capacity" -
If everything is at 100%:
Full coverage — no gaps found.
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.
- today First seen · 42 lines · 18 tokens per session scan A 64bf8fd1e3e4
coverage-gaps is a skill published in the GitHub repository floor/vlist (16 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 377 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
frontmcp-production-readiness
Pre-production audit, hardening, and go-live checklists for FrontMCP servers. Use before shipping to verify security hardening, performance, reliability, and observability, and for target-specific production checklists: Node server (Docker, graceful shutdown, Redis session scaling), Vercel and edge (cold-start…
react-hooks-composition
Advanced React hooks composition patterns - SWR integration, debounced search, memoized contexts, state machines, and performance optimization.
frontend-developer
Expert frontend developer persona — React/Vue/Angular, performance optimization, Core Web Vitals, accessibility. Builds responsive web apps with pixel-perfect precision.
react-patterns
React production patterns — hooks, state management, performance optimization, and component design. Use when building React components, reviewing React code, or fixing React performance issues.
v3-mcp-optimization
Use when ProxyManager throughput or cold-start latency is a bottleneck — catalogs six optimization patterns (O(1) lookup, 3-tier cache, batch compression, pool reuse, lazy deserialization, parallel boot) with TypeScript snippets and expected gains.
react_patterns_hooks
Curated Knowledge API for AI Agents — 68 MCP tools, 200+ skill packs, 46K chunks, semantic search over 670K vectors, 5-layer validation pipeline. Works with Claude Code, Cursor, Cline, Windsurf.