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-pipeline-selectorgit 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-pipeline-selector)<a href="https://agentmods.dev/skills/xiqin/loom/loom-pipeline-selector"><img src="https://agentmods.dev/badge/skills/xiqin/loom/loom-pipeline-selector/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-pipeline-selector"><img src="https://agentmods.dev/badge/skills/xiqin/loom/loom-pipeline-selector.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.00092 | $0.02093 |
| Opus 5 | $0.00046 | $0.01046 |
| Sonnet 5 | $0.00018 | $0.00419 |
| Haiku 4.5 | $0.00009 | $0.00209 |
Grade A, and why
loom-pipeline-selector 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 10d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI 自主流程选择
触发条件
- 用户未明确指定
--type，或显式要求 AI 选择流程。 - 用户描述需求时包含模糊信号（既非明显 typo 也非明显新功能）。
loom run --auto或 MCPloom_select_pipeline调用时。
职责边界
loom-pipeline-selector 是开发流水线步骤选择器，不是通用入口 router。它只在请求已经被判断为开发型任务，或用户明确要求自动选择流水线时使用。
- 入口分流、解释“该用哪个 loom 能力”由
loom-router负责。 - 具体选择
dynamic_steps、展示来源/风险/步骤、等待确认后写入pipeline.state.json由本 skill 负责。 - 本 skill 不处理 QA 验收、审查反馈、分支收尾、loom 使用咨询等非开发流水线入口，除非它们被明确纳入某个开发 pipeline。
执行流程
Step 1：收集信号
读取以下信号（由 PipelineSelector._collectSignals 完成）：
keywords：需求中的风险关键词（重构/跨模块/新功能/typo/依赖升级等）fileScope：估计影响文件数（1/3/5/10）hasSpecExists：specDir 是否已有 spec.mdhasSpecAndReqs：specDir 是否同时已有 spec.md 和 requirements.jsonhasRootCause：是否提到"根因""已定位"inWorktree：是否已在 git worktree 内
Step 2：规则短路
按 workflow.yaml > selection_rules.short_circuits 顺序匹配：
| 规则名 | 关键词 | file_scope_max | 步骤 |
|---|---|---|---|
| quickfix | typo/错别字/单文件/小修复 | ≤1 | executing, verification |
| chore | 依赖升级/npm update/配置调整/bump version | — | executing, verification |
| hotfix | 生产紧急/线上故障/P0/hotfix | — | approved, executing, verification |
| bugfix-no-brainstorm | bug/修复/fix + 根因明确 | ≤5 | planning, approved, executing, verification, code-review-request, review-gate, code-review-response, synced |
命中即返回，不调 AI。
Step 3：AI fallback（可选）
信号模糊 + 注入 aiClient 时，调 AI 传入 step_catalog + selection_rules 作 context，AI 返回 { steps, reasoning }。
未注入 aiClient 或 AI 失败 → 走 Step 4。
Step 4：规则兜底
按风险等级生成基础流程，并按增强/mandatory 信号追加结构化质量门：
- low：executing → verification
- medium：planning → approved → executing → verification → code-review-request → review-gate → code-review-response → synced
- high：brainstorming（若 spec 不存在）→ planning → approved → git-worktree（若不在 worktree）→ executing → verification → code-review-request → review-gate → code-review-response → synced
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 164 lines · 92 tokens per session scan A 1e43cdd968bc
loom-pipeline-selector is a skill published in the GitHub repository xiqin/loom (5 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 2,093 once invoked, about $0.0005 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…
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…
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…