Report · marked 10 Oct 2026

esengine/DeepSeek-Reasonix

Solid foundations, held back in a few specific places.

Go · 35,753 stars · 7,270 files · branch studio

82 /100 A-

Instructions 17/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup 18/18Whether an agent can install the project and get it running without a human. Full marks.Verification loop 22/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Full marks.Context economy 13/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

Instruction quality

Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no code blocks.

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.

Repository weight

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

The full marking

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

Instructions 17/27 B

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 2/12

Present but too thin to change an agent's behavior.

Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no code blocks.

uses headings, so an agent can skim it

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 18/18 A+

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 6/6

Commands are declared where an agent will look for them.

Makefile

scripts/ directory

✓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 n/a

Not applicable — a library doesn't need a container to be worked on.

Verification loop 22/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

2819 test files against 6490 source files.

e.g. benchmarks/compaction/main_test.go, benchmarks/context-retrieval/contextbench_test.go, benchmarks/context-retrieval/main_test.go

✓Test command is discoverable 7/7

An agent can find and run `make test`.

✓Continuous integration 4/4

24 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

.golangci.yml encodes the house style.

–Static type checking n/a

Not applicable — the Go compiler type checks every build.

Context economy 13/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 66 patterns.

✗File sizes fit in context 2/6

6 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/session/control/controller_test.go — 188KB

internal/assembly/boot/boot_test.go — 144KB

internal/platform/repair/update.go — 136KB

✗Repository weight 2/5

About 183MB checked out. Large enough that cloning and searching are both slow.

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

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 esengine/DeepSeek-Reasonix

# AGENTS.md

A reliable coding agent for complex software engineering tasks.

## Setup

```
go mod download
```

## Commands

```
make build     # produce a build
make vet
make studio
make fmt
make lint      # lint
make lint-go
```

## Layout

- `internal/`   4269 source files
- `desktop/`    1006 source files
- `benchmarks/` 837 source files
- `cmd/`        107 source files
- `workers/`    87 source files
- `tools/`      65 source files

## Conventions

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

## Gotchas

- `internal/session/control/controller_test.go` is 188KB. 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/esengine/DeepSeek-Reasonix.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](https://agentreadme.com/badge/esengine/DeepSeek-Reasonix.svg)](https://agentreadme.com/esengine/DeepSeek-Reasonix)

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