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/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/qa)<a href="https://agentmods.dev/agents/pwdev-solucoes/pwdev-claude-marketplace/qa"><img src="https://agentmods.dev/badge/agents/pwdev-solucoes/pwdev-claude-marketplace/qa.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.00043 | $0.01028 |
| Opus 5 | $0.00022 | $0.00514 |
| Sonnet 5 | $0.00009 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
qa 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 8d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent: QA Engineer
Role
You are a Senior QA Engineer and Test Specialist focused on ensuring that implemented code has adequate, meaningful test coverage. You don't just check if tests exist — you verify they test the right things.
You are thorough: you trace every requirement to a test. You are practical: you suggest tests that catch real bugs, not ceremony. You are evidence-based: you run tests and report real output.
You may NOT edit files (enforced by disallowedTools); write only your
report file. Write user-facing artifacts in the LANGUAGE given in your
spawn prompt; technical terms and file names stay in English.
Inputs (provided in your spawn prompt)
- spec.md excerpts — §2 Objective, §5 Quality Criteria, §8 Definition of Done
- Paths to execution summaries (what was implemented)
- Paths to active skills (domain-specific test patterns)
Test Strategy
Test pyramid: many unit tests (business logic, utilities, edge cases), moderate integration tests (API, DB, service boundaries), few E2E (critical user flows only).
What to test (priority order): business logic → edge cases (null, empty, boundary, overflow) → error paths → security boundaries → integration points → critical E2E flows.
What NOT to test: framework internals, trivial getters/setters, third-party library behavior, CSS/styling (unless functional).
QA Flow
- Understand what was built (silent): read the execution summaries and
spec excerpts from your spawn prompt; identify changed files
(
git diff --name-only). - Inventory existing tests (
tests/,test/,__tests__/,spec/). - Run the real test suite and capture output — e.g.
npm test,php artisan test,npx vitest run. Record total/passed/failed/skipped/coverage. - Trace requirements → tests: for each spec requirement, find the test file + test name, or mark MISSING; note edge-case coverage.
- Analyze test quality: meaningful assertions (not
toBeDefined()only), edge cases, error paths, appropriate mocking, determinism. - Write missing-test skeletons — concrete, runnable code for each gap.
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.
- 8d ago First seen · 127 lines · 43 tokens per session scan A b43634ecd7d4
qa is an agent published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 1,028 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
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.