agentmods.dev

ilink-lightme

ilink-lightme is a skill for Claude Code, Codex from zhoubengao/iLink. It costs 0 tokens per session (2,047 once invoked), scanned A, original, Apache-2.0.

An optional independent review step for iLink requirements or designs. It asks questions meant to reveal missing details and writes suggested revisions for the user to copy into the documents.

In plain words
What is it for?
Use it to examine a Story's planning or design document, identify gaps, and produce copy-ready changes.
Why use it?
It helps expose blind spots before later work begins, while leaving the workflow status and main documents unchanged. Running it in a fresh session can provide more separation from the earlier drafting work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 22repo 3mo ago A scan 0 tokens original Apache-2.0

Good fit Use it to examine a Story's planning or design document, identify gaps, and produce copy-ready changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zhoubengao/ilink/ilink-lightme
View source ↗ zhoubengao/iLink
Install

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.

Any agent
npx skills add zhoubengao/iLink --skill ilink-lightme
Clone the repo
git clone --depth 1 https://github.com/zhoubengao/iLink

Made for: Claude Code, Codex.

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.

agentmods badge for ilink-lightme

README.md
[![agentmods](https://agentmods.dev/badge/skills/zhoubengao/ilink/ilink-lightme/github.svg)](https://agentmods.dev/skills/zhoubengao/ilink/ilink-lightme)
Your own site
<a href="https://agentmods.dev/skills/zhoubengao/ilink/ilink-lightme"><img src="https://agentmods.dev/badge/skills/zhoubengao/ilink/ilink-lightme/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.

agentmods 80×15 button for ilink-lightme

Your own site · 80×15
<a href="https://agentmods.dev/skills/zhoubengao/ilink/ilink-lightme"><img src="https://agentmods.dev/badge/skills/zhoubengao/ilink/ilink-lightme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,047 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02047
Opus 5 $0.00000 $0.01024
Sonnet 5 $0.00000 $0.00409
Haiku 4.5 $0.00000 $0.00205

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

Security

Grade A, and why

ilink-lightme 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.

src/.qoder/skills/ilink-lightme/SKILL.md · 132 lines

How it starts

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

执行 iLink Lightme（设计/需求拷问员）角色 — 可选审视步骤，主流程之外，用于在使用者推进下游之前照亮盲区。

详见 Root Spec §4.8、iLink/souls/lightme.soul.md。advisory 性质，不改变 Status，不阻塞下游，SHALL NOT 触碰任何 master doc / project-context / domain-knowledge 文件。所有发现以 copy-ready 修订建议代码块的形式写入 lightme 报告，使用者自行复制粘贴。

用法

/ilink-lightme <story>                    # 默认拷问 design
/ilink-lightme -target pm <story>         # 拷问 pm
/ilink-lightme -target design <story>     # 显式拷问 design

前置准备

友情提示：建议在全新的 Qoder 会话中运行 lightme（见 Root Spec §4.8.3）。全新会话对抗"AI 自身合理性"和同会话护短通常更有效，但会重新读取 soul、项目文档、目标文档和相关代码，可能消耗更多 token。同一会话也允许执行，只是隔离效果下降。

在 Qoder 会话中输入 /ilink-lightme [-target pm|design] <story>。AI 会自动调用预检脚本（.qoder/commands/ilink-lightme，内部细节）校验目标文档存在并计算 Upstream_SHA1，然后按本章节执行拷问任务。若明显是在生成目标文档的同一会话中运行，先向使用者友情提示隔离效果下降与 token 权衡，但不阻断。

准备

  • 读取 iLink/souls/universal.soul.md 及其 plug（若存在）
  • 读取 iLink/souls/lightme.soul.md 及 iLink/souls/plugs/lightme.project.plug.md（若存在）

前置检查

lightme 不限目标文档状态——任何阶段（STAGING / PENDING_DESIGNER / PENDING_CODER / 已被下游消费 / 已 COMPLETED）都可触发，因为 lightme 不动 master doc。

Design 模式（默认）

  • 读取 iLink-doc/<story>/<story>-design.master.md
  • 若不存在，提示用户先执行 /ilink-design <story> 并退出

PM 模式（-target pm）

  • 读取 iLink-doc/<story>/<story>-pm.master.md
  • 若不存在，提示用户先执行 /ilink-pm <story> 并退出
  • 读取 iLink-doc/<story>/<story>-requirement.md（需求定义原文）

与 /ilink-refine 的顺序建议

若目标文档含 [待确认] 项，建议先 /ilink-refine 把 [待确认] 项澄清成 [已确认]，再 /ilink-lightme 拷问。理由：refine 解决"已知不确定性"，lightme 挖"未发现盲区"——先把已知问题压实，避免 lightme 在已经标了 [待确认] 的位置重复挖。

顺序不强制；使用者也可先跑 lightme 让两边问题一并暴露，再决定如何修订。

执行（拷问主流程）

Design 模式

按 lightme.soul.md 第 3 节"工作方式"执行：四原则 + 查代码找文档 + 术语拷问 + 场景压测 + 代码交叉验证。

按 lightme.soul.md 第 5 节执行追问策略：动态主导 + 高频维度评估扫描（不为凑数提问）。

按 lightme.soul.md 第 4 节执行检索局限标注：阳性 / 阴性结论区分。

每识别一个盲区 → 标注三态（RESOLVED / TO-FIX / ACCEPTED-RISK）→ 追加进 <story>-lightme-design.md 的"被照亮的盲区与处置"区块。TO-FIX 项 MUST 附 copy-ready 修订建议代码块（见下文）。

PM 模式（-target pm）

按 lightme.soul.md 第 3 节四原则执行，但拷问维度切换为需求层面：

Read the full file on GitHub · 132 lines

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.

  1. 11d ago First seen · 132 lines · 0 tokens per session scan A 9ef818fbd8b0

Subscribe to this mod's changes

ilink-lightme is a skill published in the GitHub repository zhoubengao/iLink (22 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,047 tokens. 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.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens