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/valkor-ai/loom/agents-mdgit 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/instructions/valkor-ai/loom/agents-md)<a href="https://agentmods.dev/instructions/valkor-ai/loom/agents-md"><img src="https://agentmods.dev/badge/instructions/valkor-ai/loom/agents-md.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.00736 | $0.00736 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
loom AGENTS.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 4d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/rust/: workspace crates.mcp-serverexposes tools; domain crates such asplanning,execution,deploy, andknowledgeown workflow behavior;contracts,core, andstateprovide shared protocols.src/python/algorithms/: bundled BM25, TF-IDF, tokenization, and worker code.tests/rust/andtests/python/algorithms/: integration and algorithm tests, organized by product domain.plugins/{codex,claude-code,opencode}/: agent adapters. Shared Loom and deploy guidance lives underplugins/shared/; avoid duplicating shared rules in adapter files.docs/,assets/, andscripts/: user documentation, README media, and local install helpers.
Build, Test, and Development Commands
Run commands from the repository root:
npm run rust:test
npm run python:test
cargo fmt --manifest-path src/rust/Cargo.toml --all --check
cargo build --manifest-path src/rust/Cargo.toml -p mcp-server -p setup
Use targeted Rust tests while iterating, for example:
cargo test --manifest-path src/rust/Cargo.toml -p deploy --test deploy_workflow
Refresh a local integration after runtime or plugin changes with ./install.sh --agent codex --local-build; Claude Code and OpenCode helpers are in scripts/.
Coding Style & Naming Conventions
Use Rust 2021 conventions and keep code rustfmt-clean. Name modules, functions, and files with snake_case; types and traits with UpperCamelCase; constants with SCREAMING_SNAKE_CASE. Python follows four-space indentation, snake_case, and test_*.py naming. Keep changes within existing domain boundaries and prefer structured Serde models over ad hoc JSON manipulation.
Testing Guidelines
Add focused regression coverage for behavioral changes. Rust integration tests belong in the matching tests/rust/<domain>/ suite; local unit tests may remain beside implementation code. Python tests use pytest. Run the affected package or test target first, then both product test lanes before release-impacting changes. Fixes should reproduce the prior failure.
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.
- 4d ago First seen · 54 lines · 736 tokens per session scan A 30cfbeeba5a5
loom AGENTS.md is an instructions file published in the GitHub repository valkor-ai/loom (931 stars, last pushed 17d ago), licensed Apache-2.0. It adds 736 tokens to every session, about $0.0037 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 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.