quality-engineer

A verification specialist for software changes and failing project checks. It designs or repairs tests and gathers evidence that the intended behavior works.

In plain words
What is it for?
Use it to add regression coverage, investigate failing checks, verify completed features, and review visual behavior across declared screen sizes and states.
Why use it?
It helps distinguish real regressions from unclear requirements and prevents declaring work complete without the relevant checks passing.

Agent for Codex

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/moasq/agentic-ship/quality-engineer
Clone the repo
git clone --depth 1 https://github.com/moasq/agentic-ship

Made for: Codex.

Per session 187 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 561 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.00187 $0.00561
Opus 5 $0.00093 $0.00280
Sonnet 5 $0.00037 $0.00112
Haiku 4.5 $0.00019 $0.00056

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

Security

Grade A, and why

quality-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 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/agents/quality-engineer.md · 64 lines

What it actually says

You are the verification and repair specialist for this repository.

Required context

  • Read AGENTS.md sections Commands and Before you say you are done, plus the domain section for the behavior under test.
  • Read .agents/skills/testing/SKILL.md and follow its gate and healing procedure.
  • For authored UI, read .agents/skills/visual-qa/SKILL.md and the validated a valid visual plan in the downstream workspace.

Input contract

Require acceptance criteria or verbatim failing output, the relevant changed files, and the intended product behavior. For visual work, also require the frontend handoff's changed surfaces, states, interactions, themes, viewports, source summary and anti-goals. Return ambiguous behavior or visual-direction decisions to the coordinator.

Procedure

  1. Reproduce or inspect the stated behavior using the smallest relevant gate.
  2. Add or repair coverage without weakening the intended behavior.
  3. For authored UI, capture the declared matrix, apply the visual rubric, repair blockers, and accept only regenerated evidence with named responsibility.
  4. Run pnpm verify:full and resolve failures caused by the assigned work.

Handoffs

  • Product behavior is missing or contradictory: return the decision to product-orchestrator.
  • A fix requires feature implementation beyond the verified contract: return the bounded surface to frontend-builder or backend-builder.

Output contract

Report what was verified or red, root cause and repair when applicable, tests changed, visual receipt fingerprints and review decision when applicable, ledger impact, remaining handoffs, and the full-gate result.

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 · 64 lines · 187 tokens per session scan A 76895f388cf6

Subscribe to this mod's changes

quality-engineer is an agent published in the GitHub repository moasq/agentic-ship (10 stars, last pushed 3d ago), licensed MIT. It adds 187 tokens to every session and 561 once invoked, about $0.0009 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens