mini-swe-agent: Instructions file for Codex

AGENTS.md

mini-swe-agent AGENTS.md is an instructions file for Codex, OpenCode from SWE-agent/mini-swe-agent. It costs 975 tokens per session, scanned A, original, MIT.

A repository guide for SWE-agent and mini-swe-agent, tools that use AI agents to solve software-engineering tasks. It explains their structure and the project's Python style and testing conventions.

In plain words
What is it for?
Use it when editing agent control flow, environments, model interfaces, run scripts, or other Python code in these projects.
Why use it?
It gives contributors clear rules for making changes in these codebases. This reduces avoidable differences in code style, file organization, and tests.

Instructions file for CodexOpenCode

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

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

About the project

mini-swe-agent is a small AI software-engineering agent that works on GitHub issues or tasks from the command line by operating in a software environment. It is designed for coding-agent research and for developers who want a simple agent that can use different language models and execution environments. The catalogue entries provide instructions and agents for using or extending it.

SWE-agent/mini-swe-agent · 8,922 stars · on GitHub · mini-swe-agent.com

Reuse

Borrowing it

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

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 mini-swe-agent AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/swe-agent/mini-swe-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/swe-agent/mini-swe-agent/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 975 This file is loaded in full into every session.
When invoked 975 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.00975 $0.00975
Opus 5.5 $0.00390 $0.00390
Sonnet 5.5 $0.00195 $0.00195
Haiku 4.5 $0.00097 $0.00097

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

Security

Grade A, and why

mini-swe-agent 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 2mo 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.

AGENTS.md · 110 lines

How it starts

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

mini-SWE-agent overview

  • mini-SWE-agent implements an AI software engineering agent that solves github issues and similar programming challenges
  • The idea of this project is to write the simplest, smallest, most readable agent.

The project is structured as

minisweagent/__init__  # Protocols/interfaces for all base classes
minisweagent/agents  # Agent control flow & loop
minisweagent/environments  # Executing agent actions
minisweagent/models  # LM interfaces
minisweagent/run  # Run scripts that serve as an entry point
  • The project embraces polymorphism: Every individual class should be simple, but we offer alternatives
  • Every use case should start with a run script, that picks one agent, environment, and model class to run

Style guide

  1. Target python 3.10 or higher
  2. Use python with type annotations. Use list instead of List.
  3. Use pathlib instead of os.path. Use Path.read_text() over with ...open() constructs.
  4. Use typer to add interfaces
  5. Keep code comments to a minimum and only highlight particularly logically challenging things
  6. Do not append to the README unless specifically requested
  7. Use jinja for formatting templates
  8. Use dataclass for keeping track config
  9. Do not catch exceptions unless explicitly told to.
  10. Write concise, short, minimal code.
  11. In most cases, avoid initializing variables just to pass them to a function. Instead just pass the expression to the function directly.
  12. Not every exception has to be caught. Exceptions are a good way to show problems to a user.
  13. This repository rewards minimal code. Try to be as concise as possible.

Here's an example for rule 11:

# bad
a = func()
Class(a)

# good
Class(func())

Test style

  1. Use pytest, not unittest.
  2. Do not mock/patch anything that you're not explicitly asked to do
  3. Avoid writing trivial tests. Every test should test for at least one, preferably multiple points of failure
  4. Avoid splitting up code in multiple lines like this: a=func()\n assert a=b. Instead, just do assert func() == b
  5. The first argument to pytest.mark.parametrize should be a tuple (not a string! not a list!), the second argument must be a list (not a tuple!).

Read the full file on GitHub · 110 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. 2mo ago First seen · 110 lines · 975 tokens per session scan A 5cd7ba3e1eaa

Subscribe to this mod's changes

mini-swe-agent AGENTS.md is an instructions file published in the GitHub repository SWE-agent/mini-swe-agent (8,922 stars, last pushed 2d ago), licensed MIT. It adds 975 tokens to every session, about $0.0039 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,461 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

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.

deepseek-ai/deepseek-harness · 4,261 tokens