context-verify

Validate AI context files for accuracy, consistency, and token budgets.

5|1|Updated Mar 10, 2026

Search Tags:#Claude Code hooks #token budget #context verification #AGENTS.md consistency #stale path detection #CI health scoring #tool bridge audit

Ready to run

npx skills add https://github.com/littlebearapps/contextdocs --skill context-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-verify
Source: https://github.com/littlebearapps/contextdocs/tree/main/.claude/skills/context-verify
Command: npx skills add https://github.com/littlebearapps/contextdocs --skill context-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents AI context files from silently decaying over time by validating that your generated Markdown stays lean, consistent, and accurate enough to use confidently.

Core Features & Use Cases

16-point context validation: checks line budgets, discoverable content, stale paths, AGENTS-to-bridge consistency, MEMORY drift, hook status, context load, imports, rule scopes, and more.
Quality scoring for safe change management: produces a 0–100 health score with CI-friendly exit behavior to catch drift before it costs tokens.
Cross-tool layout verification: audits Claude Code plugin layouts plus modern Cursor, Cline, and Copilot bridging expectations.

Quick Start

Ask the AI to run context-verify to validate your context files and return a per-tool health grade plus a prioritized fix list.

Frequently Asked Questions about context-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect stale paths and context drift in AGENTS.md files?▼

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.

How do I check Claude Code plugin manifest completeness and hook status?▼

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.

Can I use context verification to gate CI pipelines based on token budget and context load?▼

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.

What is the best way to audit AGENTS-to-bridge consistency across Cursor, Cline, and Copilot?▼

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.

Why does my AI agent fail to execute reliably when context files grow large?▼

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.