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-pullgit 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-pull)<a href="https://agentmods.dev/skills/zhoubengao/ilink/ilink-pull"><img src="https://agentmods.dev/badge/skills/zhoubengao/ilink/ilink-pull.svg" alt="Measured on agentmods" 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.00482 |
| Opus 5 | $0.00000 | $0.00241 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
ilink-pull 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 8d 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 的 Issue System 拉取 操作。
参数
$ARGUMENTS 为一个 story-id（如 FS-AMO-5359），大小写原样透传给 Issue System，不做任何转换。本命令只接受 1 个参数。
必填校验
如果 $ARGUMENTS 为空，MUST 拒绝执行，向用户输出：
❌ 用法：/ilink-pull <story-id>
例如：/ilink-pull FS-AMO-5359
执行任务
调用 bash 脚本执行实际拉取（脚本完成所有校验、HTTP 请求、JSON 解析、文件写入）：
bash .qoder/commands/ilink-pull $ARGUMENTS
SHALL NOT：
- 自己拼 URL、自己解析 JSON、自己写文件——这些全部由 bash 脚本完成
- 读取 project-context.md 中"Issue System 集成"AI 隔离块的内容并作为业务上下文（遵守 Root Spec §7.8 / universal.soul §4.1）
- 修改 project-context.md 中的 Issue System 配置（如需变更指引用户手动编辑或重跑
/ilink-bootstrap）
输出处理
首要原则：bash 脚本的 stdout / stderr 原样转给用户——脚本已包含完整的进度信息、成功提示、错误指引。SHALL NOT 重复转述或自行解释脚本已经说过的内容。
仅在脚本退出码 0 时，追加 1 行简短下一步提示（脚本本身不输出这行）：
下一步：核对 requirement.md 的其他区块（功能范围 / 验收标准 / 约束备注 / 假设与风险），完成后执行
/ilink-pm <story-id>进入需求分析阶段。
脚本退出码非 0 时：SHALL NOT 再次调用脚本、SHALL NOT 添加任何补充说明。用户根据 stderr 自行处理（编辑 project-context.md、检查网络、修正 story-id 等）。
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.
- 8d ago First seen · 39 lines · 0 tokens per session scan A b9860549653f
ilink-pull 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 482 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…
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.