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 skills add vyuh-labs/dxkit --skill 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/skills/vyuh-labs/dxkit/dxkit-uninstall)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-uninstall"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-uninstall/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-uninstall"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-uninstall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 24 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 27 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 56 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.1 | $0.00123 | $0.01320 |
| Opus 5.5 | $0.00049 | $0.00528 |
| Sonnet 5.5 | $0.00025 | $0.00264 |
| Haiku 4.5 | $0.00012 | $0.00132 |
Grade A, and why
dxkit-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 1mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-uninstall
This skill owns removing dxkit from a repo. Its one guarantee: after uninstall, the repo is back to its exact pre-dxkit state — every file dxkit created is gone, and every additive change dxkit made to a file you already had is reversed, leaving your own content byte-for-byte intact.
What it removes vs reverts
dxkit's footprint falls into two kinds, handled differently:
- Files dxkit created (they didn't exist before):
.dxkit/, thedxkit-*skills under.claude/,AGENTS.md, the git hooks in.githooks/, thedxkit-*GitHub workflows,.dxkit-ignore, and.vyuh-dxkit.json. These are removed outright. - Additive merges into files you already had: the
.gitignoreruntime-output block, theCLAUDE.mdloop block (between<!-- dxkit:loop:start -->/end -->), the.claude/settings.jsonhooks (context-hook/stop-gate), and thepackage.json@vyuhlabs/dxkitdevDependency + postinstall. These are surgically reverted — only dxkit's additions are stripped; your keys, prose, and formatting are preserved.
It knows exactly what is dxkit's because init recorded a manifest (.vyuh-dxkit.json) with a hash of every created file. A dxkit-created file you have since edited is surfaced and skipped (not clobbered) unless you pass --force.
How to run it
# 1. Dry run FIRST (default) — prints exactly what will be removed/reverted,
# changes nothing.
npx vyuh-dxkit uninstall
# 2. Apply it.
npx vyuh-dxkit uninstall --yes
Useful flags:
--remove-devdep— also remove the@vyuhlabs/dxkitdevDependency + postinstall frompackage.json(kept by default so a lockfile install doesn't break mid-cleanup). After it editspackage.json, run your package manager's install to prune the lockfile — the CLI prints the exact command for your PM (npm ci/pnpm install/yarn install/bun install).--keep-baselines— keep the curated, git-tracked artifacts (.dxkit/baselines/, the allowlist,.dxkit/external/) and remove only the runtime state. Use this if you want to pause dxkit but keep your grandfathered debt inventory.--force— also remove dxkit-created files you have edited (default: skip + warn).--no-feedback— skip the feedback prompt.--json— machine-readable plan/result.
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.
- 1mo ago First seen · 62 lines · 123 tokens per session scan A cc192286956f
dxkit-uninstall is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 1,320 once invoked, about $0.0005 per session on Opus 5.5. 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-09-03.
Other skills, from other repositories
release-habit-hooks
Cut a new release of the habit-hooks packages. Use when asked to release, publish, or bump the version. Reviews what lands, enforces the in-sync versioning rule, validates the changelog, and drives the tag-triggered PyPI publish.
cut-release
Cut a clean release — bump versions across all files, update changelog, create GitHub release.
merge-to-main
Babysit a PR through CI — create, monitor, fix failures, merge when green.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.
release
This skill should be used when the user asks about "release process", "versioning", "semantic versioning", "semver", "release automation", "publishing", "package publishing", "release checklist", "version bump", "release notes", or needs guidance on release workflows and version management.