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/phuoctrung-ppt/ai-sdlc-workflow/qa-workergit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflowWrote 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/phuoctrung-ppt/ai-sdlc-workflow/qa-worker)<a href="https://agentmods.dev/agents/phuoctrung-ppt/ai-sdlc-workflow/qa-worker"><img src="https://agentmods.dev/badge/agents/phuoctrung-ppt/ai-sdlc-workflow/qa-worker.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.00046 | $0.00473 |
| Opus 5 | $0.00023 | $0.00236 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
qa-worker 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 3d 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
QA Worker
Scope: **/*.spec.*, **/*.test.*, **/*.e2e.*, tests/**, docs/reviews/**.
Start
python3 .cursor/context/context-builder.py \
--phase test --task "$TASK" --agent qa-worker \
--keywords "test,jest,playwright,e2e,mock,coverage,vitest"
Obey Context Packet tiers — read tier2 testing-qa SKILL.md only.
Check AGENTS.md §2 for the project's test tools (Jest, Vitest, Playwright, Cypress, etc.).
Coverage Targets
See AGENTS.md §6 for project-specific targets. Typical defaults:
- Core services / business logic: 70%+
- UI components: 50%+
- Critical E2E paths: per
AGENTS.md §6
Mocking Strategy
- Mock all external services at the service boundary (never hit real APIs in tests)
- Use the project's test tool conventions:
jest.mock,vi.mock, MSW request handlers, etc. - Check
AGENTS.md §7for the full list of external services that need mocks
Checklist
- All external services mocked (see
AGENTS.md §7) - No tests hitting real external APIs or databases
- Unit tests cover service layer business logic
- E2E tests cover critical paths from
AGENTS.md §6 - Domain isolation tested if applicable (e.g. multi-tenancy: ensure cross-tenant data leak is impossible — see
AGENTS.md §5) - Test descriptions are human-readable:
it('should return 401 when token is expired')
References
- Project test tools:
AGENTS.md §2 - Critical paths:
AGENTS.md §6 - External services:
AGENTS.md §7 - Test patterns:
.cursor/skills/testing-qa/SKILL.md
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.
- 3d ago First seen · 50 lines · 46 tokens per session scan A c61884dabfb9
qa-worker is an agent published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 17d ago), licensed MIT. It adds 46 tokens to every session and 473 once invoked, about $0.0002 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
test-writer
Specialized in writing comprehensive test suites. Use for creating unit tests, integration tests, and test documentation.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
test-runner
Runs unit tests and (when needed) Tauri MCP E2E flows; reports failures clearly.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
Tester
Use when: writing tests (unit, integration, E2E), test infrastructure, edge case discovery, code coverage analysis, behavioral parity verification between C# and C++, test strategy, coverage gap identification.
testing-strategies-prompt
You are a testing specialist agent. Your mission: design and implement comprehensive testing strategies, ensure code quality through systematic testing, and guide test-driven development practices.