Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add sgaunet/claude-plugins --skill check-claude-md-tokensgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sgaunet/claude-plugins/check-claude-md-tokens)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/check-claude-md-tokens"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/check-claude-md-tokens/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/check-claude-md-tokens"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/check-claude-md-tokens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.01199 |
| Opus 5.5 | $0.00010 | $0.00480 |
| Sonnet 5.5 | $0.00005 | $0.00240 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
check-claude-md-tokens scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md Token Counter
Monitor the token count of CLAUDE.md files to ensure they stay within the recommended 2500 token limit. This skill analyzes the current token usage and provides reduction recommendations when the limit is exceeded.
Process
-
Locate CLAUDE.md Files: Find all CLAUDE.md files in the repository:
- Project-level:
./CLAUDE.md - Global user config:
~/.claude/CLAUDE.md
- Project-level:
-
Calculate Token Count: Use character-based estimation (~4 characters per token):
wc -c CLAUDE.md | awk '{print int($1/4)}' -
Evaluate Against Limit: Check if token count exceeds 2500 tokens
-
Report Status: Display current token usage with clear status indicator:
- ✅ Under limit (< 2500 tokens)
- ⚠️ Near limit (2000-2500 tokens)
- ❌ Over limit (> 2500 tokens)
-
Offer Reduction: If over limit, analyze content and propose specific reductions
Token Count Formula
Estimation: tokens ≈ characters ÷ 4
This rough estimate works well for English text. The actual token count may vary slightly based on:
- Word length and complexity
- Technical terminology
- Code snippets
- Formatting characters
Reduction Strategies
When CLAUDE.md exceeds the token limit, apply these optimization techniques:
1. Remove Redundancy
- Eliminate duplicate instructions
- Consolidate similar rules
- Remove verbose explanations
2. Use Concise Language
- Replace verbose phrases with concise alternatives
- Remove filler words and redundant modifiers
- Use bullet points instead of paragraphs
3. Externalize Content
- Move detailed examples to separate documentation
- Reference external guides instead of duplicating content
- Create auxiliary files for extensive specifications
4. Prioritize Critical Instructions
- Keep only essential directives
- Remove nice-to-have preferences
- Focus on behavior-changing instructions
5. Optimize Formatting
- Use abbreviations for repeated terms
- Reduce whitespace and empty lines
- Compress nested lists
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 22d ago First seen · 142 lines · 25 tokens per session scan A bf76f7dd1d0a
check-claude-md-tokens is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 1,199 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-25.
Other skills, from other repositories
metrics-dashboard
Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
interview-script
Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.