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-testnpx skills add vyuh-labs/dxkit --skill dxkit-testgit 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-test)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-test"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-test.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.00103 | $0.01802 |
| Opus 5 | $0.00051 | $0.00901 |
| Sonnet 5 | $0.00021 | $0.00360 |
| Haiku 4.5 | $0.00010 | $0.00180 |
Grade A, and why
dxkit-test 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-test
This skill closes the gap dxkit-action doesn't: it writes the missing
tests rather than fixing flagged findings. It is the testing mirror of
dxkit-docs — same shape, different dimension. It's built around one hard
constraint: a test that doesn't actually exercise behavior (an empty expect(true),
a snapshot of nothing, a call with no assertion) raises the coverage number
while proving nothing. The whole point of this skill is tests that are
grounded in real behavior and catch real regressions — not coverage
theater.
The testing loop
[1] Read the gap → test-gaps: the blast-radius-weighted untested worklist
[2] Orient → graph: what the file does, who depends on it, what to assert
[3] Generate → write real tests in the repo's framework + patterns
[4] Verify → run the suite + coverage; Tests up, nothing red
[5] Guardrail → guardrail check before pushing
Don't skip [2] or [4]. [2] is what makes the tests meaningful; [4] is what proves they pass and the coverage actually moved.
[1] Read the gap — what's actually untested, worst-first
Run the test-gaps report with graph context so the worklist is ranked by blast radius (how many files depend on each untested file), not just size:
npx vyuh-dxkit test-gaps --detailed --graph-context
npx vyuh-dxkit test-gaps --detailed --graph-context --json | jq '.actions, .gaps[0:10]'
The report partitions untested files into CRITICAL / HIGH / MEDIUM / LOW risk
tiers, and within each tier the most-depended-on files surface first (the
Graph context column shows role · N caller files). Work top-down: a
30-caller untested file is a bigger liability than a 500-line leaf nothing
calls. The actions array names the top-K per tier with projected
score uplift — that's your queue.
A blast radius n/a cell means graphify couldn't resolve that language's call
graph (C# is the known case) — treat it as unknown, not "no callers," and
fall back to the file's role + size to judge its risk.
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 · 154 lines · 103 tokens per session scan A 779d2a2afaf3
dxkit-test is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 7d ago), licensed MIT. It adds 103 tokens to every session and 1,802 once invoked, about $0.0005 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.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
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…