token-budget-check

Token budget validation analyzes Markdown files to compute token estimates against predefined limits. It reads frontmatter budgets and applies per-document rules to generate a report showing which files exceed their allocated token counts.

The best way to reduce token count in repository documentation is to apply content optimization suggestions. These suggestions analyze Markdown text and recommend specific reductions to trim content without losing meaning while staying under the token budget.

Frontmatter budget inference reads predefined token limits from Markdown file metadata to apply the correct restrictions. It combines these frontmatter budgets with path-based type inference to determine which per-document rules to enforce during token estimation.

Yes, you can enforce token limits on operational guides and SKILL.md files. Token budget validation applies across repository documentation assets, using path-based type inference and per-document rules to ensure these specific files adhere to predefined budgets.

A long SKILL.md file fails AI ingestion because its content exceeds the maximum token budget allowed for processing. Running a token budget check computes the token estimate against frontmatter limits and suggests optimizations to trim the file down.