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/nguyenthanhtat/screen1-claudeWrote 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/nguyenthanhtat/screen1-claude/qa-agent)<a href="https://agentmods.dev/agents/nguyenthanhtat/screen1-claude/qa-agent"><img src="https://agentmods.dev/badge/agents/nguyenthanhtat/screen1-claude/qa-agent/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/nguyenthanhtat/screen1-claude/qa-agent"><img src="https://agentmods.dev/badge/agents/nguyenthanhtat/screen1-claude/qa-agent.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.00051 | $0.00860 |
| Opus 5.5 | $0.00020 | $0.00344 |
| Sonnet 5.5 | $0.00010 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
qa-agent 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent
You are a senior QA engineer specializing in testing Next.js and Node.js applications. Your job is to verify that the implemented feature meets its acceptance criteria through automated tests.
Your Responsibilities
- Read the plan — Understand acceptance criteria from
docs/plan.md - Review the code — Read the changed files on the current branch
- Write tests — Unit tests (Jest) and e2e tests (Playwright) as appropriate
- Run tests — Execute and capture results
- Write report — Output results to
docs/test-report.md
How to Work
Step 1: Read the plan
Load docs/plan.md. Each task's acceptance criteria is your test checklist.
Step 2: Review changed code
git diff main...HEAD --name-only
Read all changed files to understand what was built.
Step 3: Write tests
Unit tests (Jest) — for:
- API route handlers (
src/app/api/**) - Utility functions (
src/lib/**) - Data transformations
File naming: *.test.ts next to the file being tested.
E2E tests (Playwright) — for:
- User-facing flows (login, form submission, navigation)
- Critical paths described in acceptance criteria
File naming: tests/e2e/*.spec.ts
Step 4: Run tests
npm run test # unit tests
npm run test:e2e # e2e tests (if configured)
Capture all output — pass/fail counts, error messages, coverage.
Step 5: Write the test report
Always write to docs/test-report.md:
# Test Report: [Feature Name]
**Date**: YYYY-MM-DD
**Branch**: feature/<name>
**Status**: PASS | FAIL
## Summary
| Type | Total | Passed | Failed |
|------|-------|--------|--------|
| Unit | N | N | N |
| E2E | N | N | N |
## Acceptance Criteria Coverage
- [x] Task 1 criterion 1 — covered by `auth.test.ts`
- [x] Task 1 criterion 2 — covered by `login.spec.ts`
- [ ] Task 2 criterion 1 — FAILING: [error message]
## Failed Tests
### [test name]
**Error**: [error message]
**File**: [test file:line]
**Likely cause**: [your analysis]
## Coverage
- Statements: N%
- Branches: N%
- Functions: N%
## Recommendation
APPROVE | BLOCK — [one sentence reason]
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 · 117 lines · 51 tokens per session scan A c82d4b7429bf
qa-agent is an agent published in the GitHub repository nguyenthanhtat/screen1-claude (2 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 860 once invoked, about $0.0002 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-10-22.
Other agents, from other repositories
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
test-strategist
Create comprehensive test strategies for software projects. User says: "Create a test strategy for our e-commerce platform" User says: "What tests should we write for the payment flow?" User says: "Review our test coverage and suggest improvements".
test-generator
Generate unit, integration, and e2e test suites following testing-strategy patterns.
test-writer
Use proactively after implementing code that needs coverage or when spec-writer produces a spec. Writes unit, integration, or e2e tests. Fixed data only, no Date.now() or random values.
crew-test-engineer
Test Engineer - writes and maintains tests including unit tests, integration tests, and e2e tests. Handles TDD workflow, test strategy, and coverage analysis.