quality

A command-line code review tool that reports lint problems, duplicated code, structural measurements, unfinished-work markers, comment ratios, and a combined slop score. Linting checks code against automated style and error rules.

In plain words
What is it for?
Use it on a source tree to count lint errors and warnings, find duplicate lines, inspect file and module structure, count TODO or FIXME markers, and review the combined quality signal.
Why use it?
It gives developers one report for common maintenance problems across projects that may use several programming languages.

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/quality
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 729 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.00729
Opus 5 $0.00000 $0.00365
Sonnet 5 $0.00000 $0.00146
Haiku 4.5 $0.00000 $0.00073

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

Security

Grade A, and why

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

docs/commands/quality.md · 75 lines

How it starts

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

vyuh-dxkit quality

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.

Code quality + slop detection. Lint summary, duplicate code (jscpd), structural metrics (graphify), and a "slop score" composite.

Usage

vyuh-dxkit quality [path] [options]

What it surfaces

  • Lint counts — errors + warnings, summed across every active language pack's linter (eslint, ruff, golangci-lint, clippy, dotnet-format, detekt, pmd, rubocop). Multi-stack repos sum contributions and the tool label lists each.
  • Duplication — jscpd-detected duplicated lines + percentage + top-10 clones with file/line attribution.
  • Structural — graphify-derived metrics: max functions in a file, average cohesion, community count, function count, dead imports, orphan modules.
  • Hygiene markers — TODO / FIXME / HACK / console.log counts across the staged source tree.
  • Comment ratio — code-to-comment ratio (filtered to pack-declared "source code" languages, not markup/data files).
  • Slop score — composite 0-100 metric that weights all of the above into one signal.

Options

Option Effect
--detailed Write detailed report (top-10 duplicate clones, top hygiene offenders, slop breakdown)
--json Stdout JSON
--no-save Skip files
--graph-context Attach each offender file's module + blast radius to the detailed report (fail-open — see context)
--attribute Attach a "Who to ask" column (each offender file's current owner, via the active-owner model). Opt-in; names + @handles, never emails.

Read the full file on GitHub · 75 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. 3d ago First seen · 75 lines · 0 tokens per session scan A 18404aa7c3f0

Subscribe to this mod's changes

quality 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 729 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.