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 Shweta-Mishra-ai/tokenmizer --skill checkpointgit clone --depth 1 https://github.com/Shweta-Mishra-ai/tokenmizerWrote 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/shweta-mishra-ai/tokenmizer/checkpoint)<a href="https://agentmods.dev/skills/shweta-mishra-ai/tokenmizer/checkpoint"><img src="https://agentmods.dev/badge/skills/shweta-mishra-ai/tokenmizer/checkpoint/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/shweta-mishra-ai/tokenmizer/checkpoint"><img src="https://agentmods.dev/badge/skills/shweta-mishra-ai/tokenmizer/checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.00440 |
| Opus 5.5 | $0.00024 | $0.00176 |
| Sonnet 5.5 | $0.00012 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
checkpoint 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 1mo 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.
What it actually says
Save the current session to TokenMizer graph memory.
Session ID
Do not ask for one. $ARGUMENTS, if given, is the session ID. If it is empty,
TokenMizer derives the ID from the working directory name — stable across
sessions on the same project, and the convention the docs already recommend
(~/projects/auth-service → auth-service). The command prints the ID it
chose.
Ask only if the command exits 2, which means the directory has no usable name
to derive from (a filesystem root, or a generic folder such as tmp). Then
ask exactly: Which session ID should this be saved under?
What to do
tokenmizer checkpoint $ARGUMENTS
Relay the command's output. Do not restate it in your own words, do not add commentary or congratulation, and do not address the operator by name.
Output
Report the result in exactly this shape, filled from the command's output:
Checkpoint saved — auth-service
checkpoint ckpt_a3f9b2
nodes 14 (6 tasks, 4 decisions, 3 files, 1 error)
resume cost 247 tokens
Resume with: tokenmizer resume auth-service
If the command exits non-zero, show its error text unchanged. It already says
what to do — an unreachable server prints the tokenmizer serve instruction
itself.
Notes
- Session IDs are lowercase slugs:
auth-service, notAuth Service. - Use the same ID across sessions for the same project. That is what makes a later resume find anything.
- The server must be running for this command;
tokenmizer servestarts it.
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.
- 1mo ago Changed · -5 lines 4a3c1d5ae178
- 1mo ago First seen · 57 lines · 61 tokens per session scan A 5acc48674331
checkpoint is a skill published in the GitHub repository Shweta-Mishra-ai/tokenmizer (34 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 440 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-30.
Other skills, from other repositories
cdb-scan
Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map…
handoff
Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work…
catchup
Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.
session-log
USE WHEN ending a substantial working session — user says "thanks/tomorrow/wrap up", or session shipped 3+ commits with no log today, or user asks for a summary. Distills the conversation into docs/sessions/YYYY-MM-DD- .md (context, what was done, key decisions, open questions, next steps). Hard cap 80 lines.…
pickup
Resume work on this project after an interruption or at the start of a new session: show recent wins, what was being done, the next action, and open decisions, in that order, then stop. Trigger only on an explicit /squirrel:pickup invocation, or an explicit request to resume or pick up this project's past work at the…
claude-bridge-role-memory-keeper
Playbook for a Claude Code agent in the dedicated memory keeper role — single-writer for shared agent memory across a team of 3+ peers. Use when you are designated as the keeper (= other peers send you write candidates, you write them and watch for drift). Memory hygiene + reconciliation against the canon + drift…