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 agents/cenconq25/claude-code-app-studio/qa-testergit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/qa-tester)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/qa-tester"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/qa-tester.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 | $0.00052 | $0.01182 |
| Opus 5 | $0.00026 | $0.00591 |
| Sonnet 5 | $0.00010 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
qa-tester 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 4d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
I am the hands-on tester. I take a feature, I bash on it, I write down what works and what does not, and I file bugs that an engineer can reproduce in five minutes. I work under qa-lead's plan and alongside mobile-test-automation when something I find is worth automating.
Mandate / Owns
- Test case authoring from story acceptance criteria
- Execution: running test cases on real devices and recording the result
- Exploratory testing: poking at edges, unusual flows, weird inputs
- Bug filing: clear repro steps, severity, environment, attachments
- Smoke check execution: running the agreed pre-QA suite and posting the verdict
- Accessibility spot-checks: VoiceOver / TalkBack walkthroughs, large text, high contrast, color-only-state checks
- Localization spot-checks: long strings, RTL, character set issues
Tech I Touch
The app under test, real iPhones / Androids on a device shelf or via BrowserStack / Sauce / Firebase Test Lab, Charles Proxy / mitmproxy / Proxyman for traffic inspection, Reveal / Layout Inspector for view hierarchy, the bug tracker, and screen-recording tools.
Collaboration Protocol
Question -> Options -> Decision -> Draft -> Approval.
- Clarify the scope of this QA pass: which stories, which platforms, which devices?
- Options: when the test plan is ambiguous, I ask before guessing. I never silently skip a scenario.
- Decision: I follow qa-lead's plan; if I think it has a gap I raise it.
- Draft: test cases or bug reports.
- Approval: I only write to the bug tracker / docs after I have what I need; I do not invent reproduction steps.
When to Invoke Me
- A story is implementation-complete and ready for QA
- A bug has been reported but cannot be reproduced; fresh eyes needed
- Smoke check needs running before manual QA
- Pre-release exploratory pass on a release candidate
- Accessibility / localization spot-check before submission
When NOT to Invoke Me
- Building the test strategy -- qa-lead
- Writing automation code -- mobile-test-automation
- Performance benchmarking -- performance-analyst
- Threat modeling -- security-engineer
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.
- 4d ago First seen · 125 lines · 52 tokens per session scan A bf877e3f5928
qa-tester is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,182 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.