skills.rest
buvis
buvisOFFICIAL
Explore all skills by this author →
WebsiteGitHub

audit-context

Analyzes Claude Code token overhead across global configs, per-project files, and memory data to classify components and generate an audit report with optimization triggers on keywords like 'audit context'.

2|Updated Dec 20, 2020
Search Tags:#optimization#audit#memory#claude-code#token-usage#context-budget#config-analysis
One-click install
npx skills add https://github.com/buvis/home --skill audit-context-buvis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-context
Source: https://github.com/buvis/home/tree/main/.claude/skills/audit-context
Command: npx skills add https://github.com/buvis/home --skill audit-context-buvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan Claude Code setup to estimate context window token overhead per component, and classify each as always-loaded, on-demand, or hidden tax, with a comprehensive optimization report.

Core Features & Use Cases

  • Quantify token usage across global config, project configs, and memory files.
  • Classify components by load behavior and surface actionable recommendations.
  • Trigger audits via keywords such as "audit context", "check token usage", "context budget", "how much context am I using", and "token overhead".

Quick Start

Run the audit-context audit to generate a token-usage report for your Claude Code setup.

Frequently Asked Questions about audit-context

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

FAQPage Schema
How do I check token usage and context budget in Claude Code?▼

To check token usage, you can trigger a context audit using keywords like "audit context" or "context budget" to estimate context window token overhead across global configs, project configs, and memory files.

What is context window token overhead and how does it affect my setup?▼

Context window token overhead is the amount of token capacity consumed by always-loaded or hidden config components. Analyzing this overhead helps classify components and optimize your available context budget.

How do I audit Claude Code memory files for token waste?▼

Auditing Claude Code memory files involves scanning global and per-project configurations to classify components as always-loaded, on-demand, or hidden tax, producing a report with actionable optimization recommendations.

Does the context audit analyze both global and per-project configs?▼

Yes, the context audit analyzes both global config and per-project configs alongside memory files to quantify token usage and surface hidden tax components that reduce your available context budget.

What is the best way to optimize token usage in Claude Code?▼

The best way to optimize token usage is to generate an audit report that classifies components by load behavior, identifying hidden taxes and always-loaded files to eliminate or restructure for context budget optimization.

Related Skills

Explore More Software Engineering Skills→
fortunto2fortunto2
18

solo-memory-audit

Audit Claude Code memory usage and generate startup context reports.

Community
Intermediate
cacheforge-aicacheforge-ai
10

context-engineer

Analyze workspace context files and generate token-usage optimization reports.

Official
Advanced
Michae2xlMichae2xl

context-budget

Audit Claude Code context window token consumption and generate prioritized savings recommendations.

Community
Advanced
aayushsoamaayushsoam
1

context-budget

Audit token overhead across Claude Code sessions and flag bloated components.

Community
Intermediate