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/configuregit 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/commands/vyuh-labs/dxkit/configure)<a href="https://agentmods.dev/commands/vyuh-labs/dxkit/configure"><img src="https://agentmods.dev/badge/commands/vyuh-labs/dxkit/configure.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 | $0.00000 | $0.00588 |
| Opus 5 | $0.00000 | $0.00294 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
configure 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 4d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit configure
Compute a deterministic configuration plan for this repo, and optionally
apply it. Each capability in the command registry declares a pure
planConfig probe that derives its recommended settings from observable
repo facts, so the same repo yields the same plan on every run and in
every environment. There is no judgment call: every plan line cites the
evidence that forced it.
Usage
vyuh-dxkit configure [path] # show the plan (nothing written)
vyuh-dxkit configure [path] --apply # merge the plan into .dxkit/policy.json
vyuh-dxkit configure check [path] # CI drift detector (exit 1 if un-applied)
Options
| Option | Effect |
|---|---|
--apply |
Write the plan into .dxkit/policy.json (default is plan-only) |
--json |
Structured output (configure.v1 / configure-apply.v1 / -check.v1) |
Behavior
- Plan (default). Shows each recommended section with a summary, the reason, and the repo evidence behind it. Nothing is written.
--apply. Deep-merges the plan into.dxkit/policy.json, preserving every existing key (a malformed existing policy is left intact and reported, never overwritten). Idempotent: a section that is already pinned goes silent in the plan, so re-running is a no-op. After a write, any managed workflows the newly enabled knobs gate are re-rendered through the same reconciliationpolicy setuses, so a knob is never left on with nothing serving it.configure check. Exits non-zero when the plan is non-empty, that is, when a capability's recommended config has not been applied (a newly shipped capability, or a section someone removed). It verifies completeness only: a section deliberately set to a non-computed value is treated as a pinned override and respected, not flagged.- Registry-driven. The plan iterates the capability registry, so a
capability that ships tomorrow with its own
planConfigjoins the plan automatically.
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.
- 4d ago First seen · 54 lines · 0 tokens per session scan A 678581b8d1fe
configure is a command published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 588 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
setup
Bootstrap a repository with AI-native CI/CD, hooks, and templates in one command.
setup
Initialize a new project with SDLC-compliant structure. Creates required files, configures build system, sets up CI/CD, and establishes quality tooling.
prep
Prepare a repository's verification infrastructure for this system — the three-command interface (check / check- / golden), the metric-class gates (stack-agnostic — the class is the requirement, the tool is an instance), the golden harness skeleton, minimum CI, and the ratchet baseline. Brownfield-safe: detect…
ci-init
Create a GitHub Actions workflow for RepoVista.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.
release
Cut a release — derive the version, close the review, rewrite CHANGELOG, commit, push, wait for CI, tag, wait for the Release workflow and the GitHub release, then wait until the version is live on NuGet.