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-docsnpx skills add vyuh-labs/dxkit --skill dxkit-docsgit 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-docs)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-docs"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-docs.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.00093 | $0.01616 |
| Opus 5 | $0.00046 | $0.00808 |
| Sonnet 5 | $0.00019 | $0.00323 |
| Haiku 4.5 | $0.00009 | $0.00162 |
Grade A, and why
dxkit-docs 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-docs
This skill closes the gap dxkit-action doesn't: it generates missing
documentation rather than fixing flagged findings. It's built around one
hard constraint — dxkit's own quality scan flags AI-slop prose, so
documentation that reads like generated filler lowers the Quality score
while raising Documentation. The whole point of this skill is docs that
are grounded in the real code and survive the slop check.
The docs loop
[1] Read the gap → health Documentation deductions + top actions
[2] Orient → graph: what are the real entry points, modules, public API
[3] Generate → write the missing artifact, grounded in actual symbols/paths
[4] De-slop → write like a human; re-run quality so it doesn't trip slop
[5] Verify → re-run health; Documentation up, slop not down
Don't skip [2] or [4]. [2] is what keeps the docs true; [4] is what keeps them from costing you on another dimension.
[1] Read the gap — what's actually missing
The Documentation dimension scores a fixed checklist. Read its deductions and ranked actions instead of guessing:
npx vyuh-dxkit health --detailed --json | jq '.dimensions.documentation'
The deductions array names each missing/substandard artifact; topActions
ranks them by score uplift. The scored artifacts are:
| Artifact | What moves the score |
|---|---|
| README | Present, and substantial (not a 5-line stub) |
| Doc-comment density | Share of source files carrying docstrings / JSDoc / Rustdoc |
| API docs | docs/api/, OpenAPI/Swagger spec |
| Architecture docs | ARCHITECTURE.md or docs/architecture/ |
| CONTRIBUTING | CONTRIBUTING.md |
| CHANGELOG | CHANGELOG.md |
Work the topActions order — the README and doc-comment density weigh
heaviest, CHANGELOG lightest.
[2] Orient — document the code that's actually there
Docs that describe code which doesn't exist are worse than no docs. Before writing a word, learn the real shape from the graph (cheap, structural):
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 · 151 lines · 93 tokens per session scan A 522c626924cd
dxkit-docs is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 7d ago), licensed MIT. It adds 93 tokens to every session and 1,616 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
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or…
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).
ring:creating-handoffs
Creating a handoff document that captures session state (completed work, decisions, open items, next steps) and delivering it via Plan Mode so the user gets the native 'clear context and continue implementing' resume option. Use when ending a session, when context grows large, or the user says 'handoff', 'save…
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.