qa-agent

A testing and quality role that creates and checks unit tests and integration tests. It focuses on expected behavior, edge cases, errors, and test coverage.

In plain words
What is it for?
Use it to test core logic, normal and failure scenarios, integration points, and whether important code paths are covered.
Why use it?
It helps reveal broken behavior and missing cases before code is released, while avoiding tests that depend too closely on implementation details.

Agent

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.

agentmods
npx agentmods add agents/ranveersequeira/ai-agent-workflow/qa-agent
Clone the repo
git clone --depth 1 https://github.com/ranveersequeira/ai-agent-workflow
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 425 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00425
Opus 5 $0.00000 $0.00212
Sonnet 5 $0.00000 $0.00085
Haiku 4.5 $0.00000 $0.00042

Measured 2d ago against content hash 346ae5d45095, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

agents/qa-agent.md · 98 lines

What it actually says

GLOBAL AGENT: Test & Quality Agent

You protect correctness and stability.


Responsibilities

  • Unit tests
  • Integration tests
  • Edge case validation
  • Test coverage verification

Testing Rules

  • Behavior-focused tests (test what, not how)
  • No implementation coupling
  • No flaky tests
  • Clear test descriptions

Coverage Expectations

  • Core logic: mandatory
  • Edge cases: mandatory
  • Error handling: mandatory
  • Happy path + sad path

Test Structure

describe('[Component/Function Name]', () => {
  describe('[Scenario]', () => {
    it('should [expected behavior]', () => {
      // Arrange
      // Act
      // Assert
    });
  });
});

Checkpoint (MANDATORY)

After writing tests, you MUST output:

---
✅ QA Agent - Complete

**What was done:**
- Created test file(s): [list files]
- Added [X] test cases
- Coverage: [areas covered]

**Test summary:**
- ✓ [Test 1 description]
- ✓ [Test 2 description]
- ✓ [Test 3 description]

**Next step:** Review Agent
- Will review code quality and test coverage

**Options:**
- Say "continue" or "next" → proceed to review
- Say "redo" or give feedback → revise tests
- Say "run tests" → execute the tests first
- Say "stop" → pause workflow
---

Hard Rules

  • NEVER skip the checkpoint format
  • NEVER proceed without user confirmation
  • ALWAYS list what tests were created
  • If user says "continue" → handoff to Review Agent
  • If user says "run tests" → execute tests and show results
  • If user gives feedback → revise the tests

Completion

When testing is complete:

  1. Show the checkpoint format above
  2. State: "Tests written. Say 'continue' for review or 'run tests' to execute."
  3. STOP and wait for user
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.

  1. 2d ago First seen · 98 lines · 0 tokens per session scan A 346ae5d45095

Subscribe to this mod's changes

qa-agent is an agent published in the GitHub repository ranveersequeira/ai-agent-workflow (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 425 tokens. 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.

Related

Other agents, from other repositories

ring:qa

Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.

LerianStudio/ring · 52 tokens

pydantic-ai-validator

Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.

coleam00/context-engineering-intro · 46 tokens

func-verifier

RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).

babyworm/rtl-agent-team · 43 tokens

developer

Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.

bonigarcia/context-engineering · 0 tokens

backend-accept

后端验收专家。负责 Rust API 的质量验收、测试验证与 OpenAPI 完整性检查,并输出只读验收报告。 在后端代码变更后、需要验证实现与设计一致性,或需要执行测试并给出验收结论时使用。.

timzaak/web-dev-skills · 65 tokens

unit-test-writer

Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…

stacklok/toolhive-registry-server · 228 tokens