agentreadme

Report · marked 9 Oct 2026

router-for-me/CLIProxyAPI

Ready for an agent to work in without hand-holding.

Go · 54,644 stars · 1,898 files · branch main

Fix these first

01
Discoverable commands
Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.
02
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
03
Lint and format rules
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

The full marking

Every deduction below names the file or setting it came from.

Instructions 27/27 A+

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12
AGENTS.md is present, which is the format the most tools read.
Also found: CLAUDE.md
✓Instruction quality 12/12
Specific enough that an agent can act on it.
5,951 characters, a workable length
names the actual commands to run
uses headings, so an agent can skim it
includes copyable code blocks
✓README as an entry point 3/3
README has a clear getting-started section.
Setup 14/20 B+

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6
go.sum pins the dependency tree.
Found go.sum
✗Discoverable commands 0/6
No declared commands. An agent has to infer how to build and run this from the file tree.
Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.
✓Environment config 4/4
.env.example documents what the app needs to run.
✓Pinned runtime version 2/2
The language runtime version is pinned.
go.mod declares a Go version
✓Reproducible environment 2/2
dockerfile gives a known-good environment.
Verification loop 19/22 A

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8
931 test files against 1739 source files.
e.g. cmd/fetch_antigravity_models/main_test.go, cmd/fetch_codex_models/main_test.go, cmd/fetch_devin_models/main_test.go
✓Test command is discoverable 7/7
An agent can find and run `go test ./...`.
✓Continuous integration 4/4
6 GitHub Actions workflows define what "passing" means.
✗Lint and format rules 0/3
No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
–Static type checking n/a
Not applicable — the Go compiler type checks every build.
Context economy 14/20 B+

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6
No generated directories committed.
✓.gitignore hygiene 3/3
.gitignore covers 47 patterns.
✗File sizes fit in context 0/6
17 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
internal/runtime/executor/claude_executor_test.go — 387KB
internal/runtime/executor/xai_executor_test.go — 317KB
sdk/api/handlers/openai/openai_responses_websocket_test.go — 314KB
✓Repository weight 5/5
About 42.8MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for router-for-me/CLIProxyAPI
# AGENTS.md

Wrap Antigravity, ChatGPT Codex, Claude Code, Grok Build, Muse Code, Devin as an OpenAI/Gemini/Claude/Codex compatible API service, allowing you to enjoy the free Gemini Series, GPT Series, Grok Series, Claude model through API

## Setup

```
go mod download
```

## Commands

```
go test ./...   # run the test suite
```

## Layout

- `internal/` 1252 source files
- `sdk/`      389 source files
- `examples/` 78 source files
- `cmd/`      9 source files
- `test/`     9 source files

## Conventions

- Tests live alongside the code they cover, following `cmd/fetch_antigravity_models/main_test.go`.
- CI defines what passing means. See `.github/workflows/agents-md-guard.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `internal/runtime/executor/claude_executor_test.go` is 387KB. It will not fit comfortably in context, so read it in parts.
- Copy `.env.example` before running anything that needs configuration.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown  or  curl -o AGENTS.md agentreadme.com/draft/router-for-me/CLIProxyAPI.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good Go AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

agent ready 85 out of 100

[![agent ready](https://agentreadme.com/badge/router-for-me/CLIProxyAPI.svg)](https://agentreadme.com/router-for-me/CLIProxyAPI)

Other Go repositories, marked

avelino/awesome-go 78 A- ollama/ollama 88 A golang/go 31 D kubernetes/kubernetes 74 B+ microsoft/TypeScript 82 A- JuliusBrussee/caveman 81 A-

All Go repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in