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 citation-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/citation-qa-report)<a href="https://agentmods.dev/skills/gongshichen/luminacode/citation-qa-report"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/citation-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/citation-qa-report"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/citation-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.00840 |
| Opus 5.5 | $0.00008 | $0.00336 |
| Sonnet 5.5 | $0.00004 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
Citation QA Report scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Web claims have WebFetch-backed sources or documented shell/curl fallback sources after a recorded WebFetch/WebSearch failure. What it actually says
Audit the research artifacts for traceability.
Before reviewing:
- Call
GetTeamContext. - Use runtime contract as authoritative.
- Read required artifacts from the Lumina team runtime directory.
Procedure:
- Load context and artifacts.
- Validate required artifacts.
- Parse source registry and evidence matrix.
- Cross-check final-report source IDs.
- Classify findings as blocking or nonblocking.
- Write
qa-report.md. - Call
SubmitGateVerdictforcitation_qa.
Checks:
-
Artifact completeness
- Required artifacts exist.
- Files are non-empty and relevant.
- Runtime artifacts are not accidentally written into project root unless requested.
-
Source registry
sources.jsonlparses as JSONL.- Each source has source_id, title, url or arxiv_id, source_type, retrieval_tool, retrieval_status, claim_support_allowed, and notes_path.
- Source IDs are unique.
- Sources used by evidence items are
retrievedorpartially_retrievedand haveclaim_support_allowed: true. retrieval_statusvalues are onlyretrieved,partially_retrieved, orinaccessible.
-
Evidence matrix
evidence-matrix.jsonlparses as JSONL.- Each evidence item has claim, source_ids, confidence, support_type.
- Referenced source IDs exist in
sources.jsonl.
-
Final report citations
- Key claims cite source IDs.
- Cited source IDs exist.
- No major claim relies only on snippets.
final-report.mdcontains a readable source index and evidence index. The evidence index must map evidence IDs to source IDs so the user can audit the report from the working-directory deliverable package.
-
Retrieval quality
- Web claims have WebFetch-backed sources or documented shell/curl fallback sources after a recorded WebFetch/WebSearch failure.
- Academic paper claims have arXiv MCP or fetched paper notes when applicable.
- No evidence item is marked as supported by model memory, training knowledge, snippets, or unretrieved metadata.
- Inaccessible sources are clearly excluded from final-report claim support.
Blocking findings:
- Any final-report key claim without a valid source ID.
- Any cited source ID missing from
sources.jsonl. - Any claim supported only by search snippets, model training knowledge, memory, unretrieved metadata, or undocumented fallback retrieval.
- Any inaccessible source used as if it were retrieved evidence.
- Any evidence item citing a source whose
retrieval_statusis missing,inaccessible,fetch_failed, or whoseclaim_support_allowedis false. - Any source record using invalid retrieval status aliases such as
success,fail,fetched, orfetch_failed. - Any Search Strategist candidate list being treated as
sources.jsonlwithout Source Reader retrieval notes. - Missing
sources.jsonl,evidence-matrix.jsonl, orfinal-report.mdwhen required by the contract. - Missing source/evidence index in
final-report.md.
Output:
Write qa-report.md:
# Citation QA Report
## Verdict
pass|fail|not_applicable
## Artifact Checks
| Artifact | Status | Evidence |
## Source Registry Checks
...
## Evidence Matrix Checks
...
## Citation Checks
...
## Findings
### Blocking
- ...
### Nonblocking
- ...
## Gate Evidence
- ...
Then call SubmitGateVerdict:
- gate/check name:
citation_qa - status:
pass,fail, ornot_applicable - evidence: artifact checks and report path.
- findings: include blocking flags where appropriate.
Pass requires concrete evidence, not just "looks good".
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 · 110 lines · 21 tokens per session scan A 5790d8b7ec73
Citation 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 840 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…