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/uninstallgit 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/uninstall)<a href="https://agentmods.dev/commands/vyuh-labs/dxkit/uninstall"><img src="https://agentmods.dev/badge/commands/vyuh-labs/dxkit/uninstall.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.00803 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
uninstall 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit uninstall
Remove dxkit and restore the repo's pre-dxkit state: delete every file
dxkit created, and surgically reverse every additive merge dxkit made
into a pre-existing file, without touching a byte the user owns. The
command is dry-run by default; nothing changes until you pass --yes.
Usage
vyuh-dxkit uninstall [path] # dry run: show the plan, change nothing
vyuh-dxkit uninstall [path] --yes # apply the plan
Options
| Option | Effect |
|---|---|
--yes |
Apply the plan (without it, the command only prints the plan) |
--keep-baselines |
Keep the curated git-tracked artifacts under .dxkit/ (see below) |
--remove-devdep |
Also strip the @vyuhlabs/dxkit devDependency + postinstall, and any tool devDeps dxkit added, from package.json |
--force |
Remove dxkit-created files even if you edited them (default: skip + warn) |
--no-feedback |
Skip the optional prefilled feedback-issue link at the end |
--json |
Emit the plan (empty, warnings, actions) and exit without applying |
Behavior
The plan is built from the install manifest (.vyuh-dxkit.json) and its
per-file provenance:
- Created files are deleted. A manifest entry recorded as created or
overwritten by dxkit is removed. Non-evolving files are hash-guarded:
if you edited one since dxkit wrote it, it is skipped and warned about
unless you pass
--force. - Your files are never deleted. An entry with
skippedprovenance is a file that pre-existed dxkit; it is left alone even under--force. - Merged files are reverted, not deleted.
.gitignore,CLAUDE.md,.claude/settings.json, andpackage.jsonget dxkit's additions stripped while your content is preserved (byte-preserving JSON serialization for the JSON files). The.vscodeJSONC file association for.dxkit/policy.jsonis removed, andcore.hooksPathis unset if dxkit pointed it at.githooks. - Managed artifacts (CI workflows, git hooks, devcontainer, skills)
are removed via the same registry
initandupdateread, so a surface cannot be installed by one path and missed by this one. - Runtime state.
.dxkit/is removed entirely (baselines, reports, loop, policy). With--keep-baselines, the curated committed artifacts survive:baselines/, the allowlist (and its reasons sidecar),external/,flow/, andworkspace.json. - The manifest goes last. If any edited file was skipped, the
manifest is kept so a later
uninstall --forcecan still find and remove it.
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.
- 3d ago First seen · 64 lines · 0 tokens per session scan A 688edf8dfcf2
uninstall 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 803 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
brooks-audit
Run a Brooks-Lint architecture audit.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
research
Research a technical or product question.