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.
npx skills add GongShichen/LuminaCode --skill qa-reportgit clone --depth 1 https://github.com/GongShichen/LuminaCodeWrote 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.
[](https://agentmods.dev/skills/gongshichen/luminacode/qa-report)<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.
<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>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.00021 | $0.00473 |
| Opus 5.5 | $0.00008 | $0.00189 |
| Sonnet 5.5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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.
What it actually says
Write QA evidence as <project_root>/QA_REPORT.md.
Before writing:
- Call
GetTeamContextand use its runtimecontractas the authoritative Team Acceptance Contract. - Do not invent a missing-contract finding because there is no
TEAM_ACCEPTANCE_CONTRACT.mdfile. A file is required only if the runtime contract lists that file inrequired_artifacts. - Keep the report concise enough for repair: normally 80-180 lines for small/medium tasks.
Required sections:
-
Scope verified
- User request summary.
- Runtime Team Acceptance Contract summary from
GetTeamContext. - Documents checked: PRD, UX design, plans, interface contract, integration report.
-
Environment
- Working directory.
- Runtime/tool versions when relevant.
- Setup commands and services started.
-
Command evidence
- Each required command from the Team Acceptance Contract.
- Exit status.
- Short stdout/stderr summary.
- Whether output proves the requirement.
-
Integration evidence
- Real user-facing component path exercised.
- Backend/API/storage/tooling contract exercised.
- Positive, negative, and persistence checks where applicable.
-
Parent workspace cleanliness
- Files present in the parent directory before/after when named-project work is used.
- Any byproducts and cleanup performed.
-
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.
-
Verdict
pass,fail, ornot_applicable.- Rationale and evidence references.
After writing the report, call SubmitGateVerdict and reference QA_REPORT.md in the evidence.
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.
- 2mo ago First seen · 56 lines · 21 tokens per session scan A c0d6d8bc79f4
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.
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.
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".
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.
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.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.