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 instructions/subotic/loom/claude-mdgit clone --depth 1 https://github.com/subotic/loomWhat 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.00376 | $0.00376 |
| Opus 5 | $0.00188 | $0.00188 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
loom CLAUDE.md 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 2d 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.
What it actually says
LOOM
Rust CLI/TUI for multi-repo workspace orchestration with git worktrees.
See docs/USER-GUIDE.md for the full user guide.
Commit Conventions
This is critical. release-plz parses commit messages on main to generate changelogs and determine version bumps. Malformed commits produce broken changelogs or missed releases.
This repo uses rebase merges only — every commit lands on main as-is.
- One topic per commit. Each commit is a single, self-contained logical change.
- Conventional Commits with scopes (e.g.,
feat(config):,fix(git):). Scopes match crate modules. - First line is the changelog entry — write it for humans. release-plz uses it verbatim.
- Breaking changes: add
!after the type and include aBREAKING CHANGE:footer. - Type determines version bump:
fix:→ patch,feat:→ minor,!/BREAKING CHANGE:→ major. - Non-release types (
docs:,test:,ci:,chore:,refactor:,style:,build:) do not trigger a release on their own.
Full details: docs/commit-conventions.md
Before Pushing
Run these checks before every push. Do not push if any fail.
cargo fmt --all -- --check
cargo clippy --workspace -- -D warnings
cargo test --workspace
Review Context
See REVIEW.md for the review checklist and CONVENTIONS.md for architectural conventions.
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.
- 2d ago First seen · 35 lines · 376 tokens per session scan A e7e909a3690e
loom CLAUDE.md is an instructions file published in the GitHub repository subotic/loom (5 stars, last pushed 5mo ago), licensed MIT. It adds 376 tokens to every session, about $0.0019 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.