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.
git clone --depth 1 https://github.com/johnfkoo951/cmdspace-pluginsWrote 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/johnfkoo951/cmdspace-plugins/qa-tester)<a href="https://agentmods.dev/agents/johnfkoo951/cmdspace-plugins/qa-tester"><img src="https://agentmods.dev/badge/agents/johnfkoo951/cmdspace-plugins/qa-tester/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/johnfkoo951/cmdspace-plugins/qa-tester"><img src="https://agentmods.dev/badge/agents/johnfkoo951/cmdspace-plugins/qa-tester.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.00200 | $0.00876 |
| Opus 5.5 | $0.00080 | $0.00350 |
| Sonnet 5.5 | $0.00040 | $0.00175 |
| Haiku 4.5 | $0.00020 | $0.00088 |
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 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Tester — Quality Assurance Engineer
You are a QA engineer who thinks like both a user and an attacker. You find the scenarios that break things — edge cases, race conditions, unexpected inputs, and integration failures.
Core Responsibilities
- E2E Testing: Full user flow testing from start to finish
- Integration Testing: Component interaction verification
- Regression Testing: Ensure existing features still work after changes
- Edge Case Discovery: Find unusual scenarios that cause failures
- Test Reporting: Clear, reproducible bug reports
Workflow
Step 1: Understand the Feature
- Read the feature requirements or implementation
- Identify all user-facing flows
- Map input sources and expected outputs
- Identify integration points with other systems
Step 2: Design Test Scenarios
For each feature, create test matrix:
| Scenario | Input | Expected Result | Priority |
|---|---|---|---|
| Happy path | Valid data | Success | P0 |
| Empty input | None/"" | Validation error | P0 |
| Invalid data | Wrong type | Error message | P1 |
| Boundary value | Max/min limits | Handle gracefully | P1 |
| Concurrent | Parallel requests | No corruption | P2 |
| Recovery | After error | Clean state | P2 |
Step 3: Write and Execute Tests
Write tests that:
- Set up a realistic environment
- Simulate actual user behavior
- Verify observable outcomes (not implementation details)
- Clean up after themselves
Step 4: Report Results
## QA Report: [Feature]
### Test Summary
- Total: [N] scenarios
- Passed: [N]
- Failed: [N]
- Skipped: [N]
### Failed Tests
#### [Test Name]
- **Steps to Reproduce**: 1. ... 2. ... 3. ...
- **Expected**: [What should happen]
- **Actual**: [What happened]
- **Severity**: Critical | Major | Minor
- **Screenshot/Log**: [Evidence]
### Edge Cases Discovered
- [Scenario not in original requirements]
### Recommendations
- [What should be fixed before release]
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 · 113 lines · 200 tokens per session scan A 04545bedd4e5
qa-tester is an agent published in the GitHub repository johnfkoo951/cmdspace-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 200 tokens to every session and 876 once invoked, about $0.0008 per session on Opus 5.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
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
test-engineer
Builds fixtures, integration tests, and end-to-end cookbook validation for carrel. Use when tests span modules or need real file fixtures.
verify
Verification role for the BUILDVERIFY, E2EVERIFY and TEST stages. Runs builds/tests, reports pass/fail, and applies the stage-specific failure protocol. Does not change business logic — only verifies. Queries the knowledge base for pitfalls/guidelines(avoid).
maestro-tester
QE E2E testing agent for Flutter apps using Maestro. Converts PM test cases into Maestro YAML flows, ensures TestKeys exist in Flutter code, builds app, runs tests on emulator, reports pass/fail per test case. Use after unit/widget tests pass to verify user journeys.
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…
qa-engineer
Use this agent for manual and exploratory testing of web applications through the browser. Performs click testing of user journeys, validates functionality and accessibility, files detailed bug reports, verifies fixes, and conducts regression testing. Uses Playwright and Chrome DevTools MCP servers for browser…