Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/cosmix/loomnpx agentmods add skills/cosmix/loom/loom-usageWrote 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/cosmix/loom/loom-usage)<a href="https://agentmods.dev/skills/cosmix/loom/loom-usage"><img src="https://agentmods.dev/badge/skills/cosmix/loom/loom-usage/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/cosmix/loom/loom-usage"><img src="https://agentmods.dev/badge/skills/cosmix/loom/loom-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 426 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
- high Tool Misuse · line 655 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00015 | $0.06050 |
| Opus 5.5 | $0.00006 | $0.02420 |
| Sonnet 5.5 | $0.00003 | $0.01210 |
| Haiku 4.5 | $0.00002 | $0.00605 |
Grade A, and why
loom-usage 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 yesterday.
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 — 749 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loom Usage — Meta-Orchestration for Claude
Overview
This skill enables Claude to drive loom itself — initializing plans, running orchestration, monitoring execution, debugging failures, and recovering from errors. This is meta-orchestration: Claude operating loom as a tool rather than working inside a loom worktree as an agent.
When to Use
- Running a loom plan end-to-end
- Interpreting
loom statusoutput and deciding next steps - Debugging why a stage failed, is blocked, or has merge conflicts
- Recovering from crashes, context exhaustion, or corrupted state
- Managing worktrees, sessions, and daemon lifecycle
- Understanding
.loom/work/directory structure and signal files
Complementary Skills
| Skill | Use For |
|---|---|
/loom-plan-writer |
Creating new plan files |
/loom-wiring-test |
Designing wiring verification YAML |
/loom-before-after |
Before/after delta-proof verification pairs |
/loom-dead-code-check |
Dead code detection configuration |
| This skill | Everything after the plan is written |
The Loom Lifecycle
WRITE PLAN VALIDATE & INIT EXECUTE MONITOR & DEBUG
─────────────────── ─────────────────────── ────────────────── ──────────────────
/loom-plan-writer → loom init plan.md → loom run → loom status
loom repair --fix loom check
loom stage retry
────────────────── ──────────────────
COMPLETE CLEAN UP
────────────────── ──────────────────
All stages merged → loom clean
Plan → DONE-PLAN-*
Phase 1: Validate & Initialize
Pre-Flight Checks
Before initializing, verify the workspace is healthy:
# Detect and fix common issues (missing hooks, stale state, gitignore gaps)
loom repair --fix
# If re-running a plan, clean previous state first
loom clean --all
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.
- yesterday Changed · +10 lines bb5a4aea6b84
- 22d ago Changed · +4 lines fac11ce4f050
- 1mo ago Changed · -5 lines 74144f004336
- 1mo ago First seen · 740 lines · 15 tokens per session scan A e0c3eb56d682
loom-usage is a skill published in the GitHub repository cosmix/loom (63 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 6,050 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
nx-monorepo
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx.
turborepo-monorepo
Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…
capgo-organization-management
Guides Capgo account lookup and organization administration with the CLI, including account whoami, organization list/add/members/set/delete, 2FA enforcement, password policy, API-key expiration and hashed-key policy, and apps per organization. Use when listing or creating Capgo organizations, auditing members' 2FA…
curate-collection
Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use…
design-on-call-rotation
Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or…
design-training-program
Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training…