context-audit

Audits always-loaded context files for redundancy, contradictions, and token waste.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill context-audit-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-audit
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/context-audit
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill context-audit-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Always-loaded files like CLAUDE.md, AGENTS.md, MEMORY.md, and bootstrap-rendered identity files grow over time, taxing every turn with extra tokens, latency, and contradictory instructions. This Skill measures the whole stack, finds redundancy and stale content, and produces a ranked action list sorted by token savings. ## Core Features & Use Cases - Token-hygiene audit: Measures each always-loaded file with a deterministic pre-pass (chars/4 approximation) and computes drift since the last audit. - Risk-classified findings: Every finding is labeled zero, low, or medium risk with quoted evidence and the exact location where the fix belongs. - Rendered-file safety: Recommendations for bootstrap-rendered files (SOUL.md, USER.md, ACCESS_POLICY.md, HEARTBEAT.md) target the interview answer bank or templates, never the rendered output. - Use Case: Your CLAUDE.md has grown to thousands of tokens and restates rules already in SOUL.md. Run the audit to get a ranked table of what to cut, compress, or extract into an on-demand skill, with an estimated token saving per row. ## Quick Start Ask the agent to run a context audit on your always-loaded files and rank the findings by token savings.

Frequently Asked Questions about context-audit

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

FAQPage Schema
How do I reduce the token size of my CLAUDE.md and system prompt files?

Run a context audit to measure every always-loaded file, then apply the ranked recommendations: delete exact redundancies, compress verbose instructions, and extract workflow-specific content into on-demand skills. The audit reports estimated token savings per finding.

How do I find contradictions across my agent's instruction files?

The audit reads the full always-loaded stack and flags conflicting rules, numbers, or policies across files with quoted evidence from each side. Contradictions are called out first in the report since they cost correctness, not just tokens.

Does the context audit edit my files automatically?

No, the audit is strictly report-only and never edits any audited file, including zero-risk deletions. It produces a recommendation list that you or a separate skill apply deliberately.

Can I edit SOUL.md or USER.md directly to fix audit findings?

No, those files are bootstrap-rendered and direct edits are overwritten by the next render. Recommendations target the interview answer bank or templates, followed by a re-render of the affected file.

What is the difference between context-audit and soul-audit?

context-audit handles token and structure hygiene: what the stack costs per turn and where files repeat or contradict each other. soul-audit handles identity content: what SOUL.md or USER.md should say, sourced from the user's interview answers.

How much does the audit's quality judging step cost?

The default judging pass uses a single cheap utility-tier model for one cycle, costing a few cents. A full multi-model panel across three providers runs only when you explicitly request a full or multi-model audit.