token-threshold-warn

Monitor repository document weight by measuring line counts and byte sizes of TASKS.md, HANDOFF.md, and MEMORY.md at session start to emit advisory warnings when thresholds are exceeded.

Session guidance degrades when oversized context documents exceed fixed line and byte thresholds, causing the token-threshold-warn check to emit advisory warnings about increased document weight.

Yes, you can check file sizes and line counts without blocking your session because the monitoring process deterministically measures documents against fixed thresholds and outputs non-blocking advisory warnings.

Set up pre-session document weight alerts by running a check at session start that measures TASKS.md, HANDOFF.md, and MEMORY.md against fixed thresholds, generating advisory warnings for oversized files.

Yes, document weight monitoring works with memory index files and individual memory entries by aggregating file counts and measuring them against fixed thresholds to manage and output advisory warnings.

Avoid relying solely on fixed thresholds for repository document monitoring when your workflow requires dynamic context adaptation, as these checks output non-blocking advisory warnings rather than enforcing session blocks.