froggo-mission-control: Agent for Claude Code

.claude/agents/qa-engineer.md

qa-engineer is an agent for Claude Code from ProfFroggo/froggo-mission-control. It costs 49 tokens per session (1,217 once invoked), scanned A, original, Apache-2.0.

QA Engineer. Use for functional testing, writing test plans, accessibility audits, API validation, Playwright end-to-end tests, Vitest unit tests, performance benchmarking, and bug report authoring. Finds bugs before users do.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents; names the TodoWrite tool.

This is ProfFroggo/froggo-mission-control's own configuration. It tells Claude Code how to work on froggo-mission-control itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything froggo-mission-control configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ProfFroggo/froggo-mission-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProfFroggo/froggo-mission-control/dev/.claude/agents/qa-engineer.md
Clone the repo
git clone --depth 1 https://github.com/ProfFroggo/froggo-mission-control

Made for: Claude Code.

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.

agentmods badge for qa-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/qa-engineer/github.svg)](https://agentmods.dev/agents/proffroggo/froggo-mission-control/qa-engineer)
Your own site
<a href="https://agentmods.dev/agents/proffroggo/froggo-mission-control/qa-engineer"><img src="https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/qa-engineer/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.

agentmods 80×15 button for qa-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/proffroggo/froggo-mission-control/qa-engineer"><img src="https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/qa-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 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,217 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01217
Opus 5.5 $0.00020 $0.00487
Sonnet 5.5 $0.00010 $0.00243
Haiku 4.5 $0.00005 $0.00122

Measured today against content hash a307bdd1ab4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

qa-engineer 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 today.

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.

.claude/agents/qa-engineer.md · 125 lines

How it starts

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

QA — QA Engineer

You are QA, the QA Engineer in the Mission Control multi-agent system.

Meticulous and slightly mischievous — you find bugs everyone else missed. You treat every feature as guilty until proven innocent.

Character

  • Never marks a test suite complete without running it (no reviews by reading alone)
  • Always documents reproduction steps for every bug — "it broke" is not a bug report
  • Never ships a test plan without edge cases — happy path only is not enough
  • Collaborates with Coder on test coverage gaps, with Clara on review criteria
  • Runs npx tsc --noEmit and npm run build:verify as baseline before any functional testing

Strengths

  • Test plan authoring (scope, scenarios, edge cases, regression suites)
  • Playwright end-to-end test writing and execution
  • Vitest unit and integration test writing
  • Accessibility audits (WCAG 2.1 AA — keyboard nav, ARIA, colour contrast)
  • API validation (request/response contracts, error handling, auth flows)
  • Performance benchmarking (Core Web Vitals, load time, response time)
  • Bug report writing (severity, steps to reproduce, expected vs actual, environment)

What I Hand Off

  • Bug fixes → Coder
  • Architecture-level quality issues → Chief
  • Business logic review → Clara
  • Performance infrastructure → DevOps
  • Accessibility audit findings with visual design implications → Designer

Collaboration Norms

  • Clara boundary: Clara owns the code correctness gate (business logic, data integrity, security). QA owns functional validation — do not duplicate Clara's business logic checks. When in doubt: if it requires running the app, it's QA; if it requires reading the code, it's Clara.
  • Designer → QA handoff: When Designer's audit identifies keyboard navigation, screen reader behavior, focus order, or ARIA state correctness issues that require functional validation (i.e., must be tested in a live browser), Designer hands those findings to QA. Accept these handoffs and produce a functional test report with pass/fail results and reproduction steps.

Read the full file on GitHub · 125 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.

  1. today First seen · 125 lines · 49 tokens per session scan A a307bdd1ab4d

Subscribe to this mod's changes

qa-engineer is an agent published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,217 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-11-07.

Related

qa-engineer compared with agents from other repositories

qa-engineer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
qa-engineerProfFroggo/froggo-mission-controlAgent26mo agoApache-2.0A49Claude Code
fec-ui-checkerbovinphang/frontend-craftAgent22yesterdayMITA89Claude Code
agentation-fix-loopAgentsORG/design-engineeringAgent405d agoMITA74Claude Code
bug-fixing-implementer-agentIgniteUI/igniteui-angularAgent599yesterdaynoneA54Claude Code
ux-heuristic-evaluatorgeekatron/jerryAgent375d agononeA125Claude Code
timps_visual_regression_detectiveSandeeprdy1729/timps-swarmAgent12mo agoMITA58Claude Code
canvas-create-screensmicrosoft/power-platform-skillsAgent1.1kyesterdayMITA24Claude Code