autoforge AGENTS.md

Repository instructions for Autoforge, an autonomous software-development framework with command-line tools for searching, viewing, editing, running commands, and analyzing issues.

In plain words
What is it for?
Localizing issue descriptions, searching and viewing files, editing Python code, listing directories, running tests or commands, and analyzing repositories.
Why use it?
They define the project's supported commands and a repeatable workflow for locating problems, changing code, and validating Python syntax.

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/shigel/autoforge/agents-md
Clone the repo
git clone --depth 1 https://github.com/shigel/autoforge

Made for: Codex, OpenCode.

Per session 534 This file is loaded in full into every session.
When invoked 534 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.00534 $0.00534
Opus 5 $0.00267 $0.00267
Sonnet 5 $0.00107 $0.00107
Haiku 4.5 $0.00053 $0.00053

Measured yesterday against content hash fedbe5e9dc7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

autoforge 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 · 61 lines

What it actually says

autoforge — Agent Instructions

This file provides instructions for AI coding agents (Codex CLI, Claude Code, etc.) working on this repository.

Overview

autoforge is an autonomous SDLC framework. You have access to harness tools via bash commands.

Available Tools

# Search codebase for patterns
PYTHONPATH=. python3 -m autoforge.harness.tools search "pattern" --dir autoforge/

# View file with line numbers
PYTHONPATH=. python3 -m autoforge.harness.tools view path/to/file.py --start 1 --end 50

# Edit file (with Python syntax validation)
PYTHONPATH=. python3 -m autoforge.harness.tools edit path/to/file.py --old "old code" --new "new code"

# Run shell command
PYTHONPATH=. python3 -m autoforge.harness.tools run-cmd "pytest tests/ -v"

# List directory
PYTHONPATH=. python3 -m autoforge.harness.tools list-dir autoforge/agents

# Extract search patterns from issue text
PYTHONPATH=. python3 -m autoforge.harness.tools localize --issue "bug description"

# Analyze a repository and propose goals
PYTHONPATH=. python3 -m autoforge.harness.init --dir /path/to/repo

Issue Resolution Workflow

  1. Read the issue description
  2. localize --issue "..." to extract search patterns
  3. search "pattern" to find relevant files
  4. view path/to/file.py to read the code
  5. edit path/to/file.py --old "..." --new "..." to fix the bug
  6. run-cmd "pytest tests/" to verify the fix

Development Rules

  • Python 3.11+, Pydantic v2, httpx
  • Immutable data (frozen dataclass / Pydantic model)
  • Files under 400 lines
  • Run tests: PYTHONPATH=. python3 -m pytest tests/ -v

Project Structure

autoforge/
├── agents/      # 7 SDLC agents + resolver stack
├── core/        # PipelineRunner, LLMClient, Config, Memory, Hooks
├── schemas/     # Pydantic schemas for structured artifact passing
├── tools/       # ACI toolkit, arXiv/GitHub API clients
├── harness/     # Agent harness mode (init, tools, solve)
└── bench/       # SWE-bench evaluation pipeline
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 · 61 lines · 534 tokens per session scan A fedbe5e9dc7f

Subscribe to this mod's changes

autoforge AGENTS.md is an instructions file published in the GitHub repository shigel/autoforge (5 stars, last pushed 4mo ago), licensed MIT. It adds 534 tokens to every session, about $0.0027 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-31.