A quality-assurance workflow that checks work in three stages: define the expected result, verify each small step, and run a final review. Quality assurance means checking that software meets its agreed requirements.

Use it to create acceptance criteria, record step-by-step verification, run the final quality check, and maintain a report of the results.

It creates written evidence for what should work and whether each stage passed, making missed checks easier to spot.

qa-cycle — Skill for Claude Code and Codex by humanerd-drew

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.

Any agent

npx skills add humanerd-drew/opencode-drewgent --skill qa-cycle

Clone the repo

git clone --depth 1 https://github.com/humanerd-drew/opencode-drewgent

Made for: Claude Code, Codex.

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/skills/humanerd-drew/opencode-drewgent/qa-cycle/github.svg)](https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/qa-cycle)

Your own site

<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/qa-cycle"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/qa-cycle/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/skills/humanerd-drew/opencode-drewgent/qa-cycle"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/qa-cycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 766 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.00034	$0.00766
Opus 5.5	$0.00014	$0.00306
Sonnet 5.5	$0.00007	$0.00153
Haiku 4.5	$0.00003	$0.00077

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

Security

Grade A, and why

qa-cycle 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 1mo 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.

@action/skills/qa/qa-cycle/SKILL.md · 102 lines

How it starts

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

qa-cycle — Contract-First QA Pipeline

Purpose

Runs 3-phase QA pipeline for any task:

CONTRACT — Define acceptance criteria before implementation
MICRO-QA — Verify each step as it's completed
FULL-QA — Final gate check before delivery

How It Works

Uses the QAEvidenceManager in P2-hippocampus/qa-evidence/ to:

Create a contract.json with acceptance criteria
Record micro-qa_*.json after each step
Run full-qa.json before delivery
Generate .qa-evidence.json manifest

Usage

skill: qa-cycle
task_id: {optional, auto-generated if omitted}
action: create_contract | record_micro | run_full_qa | status

Workflow

1. Create Contract (Before Implementation)

qa = QAEvidenceManager()
qa.create_contract(
    task_id="my-task-001",
    acceptance_criteria=[
        {"id": "c1", "description": "Feature X works", "priority": "P0"},
        {"id": "c2", "description": "Tests pass", "priority": "P0"},
    ]
)

2. Record Micro-QA (After Each Step)

qa.record_micro_qa(
    task_id="my-task-001",
    step_id="step_1",
    step_description="Implemented feature X",
    evidence={"files": ["feature_x.py"]},
    verification={"passed": True, "score": 1.0}
)

3. Run Full-QA (Before Delivery)

result = qa.run_full_qa(
    task_id="my-task-001",
    criteria_verification=[...],
    overall_score=0.95
)
if not result["ready_for_delivery"]:
    # revision loop

Hugh Kim's Contract-First QA Principle

From the Loopy-Era Harness:

Phase 2.5 시나리오 확정 → 구현 → micro-QA → full-QA
.qa-evidence.json 증거 필수
FILESYSTEM = TRUTH: 파일에서 직접 읽어 Specialist에게 전달

Integration

P2-hippocampus/qa-evidence/ — Evidence storage
P4-cortex/growth/orchestrator/ — Orchestrator calls qa-cycle
HARD hook: task_qa_gate — Blocks delivery without QA

Verification Checklist

Before marking QA complete, verify:

All acceptance criteria have test results
No blocker-level issues remain
Filesystem = Truth: re-read files to confirm changes
Evidence manifest is complete

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

1mo ago First seen · 102 lines · 34 tokens per session scan A f622fa022f6e

Subscribe to this mod's changes

qa-cycle is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (3 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 766 once invoked, about $0.0001 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-08-31.

Testing contract-first qa verification

mk:qa

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a…

ngocsangyem/MeowKit · 127 tokens

pm-verification-protocols

QA verification gate and evidence requirements.

bobmatnyc/claude-mpm · 13 tokens

wp-qa-testing

Use when WordPress software needs procedural testing framework and verification approach. Produces test strategy, test plans, test procedures, and test case specifications for developers and QA teams. Aligns to ISO/IEC/IEEE 29119-2:2021 (Test Process) with ISO/IEC TR 29119-6:2021 (Agile Tailoring). Use during…

hectorjarquin/wp-agent-skills · 86 tokens

qa-cycle