Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ww-w-ai/super-token-saver/plugin install super-token-saverWrote 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/ww-w-ai/super-token-saver/s-continue)<a href="https://agentmods.dev/skills/ww-w-ai/super-token-saver/s-continue"><img src="https://agentmods.dev/badge/skills/ww-w-ai/super-token-saver/s-continue/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/ww-w-ai/super-token-saver/s-continue"><img src="https://agentmods.dev/badge/skills/ww-w-ai/super-token-saver/s-continue.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.00095 | $0.05999 |
| Opus 5 | $0.00048 | $0.03000 |
| Sonnet 5 | $0.00019 | $0.01200 |
| Haiku 4.5 | $0.00010 | $0.00600 |
Grade A, and why
s-continue 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 2d 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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Restore context from previous sessions so the user can pick up where they left off — without the cost of /compact.
Two tools, one history. Sessions come from Claude Code (~/.claude/projects/) and from Codex
(~/.codex/sessions/). A Codex rollout is rewritten into the shape Claude Code writes, one output
line per input line, so both are read by the same code and an L{n} marker still points at the
Codex original's line. Work stopped in one tool is therefore resumable in the other.
Help
ONLY show help if the user's argument literally contains the word "help" (e.g. /s-continue help). If no argument or any other argument is given, SKIP this section entirely and proceed to Step 1.
If the user provides "help" as argument, show usage summary and stop:
/s-continue — Restore context from previous sessions (zero LLM calls)
Options:
(nothing) Show session list (Claude Code + Codex), pick which to restore
- Current session with context-loss events appears as #0 [default]
- Press Enter to restore just #0, or add more numbers
last Quick restore:
- Current session if it had /compact or auto-compact
- Otherwise, most recent other session
claude|codex Restrict the list to one tool
help Show this help
Examples:
/s-continue
/s-continue codex
/s-continue codex : rust migration
Do not run any analysis or restoration. Just display the help text and stop.
What a restore contains
compact.txt is a preview, not a transcript. The preprocessor truncated it when it was built:
| Threshold | Kept | |
|---|---|---|
| User message | 500 chars | first 300 + ..[N lines omitted].. + last 200 |
| Assistant reply | 200 chars | first 100 + [...truncated...] + last 100 |
Every turn of a selected session is restored. Within one turn the first 24 and last 24 replies are
kept as stored and the ones in between are shortened to 50 chars — during an autonomous run the
assistant answers dozens of times under one user turn, and without that cut a single turn is
unbounded (60 replies under one message measured 27 KB on their own). No reply is dropped: the
-> N AI responses at lines X-Y pointer above each turn locates the originals in the JSONL, and the
reply's own number is its position within that range.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · -55 lines 7601a4c78d7e
- 4d ago Changed · +2 lines 305764316666
- 6d ago Changed · -72 lines 7880bd410a29
- 10d ago First seen · 612 lines · 95 tokens per session scan A 91a11516c639
s-continue is a skill published in the GitHub repository ww-w-ai/super-token-saver (31 stars, last pushed 2d ago), licensed Apache-2.0. It adds 95 tokens to every session and 5,999 once invoked, about $0.0005 per session on Opus 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
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
pith-wiki
Wiki mode — persistent knowledge base maintenance. Active during /pith wiki mode. Defines page formats, ingest workflow, query workflow, and lint checks.
pith-setup
Pith onboarding conversation. Runs on first session in a new project. Introduces Pith, offers wiki setup, guides through initialization. Injected by session-start.js when no prior setup detected.
start-session
Resume work from the second-brain — vault dashboard brief plus the per-repo thread (what happened last, what is next) with a mechanical staleness check. Use at the start of a working session.
sw-learn
Captures patterns and learnings from the current work unit. Reviews build failures, gate findings, and architecture decisions. Applies objective promotion criteria autonomously — patterns.md is the artifact.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…