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 skills/vyuh-labs/dxkit/dxkit-initnpx 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.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.00071 | $0.01857 |
| Opus 5 | $0.00036 | $0.00928 |
| Sonnet 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 5d 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.
- 5d 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 7d ago), licensed MIT. It adds 71 tokens to every session and 1,857 once invoked, about $0.0004 per session on Opus 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
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).
habit-hooks-prompting
Write or revise a habit-hooks coaching prompt. Use when a linter / knip / jscpd rule fires and the agent's default fix is wrong or shallow, or when adding a project-local override prompt. Keeps prompts short and outcome-focused using the ROSE pattern.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
explore-codebase
MUST BE USED PROACTIVELY. Universal read-only codebase exploration. Combines jrag graph navigation (call chains, routes, service boundaries, impact analysis, FQN resolution) with broad file-system search (grep, glob, file reading). Use for any exploration: locating code, tracing dependencies, finding patterns, 'where…
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.