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-analyze-artifactsgit 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-analyze-artifacts)<a href="https://agentmods.dev/skills/xiqin/loom/loom-analyze-artifacts"><img src="https://agentmods.dev/badge/skills/xiqin/loom/loom-analyze-artifacts/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-analyze-artifacts"><img src="https://agentmods.dev/badge/skills/xiqin/loom/loom-analyze-artifacts.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.00109 | $0.01559 |
| Opus 5 | $0.00055 | $0.00779 |
| Sonnet 5 | $0.00022 | $0.00312 |
| Haiku 4.5 | $0.00011 | $0.00156 |
Grade A, and why
loom-analyze-artifacts 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
跨产物一致性分析(analyze-artifacts)
触发条件
specs/<date+feature>/plan.md、tasks/、traceability.json、requirements.json、spec.md均已存在。- 即将进入
approvedgate,但还没人做过跨产物一致性检查。
非触发条件
- quickfix / chore / hotfix 等无 spec/plan 的轻量流程。
- 已在 verification 阶段(那时改用
loom-converge)。
执行流程
Step 1:运行分析
调用 loom MCP 工具 loom_analyze_artifacts(参数 spec_dir)。
工具只读分析 spec.md、requirements.json、plan.md、tasks/T*.md、traceability.json、.loom/rules/constitution.md(若存在),执行下列检查并输出 artifact-analysis.json。返回 ok:false 表示有 blocker finding。
Step 2:跨产物一致性检查
按以下维度逐项检查,每条 finding 记录 { id, kind, severity, message, requirement_id?, behavior_id?, task_id?, artifact, suggested_fix }。
- 重复需求:
spec.md中两个REQ-xxx实际描述同一行为。 - 歧义需求:
spec.md有两种解释且未选定一种。 - 欠规格:
requirements.json缺少 spec 中的REQ-xxx,或某 REQ 的required_categories未覆盖。 - behavior 缺失:
requirements.json的required_categories没有 behavior 实现。 - task 未映射:
plan.md引用的 task 文件不存在,或tasks/中文件未在plan.md列出。 - behavior 未映射到 task:
requirements.json的某 behavior 在所有 task frontmatterbehavior_ids中都未出现。 - task 引用未知 behavior:task 的
behavior_ids不在requirements.json中。 - task 引用未知 requirement:task 的
requirements不在spec.md中。 - traceability 缺 REQ/behavior:
traceability.json缺少spec.md/requirements.json中的 REQ 或 behavior。 - traceability 引用未知 REQ/behavior:
traceability.json出现requirements.json没有的 REQ/behavior。 - traceability task 引用不存在:
traceability.json的 tasks 不对应真实tasks/T*.md。 - 依赖环:task
depends_on构成环。 - owns 冲突:多个 task 声明同一
owns文件。 - constitution 冲突:task 计划修改的路径与
.loom/rules/constitution.md的分层/禁止目录冲突。 - 非功能要求遗漏:
requirements.json声明performance/security/observability类型,但没有任何 task 或 behavior 覆盖对应维度。
Step 3:计算 coverage
{
"requirement_coverage": "已映射 task 的 REQ 数 / spec REQ 总数",
"behavior_coverage": "已映射 task 的 behavior 数 / requirements behavior 总数",
"required_category_coverage": "已覆盖的 required_categories 数 / 声明总数",
"traceability_req_coverage": "traceability 中 REQ 数 / requirements REQ 数",
"traceability_behavior_coverage": "traceability 中 behavior 数 / requirements behavior 数"
}
What ships with it
1 file 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.
- 8d ago First seen · 127 lines · 109 tokens per session scan A ef4276bcfdb3
loom-analyze-artifacts is a skill published in the GitHub repository xiqin/loom (5 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 1,559 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…
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…