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/baselinegit 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.02836 |
| Opus 5 | $0.00000 | $0.01418 |
| Sonnet 5 | $0.00000 | $0.00567 |
| Haiku 4.5 | $0.00000 | $0.00284 |
Grade A, and why
baseline 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit baseline
Run as:
vyuh-dxkit <cmd>afternpm install -g @vyuhlabs/dxkit, ornpx @vyuhlabs/dxkit <cmd>for one-shot use.
Capture the per-finding identities of every issue dxkit currently
surfaces in your repo, and write them to a JSON file under
.dxkit/baselines/. The file becomes the "brownfield anchor" the
guardrail check command diffs new scans against to
decide what is a net-new regression vs. pre-existing debt.
Usage
vyuh-dxkit baseline create [path] [--name <name>] [--force]
[--mode <mode>] [--ref <ref>]
vyuh-dxkit baseline show [path] [--name <name>] [--baseline <path>]
[--kind <kind>] [--json]
baseline create
Runs every analyzer, fingerprints each finding via the canonical
identity helpers, and writes .dxkit/baselines/<name>.json (default
<name> is main) — unless --mode=ref-based, in which case no
file is written and the guardrail check recomputes the prior side
from a git ref on demand.
| Option | Effect |
|---|---|
path |
Repo root to scan. Defaults to . |
--name <n> |
Baseline name. Multiple baselines can coexist (e.g. main, release-2025-q4). Default main |
--force |
Overwrite an existing baseline file rather than erroring out |
--mode <m> |
Baseline posture: committed-full, committed-sanitized, or ref-based. See "Modes" below |
--ref <r> |
Baseline ref for --mode=ref-based. Default: origin/HEAD (probed via git), falls back to origin/main |
--verbose |
Print per-tool timing to stderr |
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 · 249 lines · 0 tokens per session scan A 786b55365941
baseline 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 2,836 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.