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 zhoubengao/iLink --skill ilink-approvegit clone --depth 1 https://github.com/zhoubengao/iLinkWrote 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/zhoubengao/ilink/ilink-approve)<a href="https://agentmods.dev/skills/zhoubengao/ilink/ilink-approve"><img src="https://agentmods.dev/badge/skills/zhoubengao/ilink/ilink-approve/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/zhoubengao/ilink/ilink-approve"><img src="https://agentmods.dev/badge/skills/zhoubengao/ilink/ilink-approve.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.00000 | $0.01401 |
| Opus 5 | $0.00000 | $0.00700 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
ilink-approve 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ilink-approve
Run the iLink Human-Gate advance: Coach reflection subprocess (design-only) + Status advance.
Usage
/ilink-approve <story>
Preparation
The bash script .qoder/commands/ilink-approve <story> has already validated the STAGING document and reported which document will be advanced. Now in this slash invocation:
- Read
iLink/iLink-root-spec.md§4.7 (Coach role contract) and §6.4 (ilink-approve protocol) - Read
iLink/souls/coach.soul.md(Coach role specification)
Task
Execute the following steps in order. Coach subprocess errors SHALL NOT block Status advance.
Step 1: Resolve target STAGING document
Re-confirm the STAGING document by checking, in priority order:
iLink-doc/<story>/<story>-review.master.md→ if STAGING, target is QA review (no Status advance, Coach skipped)iLink-doc/<story>/<story>-design.master.md→ if STAGING, target advances toPENDING_CODERiLink-doc/<story>/<story>-pm.master.md→ if STAGING, target advances toPENDING_DESIGNER
If no STAGING document found, tell the user and stop.
Record target_role as review / design / pm for use in subsequent steps.
Step 2: Coach subprocess（仅当 target_role == "design" 时执行）
Root Spec §6.4：Coach 子流程仅在 design.master.md 推进场景启用。PM 与 review 推进场景跳过 Coach，但 MUST 保留 Status 推进逻辑。
If target_role != "design"，skip Steps 2.1–2.5，record "本轮非 design 推进，跳过 Coach"，and proceed directly to Step 3.
2.1 Excerpt conversation bracket
Identify in the current Qoder chat session:
- Outer window start: first human turn after the
ilink-pm <story>//ilink-pm <story>invocation - Outer window end: last human turn before this
/ilink-approve <story>invocation - Internal divider: the
/ilink-design <story>(orilink-design <story>) slash invocation turn
Excerpt every turn verbatim with [turn-N] (user|assistant) labels. Mark the divider as [--- /ilink-design 分界 ---]. SHALL NOT rewrite, summarize, or selectively skip turns.
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 · 123 lines · 0 tokens per session scan A 8f027bace9d5
ilink-approve 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 1,401 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.