context-verify

Detect stale paths and context drift in AGENTS.md by running a context verification audit that checks line budgets, import targets, and MEMORY drift to ensure your AI context remains accurate and efficient for agent execution.

Check Claude Code plugin manifest completeness and hook status by executing a cross-tool layout verification audit, which validates hook presence, plugin manifests, and rule scopes to prevent silent context decay during agent workflows.

Yes, you can use context verification to gate CI pipelines by evaluating per-tool aggregate token load against enforced budgets, generating a 0–100 health score with CI-friendly exit behavior to catch context bloat before it costs tokens.

The best way to audit AGENTS-to-bridge consistency across Cursor, Cline, and Copilot is to perform a 16-point context validation that checks cross-tool layout expectations, rule scopes, and discoverable content to ensure reliable multi-tool agent execution.

AI agent execution fails when context files grow large because token bloat and stale paths degrade context health, requiring a validation audit to enforce line budgets, detect outdated import targets, and score overall context efficiency.