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/evaluategit 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.00863 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
evaluate 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit evaluate
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.
A zero-write trial. evaluate replays your repo's recent landings (the
last few merged changes, or an explicit before/after ref pair) through
the same deterministic guardrail gate the hooks and CI would run, and
reports what the gate would have blocked plus what enabling dxkit costs
(measured gate latency, interruption rate, setup). It answers "would
dxkit help here, and what does it cost?" before you commit to installing
anything.
evaluate is an advisory replay, not a gate. It runs the trial in
disposable worktrees and writes nothing to your repository unless you
pass --output. Its exit code is always 0 on a completed trial, even
when a replayed landing would have been blocked. Scripts that want a
pass/fail signal read the JSON (totals.blocked) or run
guardrail check.
Usage
vyuh-dxkit evaluate [path] [--last-prs <n>] [--base <ref> --head <ref>]
[--preset security-only|full-debt] [--json]
[--redact] [--output <file>]
With no flags it replays a default window of recent landings and prints a terminal summary. Each landing takes roughly 30 seconds to a minute to replay, so a small window returns in a couple of minutes.
Flags
| Flag | Effect |
|---|---|
--last-prs <n> |
Replay the last n merged changes (a positive integer) |
--base <ref> |
Replay a single explicit before/after pair: the "before" ref |
--head <ref> |
The "after" ref of the explicit pair (paired with --base) |
--preset <name> |
Which findings block: security-only (default) or full-debt. Same presets as the loop Stop-gate |
--json |
Emit the versioned evidence document to stdout, for tooling |
--redact |
Strip finding evidence (locations, captured snippets) from the output, for sharing |
--untrusted |
Treat the scanned source as attacker-controlled, matching a hosted PR gate's read-only scanner posture |
--no-incremental |
Force a full scan on each replay instead of the diff-scoped default |
--output <file> |
Write the evidence JSON to a file (an explicit, user-requested write; the repo itself receives nothing) |
--verbose |
Print per-tool timing to stderr |
path |
Repository to evaluate (defaults to the current directory) |
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 · 66 lines · 0 tokens per session scan A ab25f10d22e5
evaluate 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 863 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.