A test command for the ShadowDusk .NET project that runs unit tests by default and can also run integration tests, which check how multiple parts work together. It reports the results and a coverage summary.

Use it to run the fast unit-test set, run all tests, target a graphics platform, and check test coverage results.

It provides standard commands and a time limit for test runs, so a hanging integration suite fails instead of running indefinitely.

How kaltinril/ShadowDusk configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kaltinril/ShadowDusk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/kaltinril/ShadowDusk/main/.claude/commands/test.md

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/commands/kaltinril/shadowdusk/test/github.svg)](https://agentmods.dev/commands/kaltinril/shadowdusk/test)

Your own site

<a href="https://agentmods.dev/commands/kaltinril/shadowdusk/test"><img src="https://agentmods.dev/badge/commands/kaltinril/shadowdusk/test/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/kaltinril/shadowdusk/test"><img src="https://agentmods.dev/badge/commands/kaltinril/shadowdusk/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00000	$0.00440
Opus 5.5	$0.00000	$0.00176
Sonnet 5.5	$0.00000	$0.00088
Haiku 4.5	$0.00000	$0.00044

Measured 1mo ago against content hash 6bdb39b3fa3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

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/commands/test.md · 43 lines

What it actually says

/test — Run the ShadowDusk test suite

Runs all tests and reports results with coverage summary.

Suite-level timeout guardrail (Phase 21). --settings ShadowDusk.runsettings applies a 5-minute TestSessionTimeout so a regression that hangs the suite FAILS in bounded time instead of silently eating 20+ minutes. Keep it on every run that includes integration tests. (Per-test CancellationTokenSource timeouts are the first line of defense; this session cap is the backstop.)

Default (unit tests only — fast)

dotnet test --configuration Release --settings ShadowDusk.runsettings --filter "Category!=Integration" --logger "console;verbosity=normal"

With integration tests

dotnet test --configuration Release --settings ShadowDusk.runsettings --logger "console;verbosity=normal"

Specific platform target

dotnet test --configuration Release --settings ShadowDusk.runsettings --filter "Category=Integration&Platform=OpenGL"
dotnet test --configuration Release --settings ShadowDusk.runsettings --filter "Category=Integration&Platform=DirectX"
dotnet test --configuration Release --settings ShadowDusk.runsettings --filter "Category=Integration&Platform=Metal"

With coverage

dotnet test --configuration Release --settings ShadowDusk.runsettings --collect:"XPlat Code Coverage" --results-directory ./coverage

After running tests, report:

Total passed / failed / skipped
Any failed test names with their failure message and the file:line of the assertion
If integration tests were skipped due to missing native binaries, call that out explicitly
Any tests marked [Skip] with the reason

Common failures to diagnose:

FileNotFoundException for native binaries → run ./tools/restore.sh first
Flaky timing tests → look for missing CancellationToken or hardcoded Task.Delay
Platform-specific failures → check RuntimeInformation guards in the test

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.

1mo ago First seen · 43 lines · 0 tokens per session scan A 6bdb39b3fa3f

Subscribe to this mod's changes

test is a command published in the GitHub repository kaltinril/ShadowDusk (19 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 440 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-09-04.

Testing

prototype

You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.

grainulation/grainulator · 0 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

ShadowDusk: Command for Claude Code