mini-swe-agent AGENTS.md

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

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/swe-agent/mini-swe-agent/agents-md
Clone the repo
git clone --depth 1 https://github.com/SWE-agent/mini-swe-agent

Made for: Codex, OpenCode.

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. Scan, not verified.
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 $0.00975 $0.00975
Opus 5 $0.00487 $0.00487
Sonnet 5 $0.00195 $0.00195
Haiku 4.5 $0.00097 $0.00097

Measured yesterday against content hash 5cd7ba3e1eaa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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. yesterday 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 (6,860 stars, last pushed 7d ago), licensed MIT. It adds 975 tokens to every session, about $0.0049 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-30.