Borrowing it
Nothing to install: this file belongs to vyuh-labs/dxkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vyuh-labs/dxkit/main/CLAUDE.mdgit 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/instructions/vyuh-labs/dxkit/claude-md)<a href="https://agentmods.dev/instructions/vyuh-labs/dxkit/claude-md"><img src="https://agentmods.dev/badge/instructions/vyuh-labs/dxkit/claude-md/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/instructions/vyuh-labs/dxkit/claude-md"><img src="https://agentmods.dev/badge/instructions/vyuh-labs/dxkit/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.24268 | $0.24268 |
| Opus 5.5 | $0.09707 | $0.09707 |
| Sonnet 5.5 | $0.04854 | $0.04854 |
| Haiku 4.5 | $0.02427 | $0.02427 |
Grade A, and why
dxkit CLAUDE.md scanned grade A with 2 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
CLOSED on mismatch. The arch-check bans a raw curl/wget-with-URL in Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
content-scan inside `run()` / `execSync()` outside the 4-file How it starts
The opening of the file, as written. The whole thing — 1,660 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — DXKit Development Rules
Architecture Rules
1. Tool invocation goes through the registry
Every external tool (cloc, gitleaks, semgrep, graphify, jscpd, ruff, etc.) MUST be:
- Defined in
src/analyzers/tools/tool-registry.ts(TOOL_DEFS) - Detected via
findTool(TOOL_DEFS.xxx, cwd)— never hardcode binary paths - Installed via
vyuh-dxkit tools install— never ad-hoc npx/pip calls
Builtins (grep, find, wc, git, node) are exempt — they're always available.
Executed downloads are checksum-verified (4.0.3 / T2.1). Any network
artifact an install command fetches goes through
dxkit_fetch <url> <sha256> <dest> — defined ONCE in
src/analyzers/tools/install-exec.ts (the single install executor prepends
it), with the pinned hash declared in the registry beside the URL. It fails
CLOSED on mismatch. The arch-check bans a raw curl/wget-with-URL in
tool-registry.ts and an Invoke-WebRequest without a Get-FileHash check
(annotate // unverified-download-ok for a justified exception);
test/tool-registry-version-pins.test.ts pins that every dxkit_fetch call
carries a 64-hex sha and that no unverified fetch exists in any install
command. Bumping a tool version means re-pinning its hash (prefer the
publisher's published checksum file where one exists — gitleaks, codeql).
CI tool discoverability is registry-derived, never a hardcoded PATH. The
places a tool binary can live are declared once — getSystemPaths() plus each
tool's probePaths in the registry — and findTool probes them. The CI PATH
export (exportToolPathsToGithubEnv, run at the end of tools install) reads
the SAME sources and writes them to $GITHUB_PATH, so the per-language dep audit
finds its native scanner (osv-scanner / pip-audit / govulncheck / cargo-audit)
in a workflow step instead of silently falling back to a wrong-artifact scanner.
A new language pack that installs a scanner to a new directory declares it in the
tool's probePaths (already required for detection) and is thereby covered in CI
automatically — do NOT hardcode a per-ecosystem bin dir in a workflow template.
test/tool-paths-ci.test.ts pins that every tool probePath appears in the
export.
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 · 1,660 lines · 24,268 tokens per session scan A ae117133b1a5
dxkit CLAUDE.md is an instructions file published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 1mo ago), licensed MIT. It adds 24,268 tokens to every session, about $0.0971 per session on Opus 5.5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.