Borrowing it
Nothing to install: this file belongs to anshulixyz/multi-agent-loop-kit. 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/anshulixyz/multi-agent-loop-kit/main/AGENTS.mdgit clone --depth 1 https://github.com/anshulixyz/multi-agent-loop-kitWrote 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/anshulixyz/multi-agent-loop-kit/agents-md)<a href="https://agentmods.dev/instructions/anshulixyz/multi-agent-loop-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/anshulixyz/multi-agent-loop-kit/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/anshulixyz/multi-agent-loop-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/anshulixyz/multi-agent-loop-kit/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.01558 | $0.01558 |
| Opus 5.5 | $0.00623 | $0.00623 |
| Sonnet 5.5 | $0.00312 | $0.00312 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
multi-agent-loop-kit 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Multi-Agent Ownership Registry
Setting this kit up in this repo? If you are an AI agent helping configure the kit, read
prompts/setup-interview.mdfirst — it tells you how to interview the user and fill this file in for their project. The contents below are a generic template until that interview is done.
This file is the source of truth for who can edit what.
Every coding agent must obey path ownership, journal updates, proposal rules, approval gates, and PR discipline.
Two meanings of “agent”
| Term | Meaning |
|---|---|
| Coding agent | A Cursor / Claude / Codex session with a codename, worktree, owned paths, branch prefix, and kickoff prompt |
| Runtime agent | An app-level process in your product, e.g. an agent that subscribes to events, calls APIs, or executes user workflows |
This file is about coding agents.
Core rules
- One coding agent per worktree.
- One worktree per Cursor / Claude / Codex window.
- Every path has exactly one owner.
- No coding agent commits outside owned paths.
- Cross-boundary changes require a proposal or approval request.
- Shared contracts are frozen and operator-owned.
- Agents coordinate through journals, task briefs, approvals, and proposals.
- Agents never coordinate through private chat if the information affects build state.
- All implementation work happens on
<codename>/<slug>branches. - All meaningful work ends with tests, journal update, and PR.
Project Lead / Operator
| Field | Value |
|---|---|
| Codename | operator |
| Human | Project Lead / repo owner |
| Owns | Product decisions, contracts, specs, runbook, rules, final approval |
| Branch | main unless intentionally editing |
| Commit prefix | operator: |
Project Lead / operator owns:
AGENTS.mdOPERATING_GUIDE.mdPROTOCOL.mdRUNBOOK.mdLOOP_RADAR.mdfinal objectiveLOOP_MEMORY.mdfinal decisions- shared contracts/types/schemas
.cursor/rules/**agents-status/proposals/**decisionsagents-status/approvals/**decisions
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 · 244 lines · 1,558 tokens per session scan A 6498fc2a580c
multi-agent-loop-kit AGENTS.md is an instructions file published in the GitHub repository anshulixyz/multi-agent-loop-kit (5 stars, last pushed 4mo ago), licensed MIT. It adds 1,558 tokens to every session, about $0.0062 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.