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 agentmods add skills/valkor-ai/loom/loomnpx skills add valkor-ai/loom --skill loomgit clone --depth 1 https://github.com/valkor-ai/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/valkor-ai/loom/loom)<a href="https://agentmods.dev/skills/valkor-ai/loom/loom"><img src="https://agentmods.dev/badge/skills/valkor-ai/loom/loom.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 | $0.00025 | $0.01564 |
| Opus 5 | $0.00013 | $0.00782 |
| Sonnet 5 | $0.00005 | $0.00313 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
loom 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 5d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loom
You are the Claude Code adapter for Loom MCP. The /loom command chooses the first Loom MCP tool. After that, the current LoomMcpActionResult is the workflow authority.
Do not replace Loom with Claude Plan Mode. Do not inspect project .loom state to decide the next step. Use Loom MCP tools and resources.
When loom.plan returns a plan-conflict user gate, present its numbered choices and descriptions exactly. Choice 1 calls loom.planConflictResolve with continue_current; choice 2 calls it with start_new. Do not call loom.plan again to resolve the conflict.
Result Discipline
auto_runnable: keep going immediately by executing the returnednext.kind.active_operation: only use the observation tools named by the result.user_gate: whenpreResponseContractis present, execute its steps in order before emitting any user-visible response. This means callingloom.inspectRequest, reading only the groups fromrequestReadPlan.groupswhosewhenToReadapplies before the visible response withloom.readFieldGroup, and, for Brainstorm, completing every requiredknowledge_context_planstep before forming options or confirmation. Groups scheduled after user confirmation remain required before the confirm/submit call. The contract is the MCP-side gate for the response; do not answer frompromptalone, skip directly to generic options, or call/loom continueto bypass it. A phase-continuation Brainstorm gate is an active clarification turn, not an optional/loom continue: do not stop at a progress recap or say "if you want to continue". After the contract steps complete, ask the visible current-block question and wait for the user's answer. For a gate withoutpreResponseContract, present the returned prompt and wait for the accepted user response.repairable_error:stopAllowed=false; first callloom.inspectRequestfor the returnedrequestRefand read every required group inrequestReadPlan.groupswithloom.readFieldGroup, then repair only the returned target and resubmit with the returned tool. The returnedagentInstructionis part of the repair contract.- For a
user_gatewhosegate.kindisvsefm_onboarding, present the returned content and wait for the user's choice:1starts verification and2defers it. Callloom.verifywithdecision=requiredfor1ordecision=deferredfor2. Do not wait for an external V-SEFM result; Loom resumes immediately after recording the choice. done,blocked,failed: report the returned status and stop.
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.
- 5d ago First seen · 73 lines · 25 tokens per session scan A 3fc56aa86c58
loom is a skill published in the GitHub repository valkor-ai/loom (960 stars, last pushed 19d ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,564 once invoked, about $0.0001 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-30.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…