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/depsgit 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/deps)<a href="https://agentmods.dev/commands/vyuh-labs/dxkit/deps"><img src="https://agentmods.dev/badge/commands/vyuh-labs/dxkit/deps.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.00868 |
| Opus 5 | $0.00000 | $0.00434 |
| Sonnet 5 | $0.00000 | $0.00174 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
deps 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit deps
Deterministic dependency security bumps: turn the fixable subset of your dependency vulnerabilities into concrete, verified upgrades — planned from the scanners' own fix versions, applied with your repo's own package manager, verified by the correctness floor and the guardrail before anything lands. No LLM anywhere in the lane.
Usage
vyuh-dxkit deps bump [path] # plan only (dry run, writes nothing)
vyuh-dxkit deps bump --apply # execute the bumps + verify
vyuh-dxkit deps bump --apply --land pr # …and land ONE standing PR (dxkit/dep-bump)
Options
| Flag | Meaning |
|---|---|
--apply |
Execute the planned bumps (default: dry-run plan only) |
--allow-major |
Include producer-classified major (breaking) bumps — skipped-and-named otherwise |
--land pr |
Commit manifest + lockfile to the standing dxkit/dep-bump branch and open/update the PR |
--json |
Machine-readable result (deps-bump.v1), including the full skip list and the ledger |
How the plan is built
The lane consumes the same enriched dep-vuln findings the vulnerability report renders. A bump is proposed only when a tool resolved a concrete target version:
- a structured upgrade plan (from the Tier-2 fix tools / the transitive resolver) wins — "upgrade this direct dependency to X to close N transitive advisories";
- a direct dependency with a scanner-reported
fixedVersionis the fallback; - everything else is skipped and named: no fix available, transitive
without a resolved parent, breaking without
--allow-major, already allowlisted, or a non-Node ecosystem (the apply lane is Node-first; other ecosystems' fix advice still renders in the reports).
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 · 84 lines · 0 tokens per session scan A b93ffa491b52
deps 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 868 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.
lrn
Execute the /vibeguard:learn command. $ARGUMENTS.
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.