Borrowing it
Nothing to install: this file belongs to LoomA8osAgent/a8-loom-coordinator. 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/LoomA8osAgent/a8-loom-coordinator/master/AGENTS.mdgit clone --depth 1 https://github.com/LoomA8osAgent/a8-loom-coordinatorWrote 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/looma8osagent/a8-loom-coordinator/agents-md)<a href="https://agentmods.dev/instructions/looma8osagent/a8-loom-coordinator/agents-md"><img src="https://agentmods.dev/badge/instructions/looma8osagent/a8-loom-coordinator/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.1 | $0.00885 | $0.00885 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
a8-loom-coordinator 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 6d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — a8-loom-coordinator
Cross-model agent guide (the AGENTS.md open standard — works with Codex CLI, Claude Code, Gemini CLI, Cursor, Cline, Devin, and 30+ tools). This file both governs agents working inside this repo and describes what the repo is for any agent that discovers it.
What this repo is
A config-driven governance, skills, and hooks stack for running an LLM as the autonomous senior engineer on a software project — any language, any framework, frontend or backend. The human is operator, ratifier, and spot-checker, not babysitter. Its one enforced idea: discover-then-reuse — before building anything, the agent must retrieve what the codebase already provides and reuse it, never hand-roll a fresh version. That is what makes LLM building deterministic against an existing codebase.
It is a reusable coordinator seat (the "Loom" seat) — model-portable by design,
so Opus / Sonnet / Codex / Gemini / whatever-comes-next can sit in it. This is the
first a8-loom-* project; more follow.
Install / use it in YOUR project
- Claude Code plugin:
/plugin marketplace add LoomA8osAgent/a8-loom-coordinatorthen/plugin install a8-loom-coordinator@a8-loom. - npx:
npx a8-loom-coordinator init(scaffold config) then... install(wire hooks). - Manual: clone, run
hooks/install-hooks.sh, fillstack.config.json.
Start from the example nearest your project: stack.config.example.backend.json
(Python/SQL) or stack.config.example.frontend.json (web).
If you are an agent working IN this repo
- Canon lives in
governance/(templates),hooks/(the enforcement floor),skills/(the practice),agents/(planner/builder/auditor archetypes),frontend/(opt-in CSS/DOM module).stack.config.README.mdis the annotated config schema. - Discover before you build. Grep for an existing helper/pattern before writing a
new one. Reuse or derive; never fork the vocabulary. (
HELPER-HAND-ROLL,NEW-VOCABULARY-WITHOUT-CONSENT— seegovernance/FAILURE-PATTERNS.md.) - Fix at the shared level. A behavior in ≥2 places is fixed in ONE home and the
copies deleted (
PATCH-NOT-ESCALATED-TO-SHARED). - Verify the running system, not the file on disk (
CACHE-LIE); verify the effect, not the display (VERIFY-DISPLAY-NOT-EFFECT). - Config-driven, always. Nothing in
hooks/assumes a language or framework — new behavior is a config key, not a hardcoded idiom. Keep it that way. - Syntax-check every hook edit (
node --check); validate JSON. - Never invent a language/framework assumption into the core. The CSS/DOM pieces
live only in
frontend/and run only whenfrontend.enabled.
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.
- 6d ago First seen · 63 lines · 885 tokens per session scan A aa661afa03f2
a8-loom-coordinator AGENTS.md is an instructions file published in the GitHub repository LoomA8osAgent/a8-loom-coordinator (5 stars, last pushed 1mo ago), licensed MIT. It adds 885 tokens to every session, about $0.0044 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
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.
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.
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).
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).
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.
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.