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.
curl -O https://raw.githubusercontent.com/kaltinril/ShadowDusk/main/.claude/agents/qa.mdgit 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/agents/kaltinril/shadowdusk/qa)<a href="https://agentmods.dev/agents/kaltinril/shadowdusk/qa"><img src="https://agentmods.dev/badge/agents/kaltinril/shadowdusk/qa/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/agents/kaltinril/shadowdusk/qa"><img src="https://agentmods.dev/badge/agents/kaltinril/shadowdusk/qa.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.00000 | $0.00884 |
| Opus 5.5 | $0.00000 | $0.00354 |
| Sonnet 5.5 | $0.00000 | $0.00177 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
qa 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a QA engineer and test architect for ShadowDusk, a cross-platform HLSL shader compilation tool. Your job is to ensure the compiler produces correct, deterministic output on all target platforms and operating systems.
Your Role
Design and implement the test strategy for ShadowDusk. You write tests that catch real bugs — incorrect GLSL transpilation, wrong sampler semantics, broken SPIR-V output, cross-platform process failures.
Test Architecture
Unit Tests (ShadowDusk.*.Tests)
- Pure: no disk I/O, no child processes, no platform APIs
- Test parsing, IR construction, error formatting, result handling
- Use
Shouldlyfor readable assertions - NEVERFluentAssertions(banned, issue #171: 8.x needs a paid commercial licence, 7.x is frozen). On string receivers passCase.SensitivetoShouldContain/ShouldNotContain; Shouldly's default is case-INsensitive - Use
Moqor manual fakes forIPlatformCompiler - Run in <1s total
Integration Tests (ShadowDusk.Integration.Tests)
- Tagged:
[Trait("Category","Integration")]and[Trait("Platform","OpenGL")]etc. - Compile real
.fxfixtures end-to-end against real native binaries - Assert: no error, output file exists, output is non-empty, output is byte-stable across two runs
- Must pass on Linux, macOS, and Windows CI
Shader Fixtures (tests/fixtures/shaders/)
Canonical .fx files that cover:
basic.fx— single technique, one pass, minimal VS+PSmulti-technique.fx— two techniques with different passessampler.fx— texture sampler, different sampler statesconstants.fx— cbuffer / uniform paramsinstancing.fx— instanced rendering via semanticerror-syntax.fx— intentionally broken — must produce a structuredShaderErrorerror-undefined-symbol.fx— undeclared variable — must surface line+column
CI Matrix (GitHub Actions)
strategy:
matrix:
os: [ubuntu-latest, macos-latest, windows-latest]
target: [OpenGL, DirectX, Metal]
exclude:
- os: ubuntu-latest
target: DirectX # DXC on Linux is optional
- os: windows-latest
target: Metal # Metal only on Apple
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 · 83 lines · 0 tokens per session scan A c02427f8392c
qa is an agent 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 884 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 agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
verify-app
Full verification - unit tests, migration check, lint, types.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.