A QA approval review for the quality-related parts of the release checklist. QA, or quality assurance, checks whether software works correctly, remains reliable, and is usable.

Use it to review end-to-end and integration tests, regression testing, accessibility checks, exploratory testing, and critical-path coverage.

It makes quality approval explicit and ensures functional, accessibility, exploratory, and regression checks are considered.

gate-p6-qa — Command by jonase47

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 commands/jonase47/ccpr/gate-p6-qa

Clone the repo

git clone --depth 1 https://github.com/jonase47/ccpr

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

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00965
Opus 5	$0.00000	$0.00483
Sonnet 5	$0.00000	$0.00193
Haiku 4.5	$0.00000	$0.00097

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

Security

Grade A, and why

gate-p6-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 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.

commands/gate-p6-qa.md · 79 lines

How it starts

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

/gate-p6-qa – QA Approval Evaluation

Evaluates all QA-relevant points of the Gate-P6 checklist and grants QA approval.

Argument: $ARGUMENTS = not applicable

Gate commands accept no arguments.

Prerequisites

docs/quality/QA.md (phase index) exists
docs/quality/FUNCTIONAL.md (sub-index) and its detail files (func_e2e.md, func_integration.md, func_regression.md)
docs/quality/A11Y.md (sub-index) and its detail files (a11y_keyboard.md, a11y_screenreader.md, a11y_visual.md)
docs/quality/EXPLORATORY.md (direct detail file)
docs/architecture/TESTSTRATEGY.md exists (as reference for critical paths)

Agent

Type: qa-tester
Model: sonnet

Pre-Flight

If docs/.gate-preflight-p6.md exists and is less than 10 minutes old, read it as a starting point. Mechanical checks (file existence, sections) are already done – focus on content evaluation.

Context (Orchestrator prepares)

Read the phase and sub-indexes first, then load detail files only when their status row signals an open issue:

From docs/quality/QA.md: status, key decisions, open risks (the entry points)
From docs/quality/FUNCTIONAL.md (sub-index): row status of each func_*.md
From docs/quality/A11Y.md (sub-index): row status of each a11y_*.md
From docs/quality/EXPLORATORY.md: severity summary
From docs/architecture/TESTSTRATEGY.md: critical test paths (short list)
Detail files (func_e2e.md, a11y_visual.md, ...) only when a sub-index row is needs-rework or has an open Critical risk

Prompt Template

Goal: QA approval evaluation for Gate P6.

Test Protocols: [inline summaries]

Output Format:

Checklist (max. 8 points): | # | Check Point | Status | Justification | Status: Met / Partial / Not Met

QA Approval:

Approved / Conditional Approval / Not Approved

Justification (2–3 sentences)

Conditions (if conditional, as numbered list)

Constraints:

QA evaluation ONLY, NO security evaluation

Evaluation based exclusively on available protocols

No approval if critical bugs are open

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

2d ago First seen · 79 lines · 0 tokens per session scan A 663f14312a43

Subscribe to this mod's changes

gate-p6-qa is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 965 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.

Testing agentic-workflows ai-agents anthropic claude claude-code claude-code-agents

gate-p6-qa

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/gate-p6-qa – QA Approval Evaluation

Argument: $ARGUMENTS = not applicable

Prerequisites

Agent

Pre-Flight

Context (Orchestrator prepares)

Prompt Template

What this file has done since we first saw it

Other commands, from other repositories

research

status

help

clean-check

build

firebase-publish