The Context Budget Index · Stale-Reference Receipts · November 2026 · counted with ctxcap
Stale-Reference Receipts
An instruction file that names a path which no longer exists is not a style problem. It is a factual defect with a one-line fix. This page scans the context files of the most-starred repositories, reports the references that do not resolve, and states what was done about each one.
- 23repositories scanned
- 5references that did not resolve
- 2confirmed defects after reading
- 3read and excluded as examples
The scanner is deliberately conservative. It checks paths, globs, and npm run scripts named in a context file against the repository, and stays quiet when a reference could be a name, an example, or one of two alternatives. What it reports is still a candidate, not a verdict: every row below was read before it was called a defect, and receipts/reviews.json records the reading. The excluded list is published too, because a measurement that hides its false positives is not one.
Confirmed defects
| Repository and line | Reference | The line |
|---|---|---|
| twbs/bootstrapAGENTS.md:3 | CLAUDE.md |
Guidance for AI coding agents working in this repository. Tool-agnostic; `CLAUDE.md` points here. |
| avelino/awesome-goAGENTS.md:38 | .github/scripts/check-quality.js |
- The `PR Quality Checks` workflow will run `.github/scripts/check-quality.js`; ensure referenced links in PR bodies are reachable. |
Read and excluded
Found by the scanner, and not published as defects. The reason is the reading, not a rule.
- Significant-Gravitas/AutoGPT ·
usePageName.ts— This is the scaffolding template for a new feature, not a reference to a file that should be in the repository. 'Add `usePageName.ts` hook for logic' tells a generator what to create. - Significant-Gravitas/AutoGPT ·
useComponentName.ts— This is a naming pattern: ComponentName/ComponentName.tsx and useComponentName.ts show the shape of a component and its hook. The repeated placeholder is the tell. - morluto/rea ·
turbo.jsonc— The line offers a choice: put the setting in turbo.json or turbo.jsonc. turbo.json exists, so the instruction resolves. A reference that is one of two alternatives is not dead because the other alternative is the one in use.
Not scanned
Absence cannot be proved for these, so they are listed rather than guessed at.
- openclaw/openclaw — GitHub truncated the file tree, so absence cannot be proved
- torvalds/linux — GitHub truncated the file tree, so absence cannot be proved
How it was counted
- Each repository's default branch was read through the GitHub API. The file tree was laid out as empty files, the context files were written with their real contents, and
ctxcap --staleran against that copy. Nothing was cloned and nothing was written to the repository. - A reference is reported only when it is spelled like a path into the repository and the path does not resolve. Identifiers, commands that are not
npm run, routes, branches, and package names are not paths and are skipped. - An
npm runscript is judged only when everypackage.jsonin the tree was fetched; otherwise command findings are dropped rather than guessed. - Two repositories in the index are not here: GitHub truncates their file tree, so a missing path cannot be distinguished from an unlisted one.
- Data fetched 2026-11-16. Selected 25 repositories holding the files in the The Context Budget Index for 2026-11. Counted with
ctxcap, offline.
Run it on a repository
npx ctxcap --stale # every reference that does not resolve npx ctxcap --stale-fix # a deletion diff for the ones it is sure about
To send one in: open an audit issue with the repository. The series is time-boxed to ten, and the before and after are published here with the line that changed.
Data for this month: 2026-11.json. Pull request drafts: receipts/prs. Method: receipts/README.md. Something wrong with a row? Open an issue.