What is qa-checklist-qality?

A skill for creating compact quality-assurance checklists from Jira work items and GitHub pull requests. Jira is a tool for tracking work, while a pull request is a proposed code change for review.

Use it to write checklist items in the form “what to test? — expected result” and, when requested, update linked QAlity Test issues in Open Supply Hub's Jira.

It turns ticket and code-change details into specific checks with expected results, reducing the chance that important changes are tested vaguely or forgotten.

How opensupplyhub/open-supply-hub configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to opensupplyhub/open-supply-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/opensupplyhub/open-supply-hub/main/.agent/skills/qa-checklist-qality/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/opensupplyhub/open-supply-hub

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/opensupplyhub/open-supply-hub/qa-checklist-qality/github.svg)](https://agentmods.dev/skills/opensupplyhub/open-supply-hub/qa-checklist-qality)

Your own site

<a href="https://agentmods.dev/skills/opensupplyhub/open-supply-hub/qa-checklist-qality"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/qa-checklist-qality/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/opensupplyhub/open-supply-hub/qa-checklist-qality"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/qa-checklist-qality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,194 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.00073	$0.02194
Opus 5	$0.00036	$0.01097
Sonnet 5	$0.00015	$0.00439
Haiku 4.5	$0.00007	$0.00219

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

Security

Grade A, and why

qa-checklist-qality 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 11d 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.

.agent/skills/qa-checklist-qality/SKILL.md · 233 lines

How it starts

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

QA Checklist & QAlity Test Case

Generate a compact QA checklist from Jira + PR context, then push it into the linked QAlity Test issue when requested.

When to use

User shares a Jira story and/or GitHub PR(s) and wants a QA checklist
User wants each item as what to test? — expected result
User asks to update a QAlity Test issue (issuetype: QAlity Test) with test steps
User mentions change list, OSDEV-####, or test cycle (Passes/Failed/Blocked)

Inputs to collect

Input	Required	Example
Jira story key/URL	Yes	`OSDEV-1149`
GitHub PR URL(s)	If available	`opensupplyhub/open-supply-hub#1094`
QAlity Test key/URL	If updating Jira	`OSDEV-3013`
Environment notes	Optional	reindex required, Test vs Staging

Workflow

1. Gather context

Jira story (Atlassian MCP):

getJiraIssue
  cloudId: ce4a9d75-c0aa-460b-92fa-28cb0a11baa6
  issueIdOrKey: <STORY_KEY>
  fields: summary, description, comment, issuelinks
  responseContentFormat: markdown

Read: user story, acceptance criteria, dev QA notes in comments, linked QAlity Test (tests link).

GitHub PR(s):

Prefer gh pr view <num> --repo opensupplyhub/open-supply-hub --json title,body
If gh is unavailable, use WebFetch on the PR URL

Extract: functional changes, deploy/release steps, null semantics, out-of-scope follow-ups.

2. Write the QA checklist

Use this structure:

Prerequisites — data/env setup before testing
AC coverage — one row per acceptance criterion
Regression — existing behaviour unchanged
Out of scope — informational; do not block release

Item format (required):

what to test? — expected result

In Jira/QAlity fields:

Test Step ← what to test?
Expected Result ← expected result

Keep items actionable (concrete endpoint, UI path, or data condition). Reference legacy APIs or admin UI when they are the source of truth.

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

11d ago First seen · 233 lines · 73 tokens per session scan A 9d03176d4654

Subscribe to this mod's changes

qa-checklist-qality is a skill published in the GitHub repository opensupplyhub/open-supply-hub (20 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 2,194 once invoked, about $0.0004 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

open-supply-hub: Skill for Claude Code