QA Report

QA Report is a skill for Claude Code from GongShichen/LuminaCode. It costs 21 tokens per session (473 once invoked), scanned A, original, Apache-2.0.

A lasting quality-assurance report containing evidence, command results, unresolved findings, and the reasoning behind its verdict. Quality assurance checks whether software meets expected standards and requirements.

In plain words
What is it for?
Use it to document test results, outstanding issues, supporting evidence, and whether a change should pass review.
Why use it?
It preserves what was checked and why the final judgment was made, including problems that remain open.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to document test results, outstanding issues, supporting evidence, and whether a change should pass review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gongshichen/luminacode/qa-report
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 GongShichen/LuminaCode --skill qa-report
Clone the repo
git clone --depth 1 https://github.com/GongShichen/LuminaCode

Made for: Claude Code.

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.

agentmods badge for QA Report

README.md
[![agentmods](https://agentmods.dev/badge/skills/gongshichen/luminacode/qa-report/github.svg)](https://agentmods.dev/skills/gongshichen/luminacode/qa-report)
Your own site
<a href="https://agentmods.dev/skills/gongshichen/luminacode/qa-report"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/qa-report/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.

agentmods 80×15 button for QA Report

Your own site · 80×15
<a href="https://agentmods.dev/skills/gongshichen/luminacode/qa-report"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/qa-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 473 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00473
Opus 5.5 $0.00008 $0.00189
Sonnet 5.5 $0.00004 $0.00095
Haiku 4.5 $0.00002 $0.00047

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

Security

Grade A, and why

QA Report 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 2mo 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.

.Lumina/TEAM/product-development/qa/skills/qa-report/SKILL.md · 56 lines

What it actually says

Write QA evidence as <project_root>/QA_REPORT.md.

Before writing:

  • Call GetTeamContext and use its runtime contract as the authoritative Team Acceptance Contract.
  • Do not invent a missing-contract finding because there is no TEAM_ACCEPTANCE_CONTRACT.md file. A file is required only if the runtime contract lists that file in required_artifacts.
  • Keep the report concise enough for repair: normally 80-180 lines for small/medium tasks.

Required sections:

  1. Scope verified

    • User request summary.
    • Runtime Team Acceptance Contract summary from GetTeamContext.
    • Documents checked: PRD, UX design, plans, interface contract, integration report.
  2. Environment

    • Working directory.
    • Runtime/tool versions when relevant.
    • Setup commands and services started.
  3. Command evidence

    • Each required command from the Team Acceptance Contract.
    • Exit status.
    • Short stdout/stderr summary.
    • Whether output proves the requirement.
  4. Integration evidence

    • Real user-facing component path exercised.
    • Backend/API/storage/tooling contract exercised.
    • Positive, negative, and persistence checks where applicable.
  5. Parent workspace cleanliness

    • Files present in the parent directory before/after when named-project work is used.
    • Any byproducts and cleanup performed.
  6. Findings

    • Blocking findings.
    • Non-blocking findings.
    • Deferred items and why they are safe.
    • Any failure of an explicit user requirement, PRD acceptance criterion, UX requirement, or runtime contract item belongs in blocking findings. Examples include localized-error requirements, required exit-code semantics, required integration behavior, or required artifacts.
    • Do not classify an explicit requirement violation as non-blocking just because the happy path works or the issue is common in a framework.
  7. Verdict

    • pass, fail, or not_applicable.
    • Rationale and evidence references.

After writing the report, call SubmitGateVerdict and reference QA_REPORT.md in the evidence.

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.

  1. 2mo ago First seen · 56 lines · 21 tokens per session scan A c0d6d8bc79f4

Subscribe to this mod's changes

QA Report is a skill published in the GitHub repository GongShichen/LuminaCode (9 stars, last pushed 4d ago), licensed Apache-2.0. It adds 21 tokens to every session and 473 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-30.

Related

Other skills, from other repositories

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

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens