loop: Instructions file for Codex

AGENTS.md

loop AGENTS.md is an instructions file for Codex, OpenCode from axeldelafosse/loop. It costs 665 tokens per session, scanned A, original, MIT.

A set of instructions for developing Loop, a command-line tool that coordinates Claude and Codex coding sessions.

In plain words
What is it for?
Use it when changing Loop’s planning, execution, dashboard, tmux, worktree, resume, testing, build, or release behavior.
Why use it?
It records the commands and workflows needed to preserve interactive runs, saved session state, dashboards, terminal workspaces, and separate working folders.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex.

This is axeldelafosse/loop's own configuration. It tells Codex and OpenCode how to work on loop itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything loop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to axeldelafosse/loop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/axeldelafosse/loop/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/axeldelafosse/loop

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for loop AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/axeldelafosse/loop/agents-md/github.svg)](https://agentmods.dev/instructions/axeldelafosse/loop/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/axeldelafosse/loop/agents-md"><img src="https://agentmods.dev/badge/instructions/axeldelafosse/loop/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.

agentmods 80×15 button for loop AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/axeldelafosse/loop/agents-md"><img src="https://agentmods.dev/badge/instructions/axeldelafosse/loop/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 665 This file is loaded in full into every session.
When invoked 665 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00665 $0.00665
Opus 5.5 $0.00266 $0.00266
Sonnet 5.5 $0.00133 $0.00133
Haiku 4.5 $0.00067 $0.00067

Measured 1mo ago against content hash d3ac41c45b52, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loop 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Please keep the code dead-simple and keep the src/loop/main.ts file under 150 lines of code.

Quick Commands

  • Format code: bun run fix
  • Check lint/types/style: bun run check
  • Run tests: bun test
  • Build executable: bun run build
  • Install global binary/aliases: bun run install:global
  • Cut a patch release: bun run release:patch

Repo Workflows

  • Plain-text prompts auto-create PLAN.md first, then optionally run --review-plan; if you are changing planning behavior, keep that flow aligned.
  • Default CLI behavior is paired Claude/Codex execution with persisted run state under ~/.loop/runs; preserve --run-id / --session resume behavior when changing startup, planning, or loop flow.
  • Running loop with no args starts the paired interactive tmux workspace (--tmux); loop dashboard opens the live panel for active sessions, loop-owned paired runs, and tmux sessions. Keep panel-only changes separate from task-running changes when possible.
  • --tmux and --worktree are first-class execution modes. In paired mode, tmux opens Claude/Codex side-by-side and resumed run ids should stay aligned with matching tmux/worktree names.
  • --claude-only and --codex-only switch out of the default paired flow; keep single-agent behavior working when changing shared CLI parsing or resume logic.
  • loop update / loop upgrade are supported manual update commands for installed binaries; source runs should continue to rely on git pull.
  • When options are provided without a prompt, loop reuses PLAN.md if it already exists; keep that fallback aligned with the plain-text prompt planning flow.

Coding Standards

  • Keep functions small and easy to read.
  • Use explicit parameter/return types when they improve clarity.
  • Prefer unknown over any for unknown values.
  • Use const by default, let only when reassignment is needed.
  • Prefer for...of, optional chaining, nullish coalescing, and template literals.
  • Use early returns to reduce nesting.
  • Use async/await instead of promise chains.
  • Throw Error objects with clear messages.
  • Extract magic numbers/strings into named constants when reused.

Read the full file on GitHub · 53 lines

Changes

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.

  1. 1mo ago First seen · 53 lines · 665 tokens per session scan A d3ac41c45b52

Subscribe to this mod's changes

loop AGENTS.md is an instructions file published in the GitHub repository axeldelafosse/loop (283 stars, last pushed 6mo ago), licensed MIT. It adds 665 tokens to every session, about $0.0027 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-30.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens