report

A command that runs the project's full dxkit audit and combines the results into an HTML dashboard. It checks project health, security vulnerabilities, untested files, code quality, duplication, and git activity.

In plain words
What is it for?
Use it for a full project audit, detailed analyzer reports, coverage-based checks, and score snapshots or trends over time.
Why use it?
It gathers several separate checks in one run, while allowing one failed check to finish without stopping the others.

Command

Install

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.

agentmods
npx agentmods add commands/vyuh-labs/dxkit/report
Clone the repo
git clone --depth 1 https://github.com/vyuh-labs/dxkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 871 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00871
Opus 5 $0.00000 $0.00436
Sonnet 5 $0.00000 $0.00174
Haiku 4.5 $0.00000 $0.00087

Measured 2d ago against content hash ea60f398c83d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

report 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.

docs/commands/report.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

vyuh-dxkit report

Run as: vyuh-dxkit <cmd> after npm install -g @vyuhlabs/dxkit, or npx @vyuhlabs/dxkit <cmd> for one-shot use. Examples on this page use the short form.

Run every analyzer + the dashboard in one shot. The full audit.

Usage

vyuh-dxkit report [path] [options]

What it runs

In sequence, each as a separate child process (so a failure in one doesn't take down the others):

  1. health — 6-dimension audit
  2. vulnerabilities — security deep scan
  3. test-gaps — untested-file ranking
  4. quality — lint + duplication + slop
  5. dev-report — git activity
  6. dashboard — assembles the above into HTML

Options

Option Effect
--with-coverage Pass --with-coverage to health + test-gaps (materializes real coverage first)
--detailed All analyzers write their detailed reports

Subcommands: the score-over-time series

Beyond the full audit, report carries the snapshot surface:

vyuh-dxkit report snapshot           # publish this merge's scores to the dxkit-reports ref
vyuh-dxkit report history [--json]   # the raw snapshot table (--markdown for a CI summary)
vyuh-dxkit report trend [--json]     # the score-over-time series: per-dimension sparklines

report trend renders every dimension's score over time since the first snapshot on record (retention can truncate older snapshots, so the record's start is the claim), plus the debt-over-time series (finding counts by kind, stamped per merge from the run's security aggregate) where the snapshots carry one. The series is segmented wherever the scoring methodology or the score-relevant tool set changed between snapshots: a line is never drawn across points that are not comparable, and each boundary prints its reason. Snapshots are published per merge by the reports.onMerge workflow (see the policy guide), or by hand with report snapshot.

Read the full file on GitHub · 87 lines

Changes

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.

  1. 2d ago First seen · 87 lines · 0 tokens per session scan A ea60f398c83d

Subscribe to this mod's changes

report 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 871 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.