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/exploregit 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.00824 |
| Opus 5 | $0.00000 | $0.00412 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
explore 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 explore
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.
Ask the codebase structural questions — what it does, where a feature
lives, which files everything depends on. Every subcommand reads the
same deterministic code graph at .dxkit/reports/graph.json (symbols,
call edges, and Louvain-clustered modules, extracted by graphify). It
doesn't run analysis; it queries the graph the analyzers already built.
Usage
vyuh-dxkit explore <subcommand> [args] [--json] [--limit N] [--refresh]
If no graph artifact exists yet, run vyuh-dxkit health once (it writes
graph.json as a side effect), or pass --refresh to rebuild it.
Subcommands
| Subcommand | Question it answers |
|---|---|
entry-points |
"What does this repo do?" — high-fan-out symbols in route / primary-component paths |
hot-files |
"What's the foundational layer?" — files the most other files depend on |
communities |
"What are the natural modules?" — Louvain clusters with their dominant directory |
file <path> |
"What is this file, and who depends on it?" — symbols, callers, callees, imports |
feature <keyword> |
"Where is X implemented?" — clusters of symbols matching a keyword |
api-surface |
"What's the public API / what's dead?" — exported symbols with no internal callers |
context <query> |
Slim, token-budgeted structural slice for an LLM — see context |
Examples
vyuh-dxkit explore entry-points # top entry points by call out-degree
vyuh-dxkit explore hot-files --limit 30 # 30 most-depended-on files
vyuh-dxkit explore feature auth # where "auth" is implemented
vyuh-dxkit explore feature jwt --substring # broader (noisier) keyword match
vyuh-dxkit explore file src/server.ts # one file's structural neighborhood
vyuh-dxkit explore communities --json # natural modules, machine-readable
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 6d63094a23ca
explore 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 824 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.