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 commands/vyuh-labs/dxkit/dev-reportgit clone --depth 1 https://github.com/vyuh-labs/dxkitWhat 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.00000 | $0.00634 |
| Opus 5 | $0.00000 | $0.00317 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
dev-report 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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit dev-report
Run as:
vyuh-dxkit <cmd>afternpm install -g @vyuhlabs/dxkit, ornpx @vyuhlabs/dxkit <cmd>for one-shot use. Examples on this page use the short form.
Developer activity report. Per-author commit + line stats, per-week velocity, and a hot-files ranking.
Usage
vyuh-dxkit dev-report [path] [options]
Options
| Option | Effect |
|---|---|
--since YYYY-MM-DD |
Start of the analysis window. Defaults to ~90 days back. |
--detailed |
Write detailed report + JSON |
--json |
Stdout JSON |
--no-save |
Skip files |
What it shows
| Section | Source |
|---|---|
| Per-author summary | git log --author=* aggregation: commits, insertions, deletions, files touched, first/last commit date |
| Weekly velocity | Commits + lines changed per ISO week. Empty weeks are filled with zeros so the trend is readable. |
| Hot files | Top files by commit count in the window, with autogen-file filtering applied (no more Form.Designer.cs topping the list). |
| Authoring concentration | bus-factor estimate per file |
Output
## Authors (4)
| Author | Commits | + | - | First | Last |
| ----------------- | ------: | ----: | ----: | ---------- | ---------- |
| [email protected] | 42 | 1,832 | 1,201 | 2026-02-14 | 2026-05-13 |
| [email protected] | 28 | 903 | 612 | 2026-02-20 | 2026-05-12 |
## Weekly velocity
| Week | Commits | Lines changed |
| -------- | ------: | ------------: |
| 2026-W18 | 5 | 340 |
| 2026-W19 | 0 | 0 |
| 2026-W20 | 12 | 876 |
| 2026-W21 | 3 | 45 |
## Hot files (top 10 by commit count)
| File | Commits | Authors |
| -------------------- | ------: | ------: |
| src/services/data.ts | 18 | 3 |
| src/api/auth.ts | 15 | 2 |
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.
- 2d ago First seen · 69 lines · 0 tokens per session scan A 6f6bf706df29
dev-report is a command published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 634 tokens. 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 commands, from other repositories
readme-audit
Audit a README's reading flow by treating it as a conversion funnel. Every section is evaluated against a target reader and a terminal action. Produces a structured audit blueprint that feeds directly into /readme-restructure.
readme-restructure
Execute a /readme-audit blueprint. Rewrites the README to the evaluator → conversion → links structure and creates linked docs by extracting and reorganising existing content.
setup
Initialize a new project with SDLC-compliant structure. Creates required files, configures build system, sets up CI/CD, and establishes quality tooling.
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
run-tests
Run automated functional tests using the hook-driven test framework. Execute the test suite to validate all project functionality.
test-report
Generate test execution report in markdown format.