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-reportsgit 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-reports)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-reports"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-reports.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.00129 | $0.02074 |
| Opus 5 | $0.00064 | $0.01037 |
| Sonnet 5 | $0.00026 | $0.00415 |
| Haiku 4.5 | $0.00013 | $0.00207 |
Grade A, and why
dxkit-reports 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 7d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-reports
This skill runs dxkit analyzers and reads their output back to the user. It's the "tell me how my codebase is doing" surface.
Command map
| User asks | Command | Output |
|---|---|---|
| "Overall health" / "give me the score" | npx vyuh-dxkit health |
6-dimension score table + top actions per dimension |
| "Check security" / "find vulns" | npx vyuh-dxkit vulnerabilities |
Code-level SAST + dep-vuln + secret findings, grouped by severity |
| "Test coverage gaps" | npx vyuh-dxkit test-gaps |
Source files without matching tests, prioritized by architectural role |
| "Code quality" | npx vyuh-dxkit quality |
Lint findings + duplication + slop score |
| "Who's been working on what" | npx vyuh-dxkit dev-report |
Per-author activity, hot files, churn |
| "License inventory" | npx vyuh-dxkit licenses |
Every dependency's declared license |
| "Bill of materials" | npx vyuh-dxkit bom |
Licenses + dep vulnerabilities joined (15-col XLSX-ready output) |
| "Run everything" | npx vyuh-dxkit report |
Every analyzer in one shot, ~3-5 min |
| "What has dxkit caught for us / ROI" | npx vyuh-dxkit metrics |
Findings the gate blocked before merge, per week + by category (from the loop ledger) |
| "How has the score moved over time" | npx vyuh-dxkit report trend |
Per-dimension score-over-time sparklines since the first snapshot on record, from the on-merge snapshots; segmented at scoring-methodology boundaries so cross-version blips never read as real movement |
| "Show me the dashboard" | npx vyuh-dxkit dashboard |
Single HTML view of all reports — opens at .dxkit/reports/dashboard.html, incl. an interactive Graph tab (code structure) |
| "What does this repo do / where is X" | npx vyuh-dxkit explore <sub> |
Query the code graph: entry-points / hot-files / communities / file / feature / api-surface |
| "Token-efficient context for a query" | npx vyuh-dxkit context <query> |
Slim structural slice for an LLM (also a fix-time hint via --graph-context) |
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.
- 7d ago First seen · 145 lines · 129 tokens per session scan A 9d5ea9e96e45
dxkit-reports is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 9d ago), licensed MIT. It adds 129 tokens to every session and 2,074 once invoked, about $0.0006 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
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).
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-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.
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…
explore-codebase-cli
MUST BE USED PROACTIVELY. Universal JVM (Java + Kotlin) codebase exploration (CLI surface): graph navigation (jrag callers/callees/routes/impact/flow/…) plus jrag search (locate code/config by meaning or keywords) and file-system search. Use for any exploration task: locating code, tracing dependencies, finding…
investigate
Manage structured investigations with multi-agent evidence collection, synthesis, tagging, and PHI sanitization. Use when user says "start an investigation", "root cause analysis", or "collect evidence about X". Subcommands: new, run, collect, synthesize, close, status, list, search. Do NOT use for casual debugging or…