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/describegit clone --depth 1 https://github.com/vyuh-labs/dxkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/vyuh-labs/dxkit/describe)<a href="https://agentmods.dev/commands/vyuh-labs/dxkit/describe"><img src="https://agentmods.dev/badge/commands/vyuh-labs/dxkit/describe.svg" alt="Measured on agentmods" height="20"></a>What 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.00722 |
| Opus 5 | $0.00000 | $0.00361 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
describe 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit describe
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 shareable snapshot of what dxkit sees in a repository: the whole code graph (every function, what it calls, and what calls it), joined to the HTTP contract when one exists (routes served, calls made, and how they bind). It reads the same deterministic analysis the gate uses and adds no new heuristics.
describe is read-only. It prints a terminal summary and writes nothing
to your repository unless you pass --out.
Usage
vyuh-dxkit describe [path] [--json] [--html] [--out <file>]
With no flags it prints a terminal summary. Every count it reports is
labeled observed / derived / inferred / unknown, so the picture
is honest about what was read directly versus resolved.
Flags
| Flag | Effect |
|---|---|
--json |
Emit the versioned repo card (dxkit.repo-card.v1) to stdout, for tooling |
--html |
Emit a self-contained, interactive contract-map HTML page to stdout |
--out <file> |
Write the output (HTML or JSON) to a file instead of stdout |
path |
Repository to describe (defaults to the current directory) |
The contract map
--html produces one self-contained file: no server, no API key, no
external assets. Open it in a browser and it renders a live, force-directed
map with three views:
| View | Shows |
|---|---|
| Full code graph | The whole code graph: functions sized by fan-out, with the contract overlaid |
| Request paths | Each route to its handler to the internal functions it fans out to |
| Seam | Every endpoint as a color-coded tile, laid out for a health scan at a glance |
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.
- 4d ago First seen · 73 lines · 0 tokens per session scan A 05db81dc44b5
describe is a command published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 722 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
setup
Bootstrap a repository with AI-native CI/CD, hooks, and templates in one command.
setup
Initialize a new project with SDLC-compliant structure. Creates required files, configures build system, sets up CI/CD, and establishes quality tooling.
prep
Prepare a repository's verification infrastructure for this system — the three-command interface (check / check- / golden), the metric-class gates (stack-agnostic — the class is the requirement, the tool is an instance), the golden harness skeleton, minimum CI, and the ratchet baseline. Brownfield-safe: detect…
ci-init
Create a GitHub Actions workflow for RepoVista.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.
release
Cut a release — derive the version, close the review, rewrite CHANGELOG, commit, push, wait for CI, tag, wait for the Release workflow and the GitHub release, then wait until the version is live on NuGet.