loci: Instructions file for Codex

AGENTS.md

loci AGENTS.md is an instructions file for Codex, OpenCode from thienhm/loci. It costs 627 tokens per session, scanned A, a copy of OpenAIWorkshop copilot-instructions.md, MIT.

Instructions for working on the Loci repository, including its workflow and verification rules. An AGENTS.md file is a set of guidance for coding assistants working in a project.

In plain words
What is it for?
Use it when making non-trivial changes in the Loci project. It helps decide when to plan, delegate work, update lessons, and run verification.
Why use it?
It sets expectations for planning larger tasks, using subagents, recording corrections, and checking work before declaring it finished.

Instructions file for CodexOpenCode

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

This is thienhm/loci's own configuration. It tells Codex and OpenCode how to work on loci 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 loci configures →

View source ↗ thienhm/loci
Reuse

Borrowing it

Nothing to install: this file belongs to thienhm/loci. 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/thienhm/loci/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/thienhm/loci

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 loci AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/thienhm/loci/agents-md"><img src="https://agentmods.dev/badge/instructions/thienhm/loci/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 627 This file is loaded in full into every session.
When invoked 627 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 89% copy Near-identical to another mod 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.00627 $0.00627
Opus 5.5 $0.00251 $0.00251
Sonnet 5.5 $0.00125 $0.00125
Haiku 4.5 $0.00063 $0.00063

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

Security

Grade A, and why

loci 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

This is a copy

89% identical to OpenAIWorkshop copilot-instructions.md — 122 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 72 lines

How it starts

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

Workflow Orchestration

1. Plan Node Default

  • Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
  • If something goes sideways, STOP and re-plan immediately - don't keep pushing
  • Use plan mode for verification steps, not just building
  • Write detailed specs upfront to reduce ambiguity

2. Subagent Strategy

  • Use subagents liberally to keep main context window clean
  • Offload research, exploration, and parallel analysis to subagents
  • For complex problems, throw more compute at it via subagents
  • One task per subagent for focused execution

3. Self-Improvement Loop

  • After ANY correction from the user: update tasks/lessons.md with the pattern
  • Write rules for yourself that prevent the same mistake
  • Ruthlessly iterate on these lessons until mistake rate drops
  • Review lessons at session start for relevant project

4. Verification Before Done

  • Never mark a task complete without proving it works
  • Diff behavior between main and your changes when relevant
  • Ask yourself: "Would a staff engineer approve this?"
  • Run tests, check logs, demonstrate correctness

5. Demand Elegance (Balanced)

  • For non-trivial changes: pause and ask "is there a more elegant way?"
  • If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
  • Skip this for simple, obvious fixes - don't over-engineer
  • Challenge your own work before presenting it

6. Autonomous Bug Fixing

  • When given a bug report: just fix it. Don't ask for hand-holding
  • Point at logs, errors, failing tests - then resolve them
  • Zero context switching required from the user
  • Go fix failing CI tests without being told how

Task Management

  1. Plan First: Write plan to tasks/todo.md with checkable items
  2. Verify Plan: Check in before starting implementation
  3. Track Progress: Mark items complete as you go
  4. Explain Changes: High-level summary at each step
  5. Document Results: Add review section to tasks/todo.md
  6. Capture Lessons: Update tasks/lessons.md after corrections

Read the full file on GitHub · 72 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 · 72 lines · 627 tokens per session scan A b3d3e0ecf0b7

Subscribe to this mod's changes

loci AGENTS.md is an instructions file published in the GitHub repository thienhm/loci (0 stars, last pushed 4mo ago), licensed MIT. It adds 627 tokens to every session, about $0.0025 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to OpenAIWorkshop copilot-instructions.md, differing in 122 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vibetags com-example-config-AsyncTestConfig.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.

PIsberg/vibetags · 82 tokens

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