upgrade

upgrade is a command for coding agents from vyuh-labs/dxkit. It costs 0 tokens per session (1,456 once invoked), scanned A, original, MIT.

A command-line upgrade tool for dxkit that updates both its installed npm package and the generated files in a customer repository.

In plain words
What is it for?
It helps upgrade dxkit, refresh development files and workflows, preserve reviewed allowlist entries when needed, and run a health check.
Why use it?
It prevents the binary and repository templates from becoming inconsistent after an upgrade, then checks the installation.

Command

Install

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.

agentmods
npx agentmods add commands/vyuh-labs/dxkit/upgrade
Clone the repo
git clone --depth 1 https://github.com/vyuh-labs/dxkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,456 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01456
Opus 5 $0.00000 $0.00728
Sonnet 5 $0.00000 $0.00291
Haiku 4.5 $0.00000 $0.00146

Measured 3d ago against content hash 44497f3c4bd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

upgrade 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 3d 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.

docs/commands/upgrade.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

vyuh-dxkit upgrade

Combined CLI for upgrading dxkit to a newer version. Wraps two stages — the npm binary and the in-repo scaffold — into a single command, with a plan-only preview mode that the dxkit-update agent skill consumes.

Why an upgrade CLI

dxkit ships in two layers, and an upgrade touches both:

  1. The binary@vyuhlabs/dxkit npm package. npm install @vyuhlabs/dxkit@<version> replaces the local install.
  2. The scaffold — files in the customer's repo (.devcontainer/, .githooks/, .claude/skills/dxkit-*/, AGENTS.md, CLAUDE.md, .github/workflows/dxkit-*.yml). vyuh-dxkit update refreshes these to match the new binary's templates.

Either step alone leaves an inconsistent install. vyuh-dxkit upgrade runs both, plus vyuh-dxkit doctor afterwards to verify operational health.

The scaffold-refresh step (vyuh-dxkit update) also migrates your baseline + allowlist when a release changes the finding-identity scheme: it re-anchors allowlist fingerprints onto the new scheme (preserving your reviewed suppressions) and regenerates the baseline, so the guardrail keeps working without a manual re-baseline. See update for details. Commit .dxkit/ afterward to finish the migration.

Usage

# Preview only — emit the upgrade plan, no mutations
vyuh-dxkit upgrade --plan
vyuh-dxkit upgrade --plan --json    # structured output for dxkit-update skill

# Execute — interactive (requires --yes today; no built-in prompt)
vyuh-dxkit upgrade --yes

# Pin to a specific version
vyuh-dxkit upgrade --target=3.1.0 --yes

# Print the commands without executing
vyuh-dxkit upgrade --yes --dry-run

Flags

Flag Effect
--plan Plan-only mode. Emits the UpgradePlan and exits. No mutations.
--json (Combine with --plan) Emit the plan as JSON instead of human-prose. Schema discriminator upgrade-plan.v1. Consumed by the dxkit-update skill.
--target=X.Y.Z Pin upgrade to a specific version. Default: latest from npm view @vyuhlabs/dxkit version.
--yes Skip interactive confirmation. Required for execution today (no built-in prompt; the dxkit-update skill handles confirmation conversationally).
--dry-run Print the commands without executing. Useful for risk-averse review before a real upgrade.

Read the full file on GitHub · 138 lines

Changes

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.

  1. 3d ago First seen · 138 lines · 0 tokens per session scan A 44497f3c4bd6

Subscribe to this mod's changes

upgrade is a command published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,456 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.