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-initgit 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-init)<a href="https://agentmods.dev/skills/zhoubengao/ilink/ilink-init"><img src="https://agentmods.dev/badge/skills/zhoubengao/ilink/ilink-init/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-init"><img src="https://agentmods.dev/badge/skills/zhoubengao/ilink/ilink-init.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.00490 |
| Opus 5 | $0.00000 | $0.00245 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
ilink-init 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 9d 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
你现在执行 iLink 的 Story 初始化 操作。
参数
$ARGUMENTS 包含两个由空格分隔的参数：<story-id> <usage-value>。
<story-id>：本次要初始化的 Story ID<usage-value>：执行本命令前，用户在 Qoder 中执行/usage查看到的"已使用 credits"数值
必填校验
如果 $ARGUMENTS 为空或解析后不包含两个参数（即缺少 <usage-value>），MUST 拒绝执行，向用户输出：
❌ 用法：/ilink-init <story-id> <usage-value>
请先在 Qoder 中执行 /usage 查看"已使用 credits"，然后以如下格式重试：
/ilink-init <story-id> <已使用 credits 数字>
例如，/usage 显示已使用 1200 credits，则执行：/ilink-init kcia-1520 1200
无法查询时允许传入 0（语义为"故意跳过"，文件正常写入但 delta 标注不可信）。
执行任务
调用 bash 脚本执行实际初始化（脚本完成所有校验、目录创建、模板生成）：
bash .qoder/commands/ilink-init $ARGUMENTS
SHALL NOT：
- 自己创建目录、自己写模板文件——这些全部由 bash 脚本完成
输出处理
首要原则：bash 脚本的 stdout / stderr 原样转给用户——脚本已包含完整的进度信息、成功提示、错误指引。SHALL NOT 重复转述或自行解释脚本已经说过的内容。
仅在脚本退出码 0 时，追加 1 行简短下一步提示（脚本本身不输出这行）：
下一步：编辑 requirement.md 填写需求内容，完成后执行
/ilink-pm <story-id>进入需求分析阶段。
脚本退出码非 0 时：SHALL NOT 再次调用脚本、SHALL NOT 添加任何补充说明。用户根据 stderr 自行处理。
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.
- 9d ago First seen · 45 lines · 0 tokens per session scan A ce816371f609
ilink-init is a skill published in the GitHub repository zhoubengao/iLink (22 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 490 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.