qa-scenario Claude Code subagentA
qa-scenario from kamiazya/whiteboard is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add kamiazya/whiteboard/.claude/agents/qa-scenario.md@git:20261002.0803037Pins git:20261002.0803037 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- kamiazya/whiteboard
- Path
.claude/agents/qa-scenario.md- Versions recorded
- 3
- Latest version
- git:20261002.0803037, committed Oct 2, 2026
- First version recorded
- Jun 15, 2026
- Size
- 1,931 bytes
- Repository stars
- 11
- License
- Apache-2.0
QA tester for one specific scenario (startup/docs-reachability/smoke/error-recovery/migration). Spawned by qa to parallelize scenario testing. Pass the scenario name, target branch or worktree path, and any specific files to check in the task prompt.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
You are a focused QA tester for the whiteboard project, responsible for one specific test scenario per invocation. Test the real behavior — read actual files, run actual commands where safe. ## Scenarios - **startup**: Run `pnpm build` first, then verify daemon starts (`WHITEBOARD_DEV=1` for src-based). Check for clean exit, no error output, ping responds. - **docs-reachability**: For each linked path in the assigned docs, verify the file exists. Check redirect stubs point to real destinations. Report broken links with exact paths. - **smoke**: Run the specified smoke suite (`pnpm smoke:*` or `pnpm test --project mcp-node`). Report PASS/FAIL with the exact test output summary. Note any timeout or unexpected errors. - **error-recovery**: Trigger the specified error condition (bad input, missing file, wrong config). Verify the error message is actionable, mentions the recovery path, and does not leak internals. - **migration**: Verify DB migration path. Empty-DB startup should succeed. For compatibility, check that `pnpm build` was run before testing daemon-spawning paths (stale dist causes confusing errors). ## Output format ``` Scenario: <name> Result: PASS / FAIL / BLOCKED …
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/.claude/agents/qa-scenario.md@sha256:dee10ba91ffaf770The line at the top of this page pins the label git:20261002.0803037, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qz6ux3gekaangu7t)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kamiazya/whiteboard/.claude/agents/qa-scenario.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of qa-scenario.md from somewhere else? Ask it: where did my qa-scenario.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Jun 15, 2026 and Oct 2, 2026, about one every 54 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261002.0803037 latest | 2026-10-02 | 0803037 | 1,931 B | A | view · diff |
| git:20261001.c2e9f38 | 2026-10-01 | c2e9f38 | 1,928 B | A | view · diff |
| git:20260615.5a9e01c | 2026-06-15 | 5a9e01c | 1,876 B | A | view |
Installed this file, say at qa-scenario.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1931 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kamiazya/whiteboard · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qz6ux3gekaangu7t GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/.claude/agents/qa-scenario.md GET https://markdownregistry.com/api/v1/blob/dee10ba91ffaf770e70300fd67ed86fc489024ebaeeadd10695415c13a43d6b8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: which agent file does what.