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/loopgit 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.01917 |
| Opus 5 | $0.00000 | $0.00958 |
| Sonnet 5 | $0.00000 | $0.00383 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
loop 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 yesterday.
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit loop + vyuh-dxkit hook stop-gate
Run as:
vyuh-dxkit <cmd>afternpm install -g @vyuhlabs/dxkit, ornpx @vyuhlabs/dxkit <cmd>for one-shot use.
The loop pack is dxkit's deterministic preflight/postflight layer for
autonomous coding loops — a Claude Code session that keeps working until it
decides to stop. It stops a loop from declaring "done" while it has
introduced net-new findings, by re-running the guardrail
on every Stop and feeding any net-new findings back to the model for repair.
The value is predictability, not new detection: the gate bounds the "loop shipped debt and never fixed it" failure mode to zero using the findings, baseline, and identity contract dxkit already computes. It is not a new scanner.
Setup
# Register the Stop hook + CLAUDE.md loop norm + default preset.
# Additive: merges into an existing .claude/settings.json + CLAUDE.md
# without clobbering your hooks or prose. Implies the dxkit skills.
vyuh-dxkit init --claude-loop [--loop-preset security-only|full-debt]
This is opt-in even under init --full, because it registers a hook that
blocks the agent from stopping. See init.
vyuh-dxkit hook stop-gate
The body of the Claude Code Stop hook. Not run by hand — init --claude-loop registers it in .claude/settings.json:
{
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "cd \"${CLAUDE_PROJECT_DIR:-.}\" && npx vyuh-dxkit hook stop-gate"
}
]
}
]
}
}
It reads the hook payload from stdin, runs the guardrail against the baseline, and decides:
| Outcome | Condition | Mechanism |
|---|---|---|
| Allow stop | No net-new findings (and the optional test command passed) | exit 0, no decision |
| Block → model | Net-new findings the model can fix | exit 0 + {"decision":"block","reason":"…"} on stdout — the reason reaches the model so it repairs, then tries to stop again |
| Block → operator | Guardrail couldn't run (no baseline / config error) | exit 2 + stderr to the operator (the model can't fix a preflight problem); allows on the next attempt to avoid thrashing |
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.
- yesterday First seen · 176 lines · 0 tokens per session scan A 920bd29f59b7
loop 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,917 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.