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 commands/vyuh-labs/dxkit/test-gapsgit clone --depth 1 https://github.com/vyuh-labs/dxkitWhat 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.00000 | $0.00837 |
| Opus 5 | $0.00000 | $0.00418 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
test-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 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit test-gaps
Run as:
vyuh-dxkit <cmd>afternpm install -g @vyuhlabs/dxkit, ornpx @vyuhlabs/dxkit <cmd>for one-shot use. Examples on this page use the short form.
Ranks untested source files by risk tier — surfaces what to test next, not just what's untested. CRITICAL findings first.
Usage
vyuh-dxkit test-gaps [path] [options]
Options
| Option | Effect |
|---|---|
--detailed |
Write detailed report (every untested file with classification rationale) |
--with-coverage |
Materialize real coverage data before scoring (Istanbul, coverage.py, JaCoCo, …) |
--json |
Stdout JSON |
--no-save |
Skip files |
--graph-context |
Attach each gap file's module + blast radius to the detailed report (a high-blast-radius untested file is higher-stakes; fail-open — see context) |
--attribute |
Attach a "Who to ask" column (each untested file's current owner, via the active-owner model). Opt-in; names + @handles, never emails. |
How it ranks
Each source file is classified into a tier:
| Tier | Heuristic |
|---|---|
| Critical | Name suggests security/auth/crypto/payment-handling concerns, OR is a controller/service > 500 lines |
| High | Controller/handler/service file (regardless of size) |
| Medium | Model / repository / interceptor / middleware files |
| Low | Everything else |
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 · 90 lines · 0 tokens per session scan A 403de3854990
test-gaps is a command published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 837 tokens. 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 commands, from other repositories
brooks-audit
Run a Brooks-Lint architecture audit.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
security
The security pass: secrets (blocking), SAST, dependency vulns — plus the index's entry points to review from.
init
Install the formatters this repository needs, with every command visible before it runs.
research
Research a technical or product question.