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.
/plugin marketplace add annyeong844/lumin-repo-lens/plugin install lumin-repo-lensWrote 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/commands/annyeong844/lumin-repo-lens/refactor-plan)<a href="https://agentmods.dev/commands/annyeong844/lumin-repo-lens/refactor-plan"><img src="https://agentmods.dev/badge/commands/annyeong844/lumin-repo-lens/refactor-plan/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/commands/annyeong844/lumin-repo-lens/refactor-plan"><img src="https://agentmods.dev/badge/commands/annyeong844/lumin-repo-lens/refactor-plan.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.00044 | $0.00111 |
| Opus 5 | $0.00022 | $0.00056 |
| Sonnet 5 | $0.00009 | $0.00022 |
| Haiku 4.5 | $0.00004 | $0.00011 |
Grade A, and why
refactor-plan 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 11d 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
Read ${CLAUDE_PLUGIN_ROOT}/skills/lumin-repo-lens/SKILL.md,
then read ${CLAUDE_PLUGIN_ROOT}/skills/lumin-repo-lens/references/command-routing.md.
Mode: refactor-plan
Arguments: {{ARGUMENTS}}
Follow that mode exactly.
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.
- 11d ago First seen · 12 lines · 44 tokens per session scan A 0475ecea1f87
refactor-plan is a command published in the GitHub repository annyeong844/lumin-repo-lens (26 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 111 once invoked, about $0.0002 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.
Other commands, from other repositories
document
Record a decision as an ADR or RFC, or document existing code as a spec, doc, guide, or rule; record a supplied research report or evidence material; routes to the right document type.
init
First-time Archcore setup — detect the repo, compose the full first-day seed in one preview, create it on one confirm, and wire host configs.
plan
Plan a feature or initiative through a computed route — a small fix exits with no documents, one capability gets a spec and a plan, a large initiative gets an umbrella PRD with one spec per capability; name sdd, sources, iso, or research to run that path directly.
review
Review branch changes against Archcore docs, or report project health; --drift runs staleness detection, --deep a full documentation audit.
repo-cleanup
Commit accumulated spec doc changes: survey, group by logical batch, branch, commit, merge.
re-ping
A diagnostic command that confirms the reverse-engineering add-on is installed and responds correctly. It does not read files or analyse code.