What is quality-engineering-quality-assurance?

A set of rules for writing and reviewing manual software test cases in Zephyr, a test-management tool. Each test case covers one condition on one screen.

Use it to split test coverage, name cases for web or mobile when needed, and assign High, Normal, or Low priority with a reason.

It prevents broad or mixed test cases that are difficult to understand, run, or trace back to a specific behavior.

quality-engineering-quality-assurance — Skill for Claude Code and Code

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 HoangNguyen0403/agent-skills-standard --skill quality-engineering-quality-assurance

Clone the repo

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

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/hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance)

Your own site

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance/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/hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 593 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00069	$0.00593
Opus 5	$0.00034	$0.00296
Sonnet 5	$0.00014	$0.00119
Haiku 4.5	$0.00007	$0.00059

Measured 13d ago against content hash a0e544a5cf83, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

quality-engineering-quality-assurance 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 13d 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/skills/quality-engineering/quality-engineering-quality-assurance/SKILL.md · 65 lines

How it starts

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

Quality Assurance Standards

Priority: P1 (HIGH)

1. Test Case Granularity

1 Test Case = 1 Condition on 1 Screen.
Split Screens: "Order Details" & "Item Details" separate.
Split Conditions: "Config " & "Config B" separate.
No "OR" Logic: Each TC must test single, distinct path.

2. Naming Convention

Pattern: Platform_Module_Action on Screen when Condition (e.g., Web_Order_Verify... or Mobile_Order_Verify...)
Rule: Only include Web_ or Mobile_ prefix if requirement exclusive to one platform. Omit prefix if it supports Both.
Example: Order_Verify payment term on Item Details when Toggle is OFF (Supports Both)

3. Priority Levels

Use priority rationale to justify each classification:

High: Critical path, blocker bug.
Normal: Standard validation, edge case.
Low: Cosmetic, minor improvement.

4. References

Detailed Examples

Anti-Patterns

No Broad TCs: "Verify order flow works" — too broad; every TC must cover exactly 1 condition on 1 screen
No Shared TCs (Divergent): Testing Web and Mobile behavior in single TC when behavior diverges — split into separate TCs per platform
No Incomplete Naming: Order_Verify page — name must follow full pattern: Module_Action on Screen when Condition
No Priority Inflation: Marking cosmetic spacing bug as High priority — reserve High for critical path blockers only

Review wording

Call out naming violations explicitly when a test case breaks the naming convention, then split it into separate TCs with one condition on one screen.

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

naming violations
1 Test Case = 1 Condition
High: Critical path
Low: Cosmetic
Module_Action on Screen when Condition
No "OR" Logic
Split into separate TCs
priority rationale

Read the full file on GitHub · 65 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

13d ago First seen · 65 lines · 69 tokens per session scan A a0e544a5cf83

Subscribe to this mod's changes

quality-engineering-quality-assurance is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 593 once invoked, about $0.0003 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-30.

React Testing best-practices coding-standards flutter nestjs nextjs

server-side-calls

Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.

trpc/trpc · 61 tokens

quality-engineering-quality-assurance