Report · marked 26 Aug 2026
multica-ai/multica
Ready for an agent to work in without hand-holding.
Go · 47,673 stars · 5,313 files · branch main
85
/100
A
Instructions
26/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on readme as an entry point.Setup
20/20Whether an agent can install the project and get it running without a human. Full marks.Verification loop
19/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules.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
6/10How quickly anything new can orient itself. Losing marks on repository description and license.
Higher is better. Accent marks what is costing you most.
Fix these first
01
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.
02
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.
03
License
Without a license nobody can safely reuse this, and some tools will refuse to work with it at all.
The full marking
Every deduction below names the file or setting it came from.
Instructions 26/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.
2,765 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
2/3
README exists but never explains how to get the thing running.
Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.
Setup 20/20 A+
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
pnpm-lock.yaml pins the dependency tree.
Found pnpm-lock.yaml
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (dev:web, dev:docs, dev:desktop, dev:desktop:staging, dev:mobile, dev:mobile:staging…)
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.
Found .nvmrc
✓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
1547 test files against 3827 source files.
e.g. apps/desktop/scripts/package.test.mjs, apps/desktop/scripts/worktree-dev-env.test.mjs, apps/desktop/src/main/auth-session-coordinator.test.ts
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
4 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 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 44 patterns.
✗File sizes fit in context
0/6
30 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.
server/internal/daemon/daemon.go — 383KB
server/internal/service/task.go — 314KB
server/pkg/db/generated/agent.sql.go — 314KB
✗Repository weight
4/5
About 128.5MB 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 Make humans and AI agents work as one team — open-source and self-hostable. ## Setup ``` pnpm install ``` ## Commands ``` pnpm build # produce a build pnpm test # run the test suite, must pass before any commit pnpm typecheck # type check without emitting pnpm lint # lint pnpm dev:web pnpm dev:docs pnpm dev:desktop pnpm dev:desktop:staging ``` ## Layout - `server/` 1598 source files - `packages/` 1572 source files - `apps/` 603 source files - `scripts/` 24 source files - `e2e/` 18 source files - `examples/` 9 source files ## Conventions - Tests live alongside the code they cover, following `apps/desktop/scripts/package.test.mjs`. - 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 - `server/internal/daemon/daemon.go` is 383KB. 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/multica-ai/multica.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/multica-ai/multica)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.