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/toolsgit 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.00860 |
| Opus 5 | $0.00000 | $0.00430 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
tools 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit tools
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.
List + install all external tools dxkit knows how to drive. The go-to command when a report says something is "unavailable."
Usage
vyuh-dxkit tools # list status of all tools relevant to this repo
vyuh-dxkit tools install # install missing tools (interactive)
Options
| Option | Effect |
|---|---|
--all |
Install ALL tools across every language pack (not just the active stack) |
--yes |
Skip confirmation prompts before each install |
--json |
Stdout JSON (tool status, suitable for CI scripts) |
Tool layers
DXKit organizes external tools in layers:
- Layer 1 (universal): required regardless of stack —
cloc,gitleaks,semgrep,jscpd,graphify. - Layer 2 (per-language): activated only when the corresponding pack is detected. eslint for TypeScript, ruff for Python, govulncheck for Go, etc.
- Optional: quality-of-life enhancers (
osv-scanner-fix, the EPSS/KEV enrichment endpoints, etc.). Missing-but-optional shows as a warning, not a hard error.
Listing
vyuh-dxkit tools
Output:
LAYER 1 (universal — always required):
✓ cloc 1.96 (/opt/homebrew/bin/cloc)
✓ gitleaks 8.18.4 (/opt/homebrew/bin/gitleaks)
✓ semgrep 1.78.0 (/opt/homebrew/bin/semgrep)
✓ jscpd 4.0.5 (~/.local/bin/jscpd)
✓ graphify 0.5.0 (~/.cache/dxkit/tools-venv/bin/graphify)
LAYER 2 (typescript pack active):
✓ eslint 8.57.0 (./node_modules/.bin/eslint)
✓ npm-audit built-in
✓ license-checker built-in (npx)
LAYER 2 (python pack active):
✗ ruff not found
✗ pip-audit not found
✗ pip-licenses not found
OPTIONAL:
✓ osv-scanner 1.7.4
✓ osv-scanner-fix 1.7.4
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 · 103 lines · 0 tokens per session scan A 7cca39e6a83e
tools 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 860 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.
setup
Initialize a new project with SDLC-compliant structure. Creates required files, configures build system, sets up CI/CD, and establishes quality tooling.
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.
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.