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-initgit 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-init)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-init"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-init/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-init"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 12 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 14 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 15 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 16 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 18 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 45 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 54 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 59 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 66 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 78 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 101 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 48 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 89 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.00071 | $0.01857 |
| Opus 5.5 | $0.00028 | $0.00743 |
| Sonnet 5.5 | $0.00014 | $0.00371 |
| Haiku 4.5 | $0.00007 | $0.00186 |
Grade A, and why
dxkit-init 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-init
This skill scaffolds dxkit on a repo: chooses flags, runs init, captures a baseline, and points at the next steps.
Decision tree
Ask the user what they want, then pick the right invocation:
- "Just give me everything" →
npm init @vyuhlabs/dxkit(collapses install + init), or if dxkit is already a devDep:npx vyuh-dxkit init --full --yes - "I only want the agent context, no guardrails yet" →
npx vyuh-dxkit init --with-dxkit-agents --yes - "I want guardrails but no CI" →
npx vyuh-dxkit init --with-hooks --with-dxkit-agents --yes - "I want the full setup but no pre-commit" →
--full --yesalready does this (pre-commit is opt-in via--with-precommit-hookbecause it's slow on large repos) - "Interactive — talk me through it" →
npx vyuh-dxkit init(no--yes) and let it prompt
Flag reference
| Flag | What it ships | Default under --full? |
|---|---|---|
--with-dxkit-agents |
The dxkit-* skills + AGENTS.md + CLAUDE.md shim | Yes |
--with-hooks |
.githooks/pre-push + postinstall activation wire-up |
Yes |
--with-precommit-hook |
Adds .githooks/pre-commit (slow on large repos) |
No (still opt-in) |
--with-devcontainer |
.devcontainer/devcontainer.json (per-stack features) + post-create.sh |
Yes |
--with-ci |
.github/workflows/dxkit-guardrails.yml (PR gate) — plus, when the stack declares a capability the ubuntu runner can't serve (e.g. a net*-windows build), a generated dxkit-gate-<host>.yml per required host; tell the user to mark it a required PR check alongside dxkit-guardrails |
Yes |
--with-baseline-refresh |
.github/workflows/dxkit-baseline-refresh.yml (post-merge regen; on a multi-environment stack with lint gating enabled it also captures each placed host's baseline slice and merges before committing) |
Yes |
--with-pr-review |
.github/workflows/pr-review.yml (AI PR review; needs ANTHROPIC_API_KEY) |
No (still opt-in) |
--claude-loop |
Stop-gate hook for autonomous loops (additive merge into .claude/settings.json + CLAUDE.md); implies the dxkit skills. Pair with --loop-preset security-only|full-debt |
No (opt-in — registers a hook that blocks the agent from stopping) |
--flow / --no-flow |
Set up / suppress the UI→API integration gate. When init detects a UI→API surface it offers this automatically (interactive prompt for the posture); --flow forces it on with warn, --no-flow skips it. There is no standalone flow init — flow setup lives inside init. |
Auto-offered when a UI→API surface is detected (silent otherwise) |
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 · 103 lines · 71 tokens per session scan A 04d43563c4a4
dxkit-init is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,857 once invoked, about $0.0003 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-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.