What is quality-assurance?

A collection of testing and validation practices for software projects whose work is guided by written specifications.

Use it during specification phases, feature implementation, completed-work reviews, and the setup of automated quality checks.

It helps catch unclear requirements, design problems, and implementation defects at the stage where they are cheapest to fix.

quality-assurance — Skill for Claude Code by jasonkneen

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 jasonkneen/kiro --skill quality-assurance

Clone the repo

git clone --depth 1 https://github.com/jasonkneen/kiro

Made for: Claude Code.

Or install kiro, the plugin that ships this one along with the rest of its 8 skills, 2 commands.

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/jasonkneen/kiro/quality-assurance/github.svg)](https://agentmods.dev/skills/jasonkneen/kiro/quality-assurance)

Your own site

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

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

When invoked 1,950 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.00033	$0.01950
Opus 5	$0.00016	$0.00975
Sonnet 5	$0.00007	$0.00390
Haiku 4.5	$0.00003	$0.00195

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

Security

Grade A, and why

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.

skills/quality-assurance/SKILL.md · 333 lines

How it starts

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

Quality Assurance

Ensure quality throughout the spec-driven development process with validation techniques, quality gates, and testing strategies.

When to Use This Skill

Use quality assurance practices when:

Completing any spec phase (requirements, design, tasks)
Transitioning between phases
Implementing features from specs
Reviewing completed work
Establishing team quality standards

Core Principles

Requirements-Driven Testing: Every test traces to a requirement
Phase-Appropriate Validation: Different techniques for each phase
Continuous Quality: Checks throughout development
Automated Where Possible: Reduce manual effort
Fast Feedback: Catch issues early

Phase-Specific Validation

Requirements Phase Validation

Quality Checklist:

All user stories have acceptance criteria
Requirements are unambiguous and specific
Each requirement can be validated/tested
EARS format used consistently
Requirements link to business objectives
No conflicting requirements

Review Process:

Self Review: Author checks completeness
Stakeholder Review: Business validates requirements
Technical Review: Team assesses feasibility
Approval: Formal sign-off before design

Validation Techniques:

Scenario Walkthroughs: Step through user journeys
Edge Case Analysis: Identify boundary conditions
Conflict Detection: Check for contradictions
Completeness Analysis: Ensure all needs covered

Design Phase Validation

Quality Checklist:

Design addresses all requirements
Scalability considerations documented
Maintainability assessed
Security addressed
Performance requirements considered
External integrations defined

Review Process:

Architecture Review: Senior team validates design
Security Review: Security implications assessed
Performance Review: Performance characteristics evaluated
Integration Review: External dependencies validated

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

13d ago First seen · 333 lines · 33 tokens per session scan A 22464717fcaa

Subscribe to this mod's changes

quality-assurance is a skill published in the GitHub repository jasonkneen/kiro (746 stars, last pushed 8mo ago), licensed MIT. It adds 33 tokens to every session and 1,950 once invoked, about $0.0002 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

quality-assurance