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-ingestgit 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-ingest)<a href="https://agentmods.dev/skills/vyuh-labs/dxkit/dxkit-ingest"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-ingest/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-ingest"><img src="https://agentmods.dev/badge/skills/vyuh-labs/dxkit/dxkit-ingest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 30 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 64 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 35 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 65 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 80 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 81 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 93 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 102 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00131 | $0.02477 |
| Opus 5 | $0.00066 | $0.01239 |
| Sonnet 5 | $0.00026 | $0.00495 |
| Haiku 4.5 | $0.00013 | $0.00248 |
Grade A, and why
dxkit-ingest 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 9d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dxkit-ingest
dxkit's bundled SAST (community semgrep) is intraprocedural — it cannot follow tainted data across function boundaries. The findings that dominate a Snyk Code or CodeQL report (path traversal, information exposure, SSRF, injection) are interprocedural and live outside that engine. This skill brings those findings INTO dxkit so they become first-class: fingerprinted, deduped against native findings, written to the baseline, enforced by the guardrail, linked to the code graph, and fixable through dxkit-action.
dxkit is not re-detecting — it's orchestrating. The detection engine stays whatever the customer can run; dxkit owns the governance + agentic-fix loop on top of it.
Pick the engine (license-aware)
Run the resolver's logic before ingesting:
| Situation | Engine | Why |
|---|---|---|
| Customer already runs Snyk (any tier, incl. free) | Snyk Code via REST | Reads stored findings — consumes no Snyk test quota. Their own license. |
| Customer already runs SonarQube / SonarCloud (common in .NET/Java shops) | Sonar via Web API | Reads the already-computed issues — no analysis re-run. Their own license; deepest C#/Java coverage most enterprises have. |
| Open-source repo | CodeQL on-demand | CodeQL's CLI is licensed for open source. |
| Private repo with GitHub Advanced Security | CodeQL on-demand | GHAS covers private-repo CodeQL. Confirm consent first. |
| Private repo, no GHAS, no Snyk | stay on community semgrep | No licensed interprocedural engine available. Don't run CodeQL on private code without GHAS. |
Never run CodeQL against a non-public repo without confirming the user has GitHub Advanced Security. dxkit prompts for this; honor it.
Path A — ingest Snyk Code
# Token: a Snyk API token from Snyk → Account settings → API token.
# dxkit reads it from the ENVIRONMENT — it does NOT auto-load a .env file.
export SNYK_TOKEN=... # in CI, add this once as a repo/org Actions secret
# org/project resolve from the flag, then .vyuh-dxkit.json, then the
# environment (SNYK_ORG_ID / SNYK_PROJECT_ID) — so an exported shell needs
# no flags. The project id is the project page URL in the Snyk UI.
npx vyuh-dxkit ingest --from-snyk --org <org-id> --project <project-id>
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.
- 9d ago First seen · 128 lines · 131 tokens per session scan A 1c8d069f6ac0
dxkit-ingest is a skill published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 11d ago), licensed MIT. It adds 131 tokens to every session and 2,477 once invoked, about $0.0007 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.
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…