claude-token-decrease

Audits and enforces Claude Code token reduction standards across rules, skills, and prompt layers.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill claude-token-decrease-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-token-decrease
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/claude-token-decrease
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill claude-token-decrease-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Claude Code sessions accumulate silent token bloat from proliferating rules files, skill descriptions, and always-on context layers, inflating costs and degrading prompt cache efficiency without any systematic way to audit or control it. ## Core Features & Use Cases - Eleven-Category Reduction Framework (A~K): Binding standards covering session static tax, workflow compression, memory DB strategy, RAG pre-injection, pipeline orchestration, and skill DMI policies. - Budget Ceilings & Regression Monitoring: Enforces a 6,000-token always-on ceiling with an audit checklist, anti-pattern catalog, and regression actions when limits are exceeded. - Prompt Caching Economics & Decision Tree: Codifies cache write/read cost rules and provides a decision tree for routing new content to rules, skills, or the memory DB. - Use Case: When your project's always-on context grows from 4,910 to 19,090 tokens after adding rules and skills, run the audit mode to identify overlapping rule files, skills missing DMI flags, and merge candidates with quantified savings. ## Quick Start Ask the AI to run a token budget audit of the current Claude Code configuration using the claude-token-decrease checklist and report which rules and skills exceed the ceilings.

Frequently Asked Questions about claude-token-decrease

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

FAQPage Schema
How do I reduce Claude Code token usage per session?

Audit the five always-on layers: global CLAUDE.md, project CLAUDE.md plus rules, skill descriptions, CLAUDE.local.md, and MEMORY.md. Merge overlapping rule files, set disable-model-invocation on user-invoked-only skills, and enforce a 6,000-token ceiling.

What is the DMI policy for Claude Code skills?

DMI (Disable Model Invocation) removes a skill's description from always-on context, reducing its cost to zero. Apply it only to explicitly user-invoked skills like /start-servers; skills that should auto-load via description matching must not set DMI.

How does prompt caching affect Claude token costs?

Cache writes cost 1.25x while cache reads cost 0.10x, so stable prefixes yield major savings across repeated calls. Any modification to a cached prefix invalidates the entire segment, so dynamic content like timestamps must be kept out of always-on files.

Why did my Claude Code session token cost regress after optimization?

Regression typically comes from silent rules proliferation and skill count growth, since each skill description costs roughly 84 tokens always-on. Run the monitoring checklist to compare rules files, skill counts, and memory files against the documented ceilings.

When should content go into rules versus skills versus a memory DB?

Use the decision tree: content required 100% of the time goes in rules, content needed 50-80% of the time becomes a skill, and cross-session knowledge goes into the memory DB queried via search tools. User-only invoked content gets DMI.