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-hooksgit 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-hooks)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-hooks"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-hooks.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.1 | $0.00066 | $0.01387 |
| Opus 5 | $0.00033 | $0.00694 |
| Sonnet 5 | $0.00013 | $0.00277 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade C, and why
dxkit-hooks scanned grade C 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .githooks How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-hooks
This skill handles the git-hook surface dxkit ships. Use it to install hooks, debug "the hook didn't fire," chain dxkit with an existing hook system, or guide a bypass.
What dxkit ships
.githooks/pre-push (default-on under --full) — runs the guardrail check before code leaves the developer's machine. Fast on warm scanner caches (~10-30s).
.githooks/pre-commit (opt-in via --with-precommit-hook) — same guardrail check but on every commit. Slower on large repos (~1-3 min on 500+ file repos). Not in --full by default because the wall-clock cost gates adoption.
Both run npx vyuh-dxkit guardrail check. The check exits 1 (blocking) on net-new findings vs. the baseline. The same check also runs the flow integration gate — a net-new broken UI→API integration (a call to an endpoint no backend serves, or a removed route a consumer still calls) blocks or warns per .dxkit/policy.json:flow.mode. To set up, diagnose, or repair that gate, hand off to the dxkit-flow skill.
Installation
# Pre-push only (recommended for most teams)
npx vyuh-dxkit init --with-hooks --yes
# Both pre-commit + pre-push
npx vyuh-dxkit init --with-hooks --with-precommit-hook --yes
# Add to an existing dxkit install (idempotent)
npx vyuh-dxkit init --with-precommit-hook --yes
Existing hooks at .githooks/<name> or .husky/<name> trigger sidecar-write mode: dxkit puts its hook at .githooks/<name>.dxkit and emits a chain note instead of clobbering.
Activation
Hooks activate by setting core.hooksPath = .githooks in the local git config. Dxkit wires this via npm postinstall so every clone + npm install runs it automatically. Manual:
# Either of these works
npx vyuh-dxkit hooks activate
git config core.hooksPath .githooks
npx vyuh-dxkit hooks activate is idempotent — refuses to clobber a custom hooksPath (husky's .husky, lefthook's .lefthook, etc.). Run it to confirm the current state.
Troubleshooting "hook didn't fire"
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.
- 6d ago First seen · 110 lines · 66 tokens per session scan C a775e06090ca
dxkit-hooks is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 9d ago), licensed MIT. It adds 66 tokens to every session and 1,387 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
prek-pro
Review, configure, and troubleshoot prek hooks when users need prek.toml edits, shim installs, hook validation, or pre-commit migration help.
bisect
Binary search for root cause: define a search space and a pass/fail oracle, then halve the space each step until the culprit commit, config key, or dependency is isolated. Works across git history, configuration, dependencies, or code modules.
merge-conflict-resolution
Detect, classify (porcelain status; complexity: trivial, semantic, structural, delete-modify), and resolve git merge conflicts through per-file strategy selection (accept-ours, accept-theirs, manual-merge, rebase), manual conflict hunk parsing, and post-resolution verification (orphaned markers, build, tests). Use…
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims.
refactoring-patterns
Apply safe refactoring patterns to improve code structure without changing behavior. Use when cleaning up code, reducing technical debt, or improving maintainability.