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-fixgit 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-fix)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-fix"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-fix/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-fix"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-fix.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00099 | $0.02879 |
| Opus 5.5 | $0.00040 | $0.01152 |
| Sonnet 5.5 | $0.00020 | $0.00576 |
| Haiku 4.5 | $0.00010 | $0.00288 |
Grade B, and why
dxkit-fix scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
3. **Suggest a manual workaround** if there's an obvious one (e.g. for global install failures, suggest `sudo npm install -g` on systems where the npm prefix isn't user-writable) How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-fix
This skill repairs broken dxkit installs. It does NOT install dxkit from scratch (that's dxkit-init) and it does NOT triage code findings (that's dxkit-action). Use it when something about the install itself is wrong — hooks not firing, vyuh-dxkit not on PATH, scanner toolchain missing pieces, baseline absent, etc.
How dxkit-fix works
The skill consumes npx vyuh-dxkit doctor --json output. Doctor returns a structured DoctorReport with a summary.fixable[] array — every failing check carries:
label— the problem in one linefix.hint— the human-readable explanationfix.command— the shell command that repairs it (optional)fix.skill— a more specific dxkit-* skill that can deep-dive (optional)
The skill iterates summary.fixable[], asks the customer for confirmation on each fix (with the command shown), runs it, then re-runs doctor at the end to verify everything closed.
Doctor also carries an optional top-level flow field when the repo has a UI→API surface — a diagnosis of the integration contract (unresolved client calls with reasons + suggestions, served routes nobody consumes, and how the served side is resolved). This is diagnostic, not an install fix: it does not appear in summary.fixable[], and dxkit-fix leaves it alone. It surfaces contract health (e.g. a call to a route no backend serves) rather than a broken-install signal.
The repair loop
[1] Run doctor in JSON mode → npx vyuh-dxkit doctor --json
[2] Read summary.fixable[] → enumerate broken signals + fix commands
[3] For each fixable:
[3a] Show the customer: label + hint + command
[3b] Confirm (default Y)
[3c] Run the command in their shell
[3d] Note success/failure
[4] Re-run doctor → verify the previously-fixable list is now empty
[5] Report what remains → any non-fixable failures + which dxkit-* skill handles them
Steps
1. Snapshot the broken state
npx vyuh-dxkit doctor --json > /tmp/dxkit-doctor.json
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 · 180 lines · 99 tokens per session scan B 6701c127ccc5
dxkit-fix is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 2,879 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
Code Coverage Analysis
Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.
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.
habit-hooks-review
Spawn a reviewer sub-agent to assess a change set against habit-hooks's coding principles. Use AFTER habit-hooks reports clean — habit-hooks catches structural smells; this catches what it cannot (correctness, tests, design, missed edge cases).
duo-build
Build an issue or feature interactively toward an indexed shared goal, with automatic read-only peer review; resume the same run across Claude Code and Codex.
specflow
Spec-driven development with executable contracts.
specflow-loop-selector
Choose the lightest Specflow workflow that covers an ask’s size, uncertainty and risk, then select a loop only when needed. Use for work triage, proportionate verification, loop selection, or explicit spec-build, feature-build and Gate D requests. A lightweight decision does not start a loop.