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/coveragegit 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.00766 |
| Opus 5 | $0.00000 | $0.00383 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
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 2d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit coverage
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.
Run each active language pack's test command with coverage
instrumentation and write the materialized coverage artifact. Used to
upgrade test-gaps + health.Testing from filename-match heuristic
to real line-coverage truth.
Side-effecting: this actually runs your tests. Be aware of test isolation, network calls, etc. before running on a fresh machine.
Usage
vyuh-dxkit coverage [path] [options]
Options
| Option | Effect |
|---|---|
--lang <id> |
Restrict to one pack (typescript, python, go, rust, csharp, kotlin, java, ruby) |
--timeout <seconds> |
Per-pack timeout (default: 600) |
--no-fail-fast |
Continue past pack failures; report all outcomes |
--verbose |
Per-pack stderr passthrough |
What it does per pack
Each pack declares its own test command + coverage parser:
| Pack | Default command | Artifact |
|---|---|---|
| TypeScript / JavaScript | npm test -- --coverage |
Istanbul coverage-summary.json / coverage-final.json |
| Python | coverage run -m pytest && coverage xml |
coverage.xml |
| Go | go test ./... -coverprofile=coverage.out |
coverage.out |
| Rust | cargo tarpaulin --out json |
tarpaulin-report.json |
| C# | dotnet test --collect:"XPlat Code Coverage" |
Cobertura XML |
| Kotlin | ./gradlew test jacocoTestReport |
JaCoCo XML |
| Java | mvn test jacoco:report |
JaCoCo XML |
| Ruby | bundle exec rspec (with SimpleCov) |
coverage/.last_run.json |
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.
- 2d ago First seen · 78 lines · 0 tokens per session scan A e3d5efa011c6
coverage is a command published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 766 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
readme-audit
Audit a README's reading flow by treating it as a conversion funnel. Every section is evaluated against a target reader and a terminal action. Produces a structured audit blueprint that feeds directly into /readme-restructure.
readme-restructure
Execute a /readme-audit blueprint. Rewrites the README to the evaluator → conversion → links structure and creates linked docs by extracting and reorganising existing content.
setup
Initialize a new project with SDLC-compliant structure. Creates required files, configures build system, sets up CI/CD, and establishes quality tooling.
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
run-tests
Run automated functional tests using the hook-driven test framework. Execute the test suite to validate all project functionality.
test-report
Generate test execution report in markdown format.