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/post-write)<a href="https://agentmods.dev/commands/annyeong844/lumin-repo-lens/post-write"><img src="https://agentmods.dev/badge/commands/annyeong844/lumin-repo-lens/post-write/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/post-write"><img src="https://agentmods.dev/badge/commands/annyeong844/lumin-repo-lens/post-write.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.00051 | $0.00121 |
| Opus 5 | $0.00026 | $0.00060 |
| Sonnet 5 | $0.00010 | $0.00024 |
| Haiku 4.5 | $0.00005 | $0.00012 |
Grade A, and why
post-write 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 10d 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-write-gate/SKILL.md,
then read ${CLAUDE_PLUGIN_ROOT}/skills/lumin-repo-lens/references/command-routing.md.
Mode: post-write
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.
- 10d ago First seen · 12 lines · 51 tokens per session scan A c31c72eee1f9
post-write is a command published in the GitHub repository annyeong844/lumin-repo-lens (26 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 121 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.
Other commands, from other repositories
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
get-flow-run
Inspect a Postman Flow run by its Run ID — per-block logs, failing block, and status.
ia-report-bug
Report a bug in the whetstone plugin.
data-flow-analysis
Trace how data flows through the system from input to output.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
duck-off
Turn off Rubber Duck mode and answer normally.