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/issuegit 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.01196 |
| Opus 5 | $0.00000 | $0.00598 |
| Sonnet 5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
issue 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit issue
Open a pre-filled GitHub Issue against vyuh-labs/dxkit in your
default browser. Use it when you want to report a false positive,
a missing finding, a dxkit bug, a feature request, or a docs gap.
The dxkit team triages issues in GitHub Issues — this CLI is the fastest path from "I noticed something" to "the team has a ticket they can search, dedup, and assign."
Why this exists
The team needs customer signal to improve dxkit:
- False positives tell us a scanner rule is too noisy.
- Missing findings tell us a rule is too narrow.
- Bugs tell us the install / hook / report pipeline broke.
- Feature requests tell us where the product should grow.
- Docs gaps tell us where the install/usage story confuses real users.
Sending these to GitHub Issues (rather than email or a web form) keeps triage centralized — labels, assignees, dedup search, notifications. You also get a public link to your own issue so you can subscribe to status updates.
Usage
# Interactive — opens browser to the new-issue form pre-filled
# with env info + your description
vyuh-dxkit issue --type=bug --about="vyuh-dxkit doctor crashes on macOS arm64"
# Report a false positive against a specific finding
vyuh-dxkit issue --type=false-positive \
--fingerprint=a3f9c0e8b7d2e1f4 \
--about="the scanner flags my intentional test-fixture API key"
# Feature request — no fingerprint needed
vyuh-dxkit issue --type=feature-request \
--about="add SARIF export to vulnerabilities subcommand"
# Print URL to stdout instead of opening a browser
# (useful in CI / SSH sessions without a browser handler)
vyuh-dxkit issue --type=docs --about="..." --no-browser
Types
--type |
When to use | GitHub label |
|---|---|---|
false-positive |
Scanner flagged something that isn't actually an issue | false-positive |
missing-finding |
Scanner should have flagged something but didn't | missing-finding |
bug |
dxkit itself is broken (CLI crashes, report wrong, etc.) | bug |
feature-request |
New functionality you'd like | enhancement |
docs |
Documentation is wrong / missing / unclear | documentation |
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 · 133 lines · 0 tokens per session scan A 735613ad5f01
issue 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 1,196 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
brooks-audit
Run a Brooks-Lint architecture audit.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
research
Research a technical or product question.