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/smallnest/autoresearch/claude-mdgit clone --depth 1 https://github.com/smallnest/autoresearchWrote 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.
[](https://agentmods.dev/instructions/smallnest/autoresearch/claude-md)<a href="https://agentmods.dev/instructions/smallnest/autoresearch/claude-md"><img src="https://agentmods.dev/badge/instructions/smallnest/autoresearch/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01729 | $0.01729 |
| Opus 5 | $0.00864 | $0.00864 |
| Sonnet 5 | $0.00346 | $0.00346 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
autoresearch CLAUDE.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 5d 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.
This is a copy
94% identical to autoresearch AGENTS.md — 7 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
autoresearch is a fully automated software development tool: given a GitHub Issue number, it implements the feature through multi-agent iterative review, then auto-creates a PR, merges it, and closes the Issue. The entire runtime is a single Bash script (run.sh).
Running
# Process Issue #N in the current directory's project
./run.sh 42
# With project path, max iterations, or continue mode
./run.sh -p /path/to/project 42 16
./run.sh -c 42 10 # Continue from last interrupted iteration
# Skip archiving of previous workflows (useful for debugging)
./run.sh --no-archive 42
There are no build/test/lint commands for autoresearch itself. Shell-based regression tests live under tests/, including:
tests/test_extract_score.shtests/test_agent_logic.shtests/test_archive.shtests/test_context_overflow.shtests/test_cleanup.sh
Architecture
Archiving Mechanism
Before a new run starts (and not in continue mode), run.sh automatically archives old workflow data:
- Scans
.autoresearch/workflows/forissue-*directories. - Moves non-current issue directories to
.autoresearch/archive/YYYY-MM-DD-issue-N/. - If the target archive directory already exists, it appends a numeric suffix (e.g.,
-1,-2).
Iteration Loop
Planning Phase: First agent reads Issue → outputs tasks.json with subtask breakdown
Iteration 1: Agent implements current subtask → tests run
Iteration 2+: Agent round-robin review + fix per subtask
→ Score >= 85? → mark subtask passed → advance to next subtask
→ Score < 85? → agent fixes based on review feedback → next iteration
→ All subtasks passed? → auto commit/PR/merge/close Issue
If planning fails (no tasks.json generated), falls back to original mode: implement entire Issue in one go.
Agent rotation (from iteration 2): (iter - 1) % N where N = number of agents.
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.
- 5d ago First seen · 149 lines · 1,729 tokens per session scan A f6cdbad425c5
autoresearch CLAUDE.md is an instructions file published in the GitHub repository smallnest/autoresearch (570 stars, last pushed 1mo ago), licensed MIT. It adds 1,729 tokens to every session, about $0.0086 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to autoresearch AGENTS.md, differing in 7 lines, and is treated as a copy.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).