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.
npx agentmods add instructions/swe-agent/mini-swe-agent/agents-mdgit clone --depth 1 https://github.com/SWE-agent/mini-swe-agentWhat 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 | $0.00975 | $0.00975 |
| Opus 5 | $0.00487 | $0.00487 |
| Sonnet 5 | $0.00195 | $0.00195 |
| Haiku 4.5 | $0.00097 | $0.00097 |
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.
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
- Target python 3.10 or higher
- Use python with type annotations. Use
listinstead ofList. - Use
pathlibinstead ofos.path. UsePath.read_text()overwith ...open()constructs. - Use
typerto add interfaces - Keep code comments to a minimum and only highlight particularly logically challenging things
- Do not append to the README unless specifically requested
- Use
jinjafor formatting templates - Use
dataclassfor keeping track config - Do not catch exceptions unless explicitly told to.
- Write concise, short, minimal code.
- In most cases, avoid initializing variables just to pass them to a function. Instead just pass the expression to the function directly.
- Not every exception has to be caught. Exceptions are a good way to show problems to a user.
- 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
- Use
pytest, notunittest. - Do not mock/patch anything that you're not explicitly asked to do
- Avoid writing trivial tests. Every test should test for at least one, preferably multiple points of failure
- Avoid splitting up code in multiple lines like this:
a=func()\n assert a=b. Instead, just doassert func() == b - The first argument to
pytest.mark.parametrizeshould be a tuple (not a string! not a list!), the second argument must be a list (not a tuple!).
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.
- yesterday First seen · 110 lines · 975 tokens per session scan A 5cd7ba3e1eaa
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.
Other instructions, from other repositories
openagent CLAUDE.md
Claude Code instructions for the-open-agent/openagent, covering claude.md, commands, architecture, backend (go / beego) and frontend (react).
Octop AGENTS.md
Instructions for TencentCloud/Octop, covering agents.md, 1. collaboration principles, think before writing, simplicity first and surgical edits.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
relay AGENTS.md
Instructions for AgentWorkforce/relay, covering git workflow rules, never push directly to main, correct workflow, ... do work .. and stop here - let user merge.
hands-on-modern-rl AGENTS.md
AGENTS.md instructions for walkinglabs/hands-on-modern-rl, covering repository guidelines, project structure, commands, editing rules and tikz → svg workflow.
neeko AGENTS.md
Instructions for tincopper/neeko, covering neeko — repository guidelines, 项目概览, 目录结构, 前端(feature-based 架构) and 后端(domain-driven 模块化架构).