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 evidence-matrixgit 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/evidence-matrix)<a href="https://agentmods.dev/skills/gongshichen/luminacode/evidence-matrix"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/evidence-matrix/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/evidence-matrix"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/evidence-matrix.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.00015 | $0.00519 |
| Opus 5.5 | $0.00006 | $0.00208 |
| Sonnet 5.5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
Evidence Matrix 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
Build an evidence matrix that can support a final report.
Inputs:
- Research contract.
- Source notes.
sources.jsonl.- Existing
evidence-matrix.jsonl. - Conflicts or gate findings.
Procedure:
-
Enumerate answer claims
- Extract candidate claims from source notes.
- Group claims by subquestion.
- Remove claims that do not answer the contract.
-
Link sources
- Each evidence item must reference one or more source IDs.
- Use multiple independent sources for major claims when possible.
- Use only sources whose
sources.jsonlrecord hasretrieval_statusofretrievedorpartially_retrievedandclaim_support_allowed: true. - Exclude sources marked
inaccessible,claim_support_allowed: false, metadata-only, snippet-only, or fetch_failed.
-
Classify support
- direct empirical result.
- benchmark/dataset evidence.
- theoretical argument.
- official statement/specification.
- expert opinion.
- indirect/contextual evidence.
-
Assess confidence
- high: direct, credible, recent, and corroborated.
- medium: credible but limited or single-source.
- low: weak, old, indirect, or contested.
-
Capture conflicts
- Record conflicting evidence and why it differs.
- Do not hide inconvenient sources.
-
Identify gaps
- Missing source class.
- Missing recent evidence.
- Missing primary evidence.
- Unsupported final-report claim.
Output JSONL schema:
{"claim_id":"C001","subquestion":"...","claim":"...","source_ids":["S001","S002"],"support_type":"direct empirical result","confidence":"high|medium|low","evidence_summary":"...","limitations":"...","conflicts":["..."],"report_recommendation":"use|caveat|exclude"}
Also update conflicts-and-limitations.md with:
- Strongest conflicts.
- Evidence gaps.
- How these affect final recommendations.
Completion criteria:
- Report Writer can cite every key claim from the matrix.
- QA can verify source IDs.
- Reviewer can judge whether the method is adequate.
- No evidence item depends on a source that Source Reader did not retrieve.
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 · 73 lines · 15 tokens per session scan A d9e896b23f95
Evidence Matrix is a skill published in the GitHub repository GongShichen/LuminaCode (9 stars, last pushed 4d ago), licensed Apache-2.0. It adds 15 tokens to every session and 519 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
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…