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/checksgit 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.01799 |
| Opus 5 | $0.00000 | $0.00899 |
| Sonnet 5 | $0.00000 | $0.00360 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade A, and why
checks 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit checks
Run as:
vyuh-dxkit <cmd>afternpm install -g @vyuhlabs/dxkit, ornpx @vyuhlabs/dxkit <cmd>for one-shot use.
List and dry-run the custom checks configured for this repo — user-declared
repo invariants (.dxkit/policy.json:checks)
plus the pack-declared built-in lint gate.
A custom check is a first-class gate citizen: its failures are fingerprinted,
baselined, and gated by guardrail check net-new only — a
pre-existing failure is grandfathered, so you can turn on a lint gate against a
repo with a thousand existing warnings and only ever block the error this
change introduced. User checks and lint share one runner; lint is the first
consumer of the seam, not a parallel path.
Usage
vyuh-dxkit checks [list] [path] [--json] # what's configured (default)
vyuh-dxkit checks run [path] [--json] # dry-run: execute each check, no gating
| Option | Effect |
|---|---|
list |
(default) Show configured user checks + active lint gates, and any skipped entries. |
run |
Execute each check and report pass / fail / skipped-* + finding counts. Never blocks, never writes a baseline. |
path |
Repo root. Defaults to . |
--json |
Machine-readable output (agent-queryable). |
checks list resolves through the same entry point the baseline producer
and the guardrail use, so what it prints is exactly what the gate sees. checks run answers "what would the gate find right now?" — but net-new-ness is decided
by guardrail check against the committed baseline, not here.
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 · 152 lines · 0 tokens per session scan A cc4ec16745bd
checks 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 1,799 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.