Report · marked 25 Aug 2026
dotnet/aspnetcore
Solid foundations, held back in a few specific places.
C# · 38,393 stars · 17,547 files · branch main
76
/100
B+
Instructions
16/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and instruction quality.Setup
16/16Whether 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
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
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
Instruction quality
Worth fixing: it never states a build, test, or run command; has no code blocks.
03
Agent instruction file
Rename or symlink to AGENTS.md so tools other than one vendor's can read it. Keeping Copilot instructions alongside it costs nothing.
The full marking
Every deduction below names the file or setting it came from.
Instructions 16/27 B-
Whether the repo tells an agent how to behave before it starts guessing.
✗Agent instruction file
8/12
Copilot instructions 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 Copilot instructions alongside it costs nothing.
✗Instruction quality
6/12
Real instructions, with gaps.
Worth fixing: it never states a build, test, or run command; has no code blocks.
5,035 characters, a workable length
uses headings, so an agent can skim it
✗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 16/16 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 (build, lint, test, integration-test, coverage, get-version)
–Environment config
n/a
Not applicable — this reads as a library, with no environment to configure.
✓Pinned runtime version
2/2
The language runtime version is pinned.
package.json engines.node >=20.9.0
✓Reproducible environment
2/2
.devcontainer/devcontainer.json 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
5958 test files against 11405 source files.
e.g. eng/common/native/install-cmake-test.sh, src/Analyzers/Analyzers/test/CompilationFeatureDetectorTest.cs, src/Analyzers/Analyzers/test/ConfigureMethodVisitorTest.cs
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
21 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 C# 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 47 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.
src/Http/Routing/test/testassets/RoutingSandbox/wwwroot/full.render.js — 1933KB
src/Components/benchmarkapps/Wasm.Performance/TestApp/wwwroot/benchmarks/jsonHandlingData.js — 725KB
src/Components/test/E2ETest/Tests/VirtualizationTest.cs — 292KB
✗Repository weight
2/5
About 393MB 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 ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux. ## Setup ``` npm ci ``` ## Commands ``` npm run build # produce a build npm run test # run the test suite, must pass before any commit npm run lint # lint npm run integration-test npm run coverage npm run get-version ``` ## Layout - `src/` 11348 source files - `eng/` 52 source files ## Conventions - Tests live alongside the code they cover, following `eng/common/native/install-cmake-test.sh`. - CI defines what passing means. See `.github/workflows/backport.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `src/Http/Routing/test/testassets/RoutingSandbox/wwwroot/full.render.js` is 1933KB. 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/dotnet/aspnetcore.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/dotnet/aspnetcore)Other C# 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.