Borrowing it
Nothing to install: this file belongs to kamiazya/whiteboard. 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/kamiazya/whiteboard/main/.claude/agents/qa-scenario.mdgit clone --depth 1 https://github.com/kamiazya/whiteboardWrote 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/kamiazya/whiteboard/qa-scenario)<a href="https://agentmods.dev/agents/kamiazya/whiteboard/qa-scenario"><img src="https://agentmods.dev/badge/agents/kamiazya/whiteboard/qa-scenario.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.00058 | $0.00430 |
| Opus 5 | $0.00029 | $0.00215 |
| Sonnet 5 | $0.00012 | $0.00086 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
qa-scenario 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 6d 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.
What it actually 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 buildfirst, then verify daemon starts (WHITEBOARD_DEV=1for 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:*orpnpm test --project mcp-*). 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 buildwas run before testing daemon-spawning paths (stale dist causes confusing errors).
Output format
Scenario: <name>
Result: PASS / FAIL / BLOCKED
Evidence: <exact command output or file content excerpt>
Issues found:
- <description> (add to tmp/issues/ if significant)
If BLOCKED, explain what prerequisite is missing (e.g., loopback bind not available in sandbox, pnpm build required first).
Test only the assigned scenario. Be direct about PASS/FAIL — do not hedge.
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.
- 6d ago First seen · 35 lines · 58 tokens per session scan A 038d21b976c4
qa-scenario is an agent published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 430 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
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…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.