count-registry

To keep repository entity counts accurate, reference an authoritative manifest instead of hard-coding values. This prevents documentation drift by reading source files to preserve correct counts for agents, skills, instructions, and validators.

Documentation drift occurs when repository statistics become outdated as code changes. Using a canonical manifest file as the source of truth prevents drift by providing authoritative entity counts for generated artifacts and content workflows.

You can reference repository statistics without hard-coding numbers by using descriptive phrasing when exact counts are unnecessary. When exact numbers are required, apply source attribution from the canonical manifest file.

Yes, you need a count-manifest.json file located in the .github directory. This manifest serves as the required source of truth for reading and preserving source-attributed counts for agents, skills, instructions, and validators.

The best way to update repo docs with accurate entity counts is to query the canonical manifest file. This ensures your documentation wording avoids manually guessing or embedding outdated numbers during content generation workflows.