Borrowing it
Nothing to install: this file belongs to ojamin/okf-loom. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ojamin/okf-loom/develop/AGENTS.mdgit clone --depth 1 https://github.com/ojamin/okf-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/ojamin/okf-loom/agents-md)<a href="https://agentmods.dev/instructions/ojamin/okf-loom/agents-md"><img src="https://agentmods.dev/badge/instructions/ojamin/okf-loom/agents-md/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/instructions/ojamin/okf-loom/agents-md"><img src="https://agentmods.dev/badge/instructions/ojamin/okf-loom/agents-md.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.00541 | $0.00541 |
| Opus 5.5 | $0.00216 | $0.00216 |
| Sonnet 5.5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
okf-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 1mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — okf-loom Skill
This repo is a loadable OKF skill checkout. Start with SKILL.md,
then load the focused resource file for the task you are doing.
Required orientation
- Read
SKILL.md— especially its Default behaviours: author docs as fully-dressed OKF concepts, validate after writing, serve the live studio proactively when the user wants to see or discuss docs (scripts/okf-loom serve <bundle> --no-open, add--tunnelfor a public link), and run the comment loop (wait→comment-claim→ mutators →comment-resolve) while a studio is up. - Use
scripts/okf-loom ...for runtime commands. - Use
docs-bundle/reference/spec.mdas the canonical current spec. - Do not reintroduce package publishing as the primary workflow. This git repo skill layout is the artifact.
What lives where
okf-loom/
├── SKILL.md # primary loadable skill entrypoint
├── resources/ # small agent-readable guidance files
├── scripts/okf-loom # checked-in helper command
├── scripts/okf_loom/ # checkout-local runtime package
├── docs-bundle/ # OKF docs bundle
├── samples/ # example bundles
├── tests/ # executable proofs
└── docs/ # screenshots, design plans (docs/design/)
Command baseline
scripts/okf-loom --help
scripts/okf-loom validate docs-bundle --strict
No primary runtime install step is required for normal docs validation. PyYAML is used when present; otherwise okf-loom uses its conservative built-in YAML fallback.
Hard rules
typeis the only hard-required concept frontmatter key in OKF v0.1.- Preserve unknown frontmatter keys and hand-authored content.
- Consumers tolerate broken links; mutators fail closed on missing targets
unless
--allow-forward-referenceis explicit. index.mdandlog.mdare reserved filenames.- Only the bundle-root
index.mdmay carry frontmatter. - Index regeneration must be marker-safe; log updates are append-only.
- All writes must stay atomic.
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.
- 1mo ago First seen · 56 lines · 541 tokens per session scan A 4a0f5a9e34ed
okf-loom AGENTS.md is an instructions file published in the GitHub repository ojamin/okf-loom (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 541 tokens to every session, about $0.0022 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-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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.