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 msiShariful/claude-token-inspector --skill suggest-splitgit clone --depth 1 https://github.com/msiShariful/claude-token-inspectorWrote 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/msishariful/claude-token-inspector/suggest-split)<a href="https://agentmods.dev/skills/msishariful/claude-token-inspector/suggest-split"><img src="https://agentmods.dev/badge/skills/msishariful/claude-token-inspector/suggest-split/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/msishariful/claude-token-inspector/suggest-split"><img src="https://agentmods.dev/badge/skills/msishariful/claude-token-inspector/suggest-split.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.00052 | $0.00753 |
| Opus 5.5 | $0.00021 | $0.00301 |
| Sonnet 5.5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
suggest-split 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 4d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conversation Split Advisor
Analyze the current conversation and determine whether it has drifted enough that starting a new session would meaningfully improve context quality.
Analysis process
-
Map the conversation topics — scan the full history and identify distinct task areas or subject shifts. A "topic" is a coherent unit of work (e.g., "debugging the auth middleware", "writing README", "reviewing PR #42").
-
Find the current task — what is the user actually working on right now? This is the anchor.
-
Score past topics by carry-forward value:
- Essential (carry forward): decisions made, constraints discovered, code written that is still active
- Partial (summarize): context that's partially relevant but could be distilled to 2–3 sentences
- Dead weight (discard): earlier topics completely unrelated to the current task
-
Assess the split case — is there a clear turning point where the conversation shifted to the current task? If yes, that's the split candidate.
Output format
If a split is recommended:
✂️ Split recommended — conversation has drifted across {N} topic(s)
Then:
Topic map (chronological):
| Turns | Topic | Status |
|---|---|---|
| 1–8 | Debugging login timeout | 🗑️ Discard — resolved, no longer relevant |
| 9–14 | Reviewing PR #42 | 📋 Summarize — 2 decisions still apply |
| 15–now | Refactoring auth middleware | ✅ This is your current task — carry forward |
What to carry into the new conversation:
Write a ready-to-paste context block the user can paste at the start of their new session:
--- CONTEXT FROM PREVIOUS SESSION ---
[2–5 bullet points covering only the decisions, constraints, and code that are still relevant to the current task. Be specific: file names, function names, exact decisions made.]
--- END CONTEXT ---
Split instructions:
1. Copy the context block above
2. Start a new Claude Code session
3. Paste the context block as your first message
4. Continue with: [one sentence describing where to pick up]
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.
- 4d ago Changed · +1 lines · +4 tokens per session 0be0a48acfbc
- 1mo ago First seen · 86 lines · 48 tokens per session scan A 0a9a5d59aa4c
suggest-split is a skill published in the GitHub repository msiShariful/claude-token-inspector (4 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 753 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
knowledge-wiki
A tool that turns useful lessons from coding sessions into general articles for a team wiki. A wiki is a collection of linked reference pages, and this one can be kept locally or shared through a Git repository.
team-memory-protocol
A shared-memory process for teams of coding agents working on the same build. It stores project knowledge, shared context, and task progress in separate files or repositories.
fresh-start
Continue in a new chat without losing anything — writes a compact handoff to paste into a fresh conversation. Use whenever the user wants to move to a new chat or conversation, hits usage limits, says replies got slow or Claude forgets earlier details, or the conversation has grown long.
doc-digest
Turn a long document, PDF, transcript, spreadsheet or log into a compact working digest the conversation can continue from. Use when the user shares or pastes something long (several pages or more) and wants to discuss, analyze, compare or use it over more than one message, or asks to summarize a document so they can…
project-context
Turn background the user keeps re-explaining or re-pasting into reusable instructions, so new chats start with it for free. Use when the user repeats the same context, rules, style guide, persona or reference text across messages or chats, says they are tired of explaining the same thing, or asks how to set up a…
token-check
Estimate how many tokens a pasted text, an attached file or the conversation so far takes, what it means for the context window and usage limits, and how to cut it. Use when the user asks how big something is in tokens, why they keep hitting limits, or whether a file is too large to send.