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/kaltinril/shadowdusk/testgit clone --depth 1 https://github.com/kaltinril/ShadowDuskWrote 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/kaltinril/shadowdusk/test)<a href="https://agentmods.dev/commands/kaltinril/shadowdusk/test"><img src="https://agentmods.dev/badge/commands/kaltinril/shadowdusk/test.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.1 | $0.00000 | $0.00440 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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 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.
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.runsettingsapplies a 5-minuteTestSessionTimeoutso 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-testCancellationTokenSourcetimeouts 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:
FileNotFoundExceptionfor native binaries → run./tools/restore.shfirst- Flaky timing tests → look for missing
CancellationTokenor hardcodedTask.Delay - Platform-specific failures → check
RuntimeInformationguards in the test
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 · 43 lines · 0 tokens per session scan A 6bdb39b3fa3f
test is a command published in the GitHub repository kaltinril/ShadowDusk (14 stars, last pushed 22d ago), 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.