A setup and verification procedure for a local ShadowDusk build. It installs or checks prerequisites, builds the project, runs its test suite, and can optionally check GPU rendering on Windows.

Use it after cloning the repository, when setting up a machine, or when checking a build, tests, and optional GPU render gates.

It gives a new contributor a repeatable way to find out whether their checkout and development environment work, instead of treating a partial build or passing test command as full verification.

local-test — Skill for Claude Code by kaltinril: A setup and verification procedure for a local ShadowDusk…

Install

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.

agentmods

npx agentmods add skills/kaltinril/shadowdusk/local-test

Any agent

npx skills add kaltinril/ShadowDusk --skill local-test

Clone the repo

git clone --depth 1 https://github.com/kaltinril/ShadowDusk

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kaltinril/shadowdusk/local-test.svg)](https://agentmods.dev/skills/kaltinril/shadowdusk/local-test)

Your own site

<a href="https://agentmods.dev/skills/kaltinril/shadowdusk/local-test"><img src="https://agentmods.dev/badge/skills/kaltinril/shadowdusk/local-test.svg" alt="Measured on agentmods" height="20"></a>

Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,469 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00085	$0.01469
Opus 5	$0.00043	$0.00734
Sonnet 5	$0.00017	$0.00294
Haiku 4.5	$0.00009	$0.00147

Measured yesterday against content hash 3f6b1cee2738, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

local-test 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.

.claude/skills/local-test/SKILL.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Local testing setup

The one command that takes a clone to a verified build is tools/setup-local-testing.ps1. It needs PowerShell 7+ (pwsh), which runs on Windows, Linux and macOS.

pwsh tools/setup-local-testing.ps1                              # build + full test suite
pwsh tools/setup-local-testing.ps1 -WithRenderGates             # + the GPU render proofs (Windows)
pwsh tools/setup-local-testing.ps1 -SkipTests                   # build only

It prints a PASS/WARN/FAIL line per step and exits non-zero if anything failed. Nothing is silently skipped: a step that cannot run says why and gives the command that fixes it.

The one thing to tell people first

There are two halves to verifying ShadowDusk, and the script only runs both if asked.

Half	What it proves	Command
`dotnet test`	the compiler behaves	the default run
the render gates	the output actually loads and renders like `mgfxc`/`fxc` in the real engine	`-WithRenderGates`

Only the second is the product bar (rung 4). It needs Windows and a real GPU, so it cannot run in CI and it cannot run on a Mac or Linux box. If someone says "tests pass", ask which half they ran.

Prerequisites worth pre-empting

Both .NET 8 and .NET 10 SDKs. The shipped libraries multi-target net8.0+net10.0, so a box with only one SDK cannot build the solution at all. This is the single most common first-run failure.
dotnet tool restore — supplies the pinned dotnet-mgcb. The MGCB plugin gate and the XNB Content.Load gate both need it. The script does this for you.
python — only for the render gates' image comparisons. Irrelevant otherwise.
A DX12-capable GPU for the DX12 gates; -SkipVulkan on the gate script for a box with no Vulkan GPU.

Trying the things Victor Chelaru asked for

.xnb output (issue #199) — shipped. Name an .xnb output path and the CLI wraps it, so Content.Load<Effect>("Foo") works with no consumer code change:
```
dotnet run --project src/ShadowDusk.Cli -- MyShader.fx Content/MyShader.xnb /Profile:OpenGL
```
From the library it is CompiledShader.ToXnb(). The rung-4 proof is dotnet run --project validation/XnbContentLoad -c Release, which loads both a stock mgcb build and ours through a real ContentManager and pixel-compares.

Read the full file on GitHub · 99 lines

Changes

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 · 99 lines · 85 tokens per session scan A 3f6b1cee2738

Subscribe to this mod's changes

local-test is a skill published in the GitHub repository kaltinril/ShadowDusk (14 stars, last pushed 22d ago), licensed MIT. It adds 85 tokens to every session and 1,469 once invoked, about $0.0004 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-09-04.

Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens