Report · marked 25 Aug 2026
milvus-io/milvus
Solid foundations, held back in a few specific places.
Go · 45,787 stars · 5,766 files · branch master
75
/100
B+
Instructions
15/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
16/20Whether an agent can install the project and get it running without a human. Losing marks on environment config.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
11/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
01
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 headings to structure it; has no code blocks.
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
Environment config
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
The full marking
Every deduction below names the file or setting it came from.
Instructions 15/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
0/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 headings to structure it; has no code blocks.
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 16/20 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
0/4
Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
✓Pinned runtime version
2/2
The language runtime version is pinned.
go.mod declares a Go version
✓Reproducible environment
2/2
.devcontainer.json gives a known-good environment.
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
2055 test files against 4927 source files.
e.g. build/ci/jenkins/pod/chaos-test.yaml, build/ci/jenkins/pod/scale-test.yaml, client/bulkwriter/bulk_import_test.go
✓Test command is discoverable
7/7
An agent can find and run `pytest`.
✓Continuous integration
4/4
21 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 11/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 87 patterns.
✗File sizes fit in context
0/6
122 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/http/webui/assets/index-nmS7rbPW.js — 915KB
tests/python_client/milvus_client/test_milvus_client_struct_array_nullable.py — 549KB
internal/mocks/mock_mixcoord_client.go — 487KB
✗Repository weight
2/5
About 326MB 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 Milvus is a high-performance, cloud-native vector database built for scalable vector ANN search ## Setup ``` go mod download ``` ## Commands ``` make milvus make build-go make milvus-gpu make get-build-deps make getdeps make get-proto-deps ``` ## Layout - `internal/` 3355 source files - `pkg/` 700 source files - `tests/` 520 source files - `client/` 197 source files - `cmd/` 82 source files - `scripts/` 35 source files ## Conventions - Tests live alongside the code they cover, following `build/ci/jenkins/pod/chaos-test.yaml`. - CI defines what passing means. See `.github/workflows/all-contributors.yaml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - Generated output is committed (`build/`). Search will return the compiled copy, so edit the source, not that. - `internal/http/webui/assets/index-nmS7rbPW.js` is 915KB. It will not fit comfortably in context, so read it in parts. --- 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/milvus-io/milvus.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/milvus-io/milvus)Other Go repositories, marked
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.