Report · marked 25 Aug 2026

koala73/worldmonitor

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

TypeScript · 84,137 stars · 6,111 files · branch main

91 /100 A

Instructions 27/27Whether the repo tells an agent how to behave before it starts guessing. Full marks.Setup 20/20Whether an agent can install the project and get it running without a human. Full marks.Verification loop 25/25Whether 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

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 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.

✓Instruction quality 12/12

Specific enough that an agent can act on it.

11,031 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 20/20 A+

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

✓Deterministic install 6/6

package-lock.json pins the dependency tree.

Found package-lock.json

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

package.json scripts (lint, lint:fix, lint:boundaries, lint:api-contract, lint:safe-html, lint:panel-content-writes…)

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

1906 test files against 3380 source files.

e.g. api/_api-key.test.mjs, api/_cors.test.mjs, api/_rate-limit.test.mjs

✓Test command is discoverable 7/7

An agent can find and run `make test`.

✓Continuous integration 4/4

38 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

biome.json encodes the house style.

✓Static type checking 3/3

Strict type checking is on, which catches a whole class of agent mistakes before they run.

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 90 patterns.

✗File sizes fit in context 0/6

28 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.

scripts/seed-forecasts.mjs — 883KB

scripts/ais-relay.cjs — 593KB

tests/forecast-trace-export.test.mjs — 407KB

✗Repository weight 2/5

About 192MB 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 koala73/worldmonitor

# AGENTS.md

Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface

## Setup

```
npm ci
```

## Commands

```
npm run dev                 # run locally
npm run build               # produce a build
npm run typecheck           # type check without emitting
npm run lint                # lint
npm run lint:fix
npm run lint:boundaries
npm run lint:api-contract
npm run lint:safe-html
```

## Layout

- `tests/`   863 source files
- `src/`     803 source files
- `scripts/` 595 source files
- `server/`  411 source files
- `api/`     215 source files
- `convex/`  135 source files

## Conventions

- Tests live alongside the code they cover, following `api/_api-key.test.mjs`.
- TypeScript runs in strict mode. Type errors are the fastest feedback available, so do not weaken it.
- CI defines what passing means. See `.github/workflows/analytics-collector-monitor.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `scripts/seed-forecasts.mjs` is 883KB. 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/koala73/worldmonitor.md

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/koala73/worldmonitor.svg)](https://agentreadme.com/koala73/worldmonitor)

Other TypeScript repositories, marked

freeCodeCamp/freeCodeCamp 69 B openclaw/openclaw 68 B nilbuild/developer-roadmap 45 C vuejs/vue 67 B n8n-io/n8n 87 A anomalyco/opencode 80 A-

All TypeScript 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