Report · marked 25 Aug 2026
nicolargo/glances
Solid foundations, held back in a few specific places.
Python · 33,426 stars · 566 files · branch develop
72
/100
B+
Instructions
23/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and readme as an entry point.Setup
11/20Whether an agent can install the project and get it running without a human. Losing marks on deterministic install and environment config.Verification loop
22/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on static type checking.Context economy
10/20Whether the repo fits in a context window, or fights it. Losing marks on no committed build output and file sizes fit in context.Navigability
7/10How quickly anything new can orient itself. Losing marks on 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
Deterministic install
Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.
03
Agent instruction file
Rename or symlink to AGENTS.md so tools other than one vendor's can read it. Keeping CLAUDE.md alongside it costs nothing.
The full marking
Every deduction below names the file or setting it came from.
Instructions 23/27 A
Whether the repo tells an agent how to behave before it starts guessing.
✗Agent instruction file
9/12
CLAUDE.md is present, but not the vendor-neutral AGENTS.md.
Rename or symlink to AGENTS.md so tools other than one vendor's can read it. Keeping CLAUDE.md alongside it costs nothing.
✓Instruction quality
12/12
Specific enough that an agent can act on it.
4,924 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 11/20 B-
Whether an agent can install the project and get it running without a human.
✗Deterministic install
3/6
Only requirements.txt, which pins loosely at best.
Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
Makefile
pyproject.toml scripts
✗Environment config
2/4
Env vars are mentioned in the README but there's no example file to copy.
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
0/2
No pinned runtime version.
Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.
✗Reproducible environment
0/2
No container or devcontainer definition.
A Dockerfile or devcontainer removes an entire class of 'it won't install' failures.
Verification loop 22/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
59 test files against 279 source files.
e.g. tests/HOW_TO_TEST_MCP.md, tests/conf/glances_restful_cors.conf, tests/conf/glances_xmlrpc_allowed_hosts.conf
✓Test command is discoverable
7/7
An agent can find and run `make test`.
✓Continuous integration
4/4
10 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
pyproject.toml encodes the house style.
✗Static type checking
0/3
No static type checking.
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.
Context economy 10/20 C+
Whether the repo fits in a context window, or fights it.
✗No committed build output
3/6
Generated output is committed: __pycache__/.
Add these to .gitignore and `git rm -r --cached` them. Generated files pollute search results, so an agent grepping for a function finds the compiled copy and edits the wrong file.
✓.gitignore hygiene
3/3
.gitignore covers 48 patterns.
✗File sizes fit in context
0/6
2 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.
glances/outputs/static/public/glances.js — 670KB
glances/outputs/static/public/browser.js — 560KB
✗Repository weight
4/5
About 57.3MB 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 Glances an Eye on your system. A top/htop alternative for GNU/Linux, BSD, macOS and Windows operating systems. ## Setup ``` pip install -r requirements.txt ``` ## Commands ``` make alpine_images make ubuntu_images make help make install-uv make upgrade-uv make venv ``` ## Layout - `glances/` 203 source files - `tests/` 55 source files - `tests-data/` 13 source files - `docs/` 2 source files ## Conventions - Tests live alongside the code they cover, following `tests/HOW_TO_TEST_MCP.md`. - CI defines what passing means. See `.github/workflows/build.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `glances/outputs/static/public/glances.js` is 670KB. It will not fit comfortably in context, so read it in parts. - No lockfile is committed, so an install here may not match what CI produced. --- 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/nicolargo/glances.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/nicolargo/glances)Other Python 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.