What is lumin-repo-lens-canon?

Maintainer instructions for Lumin Repo Lens, a tool that audits repository facts and checks whether its canonical record has drifted. Canonical facts are the reviewed facts treated as the project’s reference record.

Use it to draft or check repository facts, review parser contracts, detect drift, and validate audit results.

It helps maintainers distinguish verified repository information from missing or outdated information and report the evidence range.

lumin-repo-lens-canon — Skill for Claude Code and Codex by annyeong844

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add annyeong844/lumin-repo-lens

Claude Code

/plugin install lumin-repo-lens

Made for: Claude Code, Codex.

Or install lumin-repo-lens, the plugin that ships this one along with the rest of its 3 skills, 9 commands, 4 hooks.

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/annyeong844/lumin-repo-lens/lumin-repo-lens-canon/github.svg)](https://agentmods.dev/skills/annyeong844/lumin-repo-lens/lumin-repo-lens-canon)

Your own site

<a href="https://agentmods.dev/skills/annyeong844/lumin-repo-lens/lumin-repo-lens-canon"><img src="https://agentmods.dev/badge/skills/annyeong844/lumin-repo-lens/lumin-repo-lens-canon/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/annyeong844/lumin-repo-lens/lumin-repo-lens-canon"><img src="https://agentmods.dev/badge/skills/annyeong844/lumin-repo-lens/lumin-repo-lens-canon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 813 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.

Model	Per session	Once invoked
Fable 5.1	$0.00053	$0.00813
Opus 5	$0.00026	$0.00407
Sonnet 5	$0.00011	$0.00163
Haiku 4.5	$0.00005	$0.00081

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

Security

Grade A, and why

lumin-repo-lens-canon 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 12d 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.

skills/lumin-repo-lens-canon/SKILL.md · 104 lines

How it starts

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

Lumin Repo Lens Canon

This is the maintainer-facing canonical fact surface for lumin-repo-lens. It owns canon-draft and check-canon together because draft output is reviewed, promoted, and later checked for drift as one lifecycle.

Default voice is concise and factual. This surface may use colder terminology than the audit surface, but every claim still needs machine evidence and scan range. Do not use casual hedging. If evidence is missing or degraded, emit unknown or a degraded status directly with the scan range.

Core Contract

NO STRUCTURAL CLAIM WITHOUT MACHINE EVIDENCE
NO ABSENCE CLAIM WITHOUT STATED SCAN RANGE

Shared Engine

The shared engine lives in the sibling audit skill:

node ${CLAUDE_PLUGIN_ROOT}/skills/lumin-repo-lens/scripts/audit-repo.mjs

In a maintainer checkout, the equivalent command is:

node audit-repo.mjs

Slash commands still read <SKILL_ROOT>/references/command-routing.md from the shared audit skill for exact flag routing. Below, <SKILL_ROOT> means ${CLAUDE_PLUGIN_ROOT}/skills/lumin-repo-lens in plugin installs, or the repo root in a maintainer checkout.

Below, <audit-repo> means whichever of the two commands above applies to the current context.

This surface owns /lumin-repo-lens:canon-draft and /lumin-repo-lens:check-canon.

References To Load

Read <SKILL_ROOT>/references/command-routing.md first for slash-command routing.
Read <SKILL_ROOT>/references/lifecycle-modes.md when exact flags, exit codes, or artifact names matter.
Read <SKILL_ROOT>/canonical/canon-drift.md for drift categories, parser contract, per-source Markdown reports, and canon-drift.json shape.
Read <SKILL_ROOT>/canonical/fact-model.md, <SKILL_ROOT>/canonical/identity-and-alias.md, and <SKILL_ROOT>/canonical/classification-gates.md when a drift category, identity, or label set is ambiguous.

Canon Draft

Use when current artifacts should propose canonical facts for review:

Read the full file on GitHub · 104 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 277 B

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.

12d ago First seen · 104 lines · 53 tokens per session scan A f6a896993ecb

Subscribe to this mod's changes

lumin-repo-lens-canon is a skill published in the GitHub repository annyeong844/lumin-repo-lens (26 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 813 once invoked, about $0.0003 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.

Claude Code Debugging claude-code-plugin plugin repository-analysis

ask-codex

Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…

umputun/cc-thingz · 103 tokens

root-cause-investigator

Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.

umputun/cc-thingz · 53 tokens

diagnose-hard-bug

Hard-bug diagnosis: tight loop, ranked hypotheses.

martineserios/thebrana · 17 tokens

codex-model-guard

Install, inspect, update or remove native Model Guard for Codex CLI. Use for its status line, model-routing diagnostics (effective-model header and response body label), passive 516 reasoning anomalies and account display.

ventusff/claude-model-guard · 48 tokens

diagnosing-bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

martineserios/thebrana · 40 tokens

release-it

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…

wondelai/skills · 131 tokens