mkcontext-audit

Solid

Read-only audit of `.claude/` structural overhead. Reports prioritized "remove X save Y tokens" recommendations against the model context window. NOT for monetary cost tracking — that's /mk:budget. NOT for transcript size monitoring — long-session continuity defers to Claude Code native compaction. NOT for runtime context decisions (what to read, when to compact) — see mk:context-engineering. Use when planning to add context capacity, diagnosing perceived slowdowns, or auditing health.

AI & Automation 15 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
40
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /mk:context-audit — Context Window Structural Audit Read-only audit of `.claude/` structural overhead. Surfaces what is loaded into every host-runtime session and how much of the context window it consumes, then recommends the highest-leverage trims. Complementary lens: `mewkit inventory --substrate` shows the same artifact set grouped by the responsibility each serves (covered / partial / missing), so a trim can be checked against responsibility coverage before removing an artifact. The per-phase read budget that bounds what an audit-driven session should load lives in `rules/context-budget-rules.md`. ## When to Use Three concrete triggers: 1. **Pre-add capacity check** — before adding a new agent, skill, or rule file, confirm the project is below the 25% structural-overhead threshold. 2. **Post-degradation diagnostic** — when sessions feel slow, off-topic, or over-compacted, audit to see if structural overhead has grown past 10%. 3. **Periodic health audit** — quarterly or on model upgrades, confirm the always-on bundle still pays its keep (paired with the dead-weight audit in `harness-rules.md` Rule 7). ## Context vs Cost (Boundary) | Concern | Mechanism | Unit | | ------------------------------- | -------------------------------------------------------- | ------------- | | Monetary cost | `/mk:budget` + `../autobuild/scripts/budget-tracker.sh` | USD ...

Details

Author
ngocsangyem
Repository
ngocsangyem/MeowKit
Created
4 months ago
Last Updated
today
Language
TypeScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

context-budget

Use when context feels heavy or you've added skills, agents, MCP servers, or memory and want a token-consumption audit of the whole setup with a prioritized trim list.

0 Updated 1 weeks ago
Endika
AI & Automation Listed

context-budget-auditor

Measures token consumption across every loadable pmo-platform component in a Claude Code / Cowork session — the SKILL.md catalog, core/rules/, core/standards/schemas/specs/disciplines, agents, hooks, and the CLAUDE.md context-file chain — and reports total + per-component estimated token cost, a flagged-bloat section with the applied thresholds stated inline, and a K1/K2 load-vs-reference hint per component. Single Measure mode. Estimates are a heuristic, trend-over-time signal (not falsely-precise absolutes), and the skill roster is sourced live, never hardcoded. Read-and-report only — measures cost, changes nothing. Triggers: "audit the context budget", "measure token consumption", "how much context does the platform load", "what's the per-component token cost", "flag context bloat", "which components are bloated", "context budget report".

0 Updated today
cody-hutson
AI & Automation Listed

rootnode-context-budget

Analyzes Claude Project context budget under the automatic-RAG-by-window model: knowledge files vs. threshold-exempt overhead (Skills, MCPs, CI, Memory). Two modes: Quick Diagnostic and Full Budget Audit. Use when user says "check my context budget," "how much context am I using," "is my project too big," "optimize my token usage," "tier my files," "optimize for RAG," "improve retrieval quality," "should I keep compressing," "am I over-compressing," "should I accept RAG mode." Also trigger on context pressure symptoms: "Claude forgets my instructions," "responses getting generic," "content not found in my knowledge files." Also use when a project audit scores Knowledge Architecture ≤ 3. Do NOT use for content placement decisions (use rootnode-memory-optimization if available), full project audits (use rootnode-project-audit if available), or behavioral tuning (use rootnode-behavioral-tuning if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

40 Updated 2 days ago
drayline