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 xiqin/loom --skill loom-routergit clone --depth 1 https://github.com/xiqin/loomWrote 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/xiqin/loom/loom-router)<a href="https://agentmods.dev/skills/xiqin/loom/loom-router"><img src="https://agentmods.dev/badge/skills/xiqin/loom/loom-router/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/xiqin/loom/loom-router"><img src="https://agentmods.dev/badge/skills/xiqin/loom/loom-router.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.00045 | $0.01292 |
| Opus 5 | $0.00023 | $0.00646 |
| Sonnet 5 | $0.00009 | $0.00258 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
loom-router 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loom 入口路由
loom-router 是轻量入口分流层，只判断当前请求应该进入哪个 loom 能力。它不生成 dynamic_steps，不写 pipeline.state.json，不替代 loom-pipeline-selector。
触发条件
- 用户提出新请求，但还不清楚应使用哪个 loom skill。
- 用户问“这个任务应该走什么流程”。
- 请求可能属于 bug、功能开发、代码审查、QA、分支收尾、索引更新、架构改进、技能编写或 loom 使用咨询之一。
- 当前会话需要判断继续当前上下文、写 handoff、压缩，还是开 fresh session。
非触发条件
- 已经处在明确的 pipeline stage 中，并且下一步由
pipeline.state.json/progress.md决定。 - 用户已经明确指定要运行某个 skill。
loom-pipeline-selector已完成选择且用户已确认，后续应按 pipeline 状态执行。
职责边界
router 负责
- 识别请求入口类型。
- 解释推荐路径和理由。
- 判断是否需要先澄清、先复现、先审查、先 QA，或交给
loom-pipeline-selector。 - 给出上下文卫生建议：继续当前会话、写 handoff、压缩，或开 fresh session。
router 禁止
- 禁止直接写
pipeline.state.json。 - 禁止生成或持久化
dynamic_steps。 - 禁止绕过
loom-pipeline-selector的用户确认门禁。 - 禁止把自己变成第二套 pipeline planner。
路由表
| 用户请求类型 | 推荐入口 | 说明 |
|---|---|---|
| 新功能、需求、跨模块改动 | loom-pipeline-selector |
router 只说明应进入开发流水线；具体 steps 由 selector 选择并等待用户确认。 |
| 需求含糊、设计取舍多 | loom-brainstorming |
先澄清 shared understanding，再进入 spec / plan。 |
| bug、测试失败、异常行为 | loom-systematic-debugging |
先构造 red-capable feedback loop，再考虑修复。 |
| 明确行为变更或 bug 修复 | loom-test-driven-development |
在实现阶段使用 seam gate 和红绿重构。 |
| 准备发起审查 | loom-requesting-code-review |
先做 Standards + Spec 双轴预审查，再生成审查请求。 |
| 收到审查反馈 | loom-receiving-code-review |
分类处理、修复或 push back。 |
| 新功能验收或 release 验收 | loom-qa |
生成/执行 QA 用例并输出报告。 |
| 开发分支已验证完成 | loom-finishing-a-development-branch |
选择 merge、PR、keep 或 discard。 |
| 代码已变更且验证通过 | loom-index-update |
同步图后端、memory 和必要入口文档。 |
| 多个独立任务可并行 | loom-dispatching-parallel-agents |
仅在无共享文件冲突且已有确认 plan 时使用。 |
| 需要编写或修改 skill | loom-writing-skills |
检查职责边界、触发条件、完成标准和 context load。 |
| 用户询问 loom 能力 | loom-using-loom |
解释框架、skills 和 pipeline。 |
执行流程
Step 1：分类请求
用一句话标注请求类型，例如：bug 调试、新功能开发、代码审查、QA 验收、分支收尾、loom 咨询。
Step 2：说明推荐路径
输出推荐入口、原因和下一步。开发型任务必须说明：具体流水线仍由 loom-pipeline-selector 选择，且需要用户确认后才会写入状态。
Step 3：判断是否需要阻塞执行
以下情况必须先停下，不直接实现：
- 需求关键行为不清楚。
- bug 没有可运行的失败信号。
- 要审查的 diff 或 fixed point 不明确。
- pipeline selector 尚未展示步骤并获得用户确认。
- 阶段切换前还没有写 handoff。
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 · 105 lines · 45 tokens per session scan A 1ff6a6080ad3
loom-router is a skill published in the GitHub repository xiqin/loom (5 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,292 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…