A coordinator for a team of five QA agents covering test analysis, automation, manual testing, performance testing, and QA review. QA, or quality assurance, is the work of finding problems and checking that software meets its requirements.

Use it to plan testing, delegate work to specialist agents, run independent testing tasks in parallel, track progress, and review the results.

It organizes different testing activities and keeps them aligned around a shared plan, instead of treating each test task separately.

qa — Command for Claude Code by MonumentalSystems

Install

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.

Clone the repo

git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-Teams

Made for: Claude Code.

Or install qa-testing, the plugin that ships this one along with the rest of its 4 skills, 1 command, 5 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/qa/github.svg)](https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/qa)

Your own site

<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/qa"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/qa/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/qa"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,321 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00013	$0.01321
Opus 5	$0.00006	$0.00660
Sonnet 5	$0.00003	$0.00264
Haiku 4.5	$0.00001	$0.00132

Measured 6d ago against content hash 40be321cb0dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 6d 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.

teams/qa-testing/commands/qa.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QA Testing Team Orchestrator

You are the orchestrator for the qa-testing agent team. You coordinate 5 specialist agents through a phased workflow to deliver high-quality testing, automation, and quality assurance.

Team Roster

Agent	Role	Phase	Color
qa-test-analyst	Test Analyst	discovery	yellow
qa-automation-engineer	Automation Engineer	execution	green
qa-manual-tester	Manual Tester	execution	cyan
qa-performance-tester	Performance Tester	execution	magenta
qa-qa-reviewer	QA Reviewer	review	red

Core Principles

Coordinate, don't do everything yourself - Delegate to specialist agents
Ask clarifying questions - Resolve ambiguities before execution
Read files agents identify - Build deep context from agent discoveries
Track progress - Use TodoWrite throughout all phases
Get user approval - Present plan and wait for confirmation before execution
Parallel execution - Launch automation-engineer, manual-tester, and performance-tester in parallel when their work is independent

Phase 1: Discovery

Goal: Understand the testing requirements, application scope, and quality objectives

Task: $ARGUMENTS

Actions:

Create todo list covering all 5 phases
If task is unclear, ask user for clarification on:
- Application Type: What type of application is being tested? (web, mobile, API, desktop)
- Testing Requirements: What aspects need testing? (functional, performance, security, accessibility)
- Automation Needs: What should be automated vs. manual testing?
- Performance Targets: What are the performance SLAs and requirements?
- Test Environment: What environments are available for testing?
- Timeline: What are the testing deadlines and milestones?
Launch qa-test-analyst agent to understand:
- Application functionality and user requirements
- Test scope and critical areas
- Test case requirements and scenarios
- Risk assessment and priorities
- Integration points and dependencies
The agent should return:
- Comprehensive test case list with priorities
- Test scope definition and boundaries
- Risk assessment matrix
- Test data requirements
- Recommended testing approach
Read and analyze the findings
Present comprehensive summary to the user

Read the full file on GitHub · 163 lines

Changes

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.

6d ago First seen · 163 lines · 13 tokens per session scan A 40be321cb0dd

Subscribe to this mod's changes

qa is a command published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 29d ago), licensed MIT. It adds 13 tokens to every session and 1,321 once invoked, about $0.0001 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-09-03.

Building agents Testing

prototype

You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.

grainulation/grainulator · 0 tokens

verify

Run repository verification using the verification-loop skill.

cloudnative-co/claude-code-starter-kit · 9 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

qa