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-prgit 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-pr)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-pr"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-pr"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00099 | $0.01633 |
| Opus 5.5 | $0.00040 | $0.00653 |
| Sonnet 5.5 | $0.00020 | $0.00327 |
| Haiku 4.5 | $0.00010 | $0.00163 |
Grade A, and why
dxkit-pr 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 1mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-pr
This skill turns a finished branch into a reviewable pull request: a title
and body grounded in what actually changed (not a generic template), and a
checklist that guides the reviewer through what to verify. It's the natural
close of dxkit-feature (built something) and dxkit-action (fixed findings) —
both hand off here when the work is ready for review.
A good PR description is written from the diff, not from memory. This skill reads the branch, summarizes it honestly, and attaches the dxkit signals (guardrail verdict, allowlist activity, score movement) a reviewer would otherwise have to reconstruct by hand.
The PR loop
[1] Compute → `vyuh-dxkit pr` builds the body from the real commits + diff
[2] Narrate → you write only "What & why"; tailor the computed checklist
[3] Confirm → show the user the draft; open with `gh pr create` on yes
The heavy lifting is one command. vyuh-dxkit pr reads base..HEAD and emits a
ready-to-review body with the parts that used to drift when hand-assembled:
- a title from the dominant conventional-commit type + scope,
- a Changes section bucketed by commit type (Features / Fixes / Refactors / …),
- the dxkit signals block (the receipt: guardrail verdict + allowlist delta),
- suggested reviewers (the active-owner model, blended with CODEOWNERS),
- a diff-derived reviewer checklist (a supply-chain row only when a manifest moved, a migration row only when a migration moved, a tests row when source changed without a test, …), and
- a Structural review section: functions this change adds that structurally match existing code — the seam signal as a reviewer prompt, not a block.
Everything there is computed from the branch, so the body can't misrepresent the change. Your job is the narrative ("What & why") and pruning/tailoring the checklist to the actual change.
vyuh-dxkit pr --base <base-branch> # markdown body on stdout
vyuh-dxkit pr --base <base-branch> --since <base-branch> # + health-score movement
vyuh-dxkit pr --base <base-branch> --json # every computed field, to parse
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.
- 1mo ago First seen · 130 lines · 99 tokens per session scan A c3d763979dcc
dxkit-pr is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 1,633 once invoked, about $0.0004 per session on Opus 5.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.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
ring:committing-changes
Commit changes with scope allowlist enforcement, atomic grouping, GPG-signed conventional commits, and trailer management. Detects the repo's PR-validation scope policy before proposing any message. Use when the user asks to commit or has changes ready to record. Skip when the working tree is clean or the user wants…
ring:opening-pull-requests
Open a GitHub Pull Request with automatic base branch detection, scope allowlist enforcement, PR template filling, and post-create base verification. Replaces ring:generating-pr-descriptions. Use after pushing a branch when ready to open a PR. Skip if the branch is not yet pushed or there are uncommitted changes …
ring:shipping-changes
End-to-end git orchestrator: branch → commit → push → PR, with a full plan presented before any execution. Detects base branch and scope allowlist once and propagates to all phases. Use when ready to ship a complete unit of work. Skip if only one phase is needed: commit-only → ring:committing-changes, PR-only →…
ring:generating-pr-descriptions
Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.