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 KevinZai/commander --skill ccc-resume-sessiongit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/ccc-resume-session)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-resume-session"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-resume-session.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Rogue Agent · line 40 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00038 | $0.01049 |
| Opus 5 | $0.00019 | $0.00524 |
| Sonnet 5 | $0.00008 | $0.00210 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
ccc-resume-session 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-resume-session — Resume Session State
Load the last saved session state and orient fully before doing any work.
This skill is the counterpart to $ccc-save-session.
When to Use
- Starting a new session to continue work from a previous day
- After starting a fresh session due to context limits
- When handing off a session file from another source (provide the file path as argument)
- Any time you have a session file and want Claude to fully absorb it before proceeding
Usage
$ccc-resume-session # loads most recent file in ~/.claude/sessions/
$ccc-resume-session 2024-01-15 # loads most recent session for that date
$ccc-resume-session ~/.claude/sessions/2024-01-15-session.tmp # loads a specific legacy-format file
$ccc-resume-session ~/.claude/sessions/2024-01-15-abc123de-session.tmp # loads a current short-id session file
Process
Step 1: Find the session file
If no argument provided:
- Check
~/.claude/sessions/ - Pick the most recently modified
*-session.tmpfile - If the folder does not exist or has no matching files, tell the user:
Then stop.No session files found in ~/.claude/sessions/ Run $ccc-save-session at the end of a session to create one.
If an argument is provided:
- If it looks like a date (
YYYY-MM-DD), search~/.claude/sessions/for files matching that date and load the most recently modified variant - If it looks like a file path, read that file directly
- If not found, report clearly and stop
Step 2: Read the entire session file
Read the complete file. Do not summarize yet.
Step 3: Confirm understanding
Respond with a structured briefing in this exact format:
SESSION LOADED: [actual resolved path to the file]
════════════════════════════════════════════════
PROJECT: [project name / topic from file]
WHAT WE'RE BUILDING:
[2-3 sentence summary in your own words]
CURRENT STATE:
Working: [count] items confirmed
In Progress: [list files that are in progress]
Not Started: [list planned but untouched]
WHAT NOT TO RETRY:
[list every failed approach with its reason — this is critical]
OPEN QUESTIONS / BLOCKERS:
[list any blockers or unanswered questions]
NEXT STEP:
[exact next step if defined in the file]
[if not defined: "No next step defined — recommend reviewing 'What Has NOT Been Tried Yet' together before starting"]
════════════════════════════════════════════════
Ready to continue. What would you like to do?
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 First seen · 125 lines · 38 tokens per session scan A 7897b66c3cdc
ccc-resume-session is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,049 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
scout-consolidation
Launch a Scout consolidation session as a background process. Runs a lighter delta scan — captures what changed since the last run and updates action items and KB.
maude
Use when the user is starting a session, losing track of where something is, asking "where did I put X", "where is X", "what's the state of Y", "what changed", wants to audit their config or setup, says "save this", "remember this", "remind me about Z", or invokes any /maude: command. ALSO use when the user expresses…
session
Session lifecycle management. Parent skill for session-related skills: learning (pattern extraction) and compact (context compression).
vault
Context vault operations: read/update todos, add log entries, search vault content, read strategy/project docs, update project files. Use when user says "vault", "add todo", "update todos", "log entry", "search vault", "check todos", "context vault", "add to log", or any operation on a personal context vault.
context-hygiene
Use when starting a project, reading project documentation or history, or resolving conflicts between documents. For current state, read only the latest documents designated by the project; do not proactively read archives; do not duplicate the spec; use long-term memory only for environment, people, and preferences…
g-resume
Re-hydrate a fresh session with the right slice of the durable record. The read-side counterpart to /g-retro — selectively retrieves the relevant retro, ADRs, journal, and handoff keyed by the current branch/milestone/first-task, and assembles a focused re-entry briefing. Loads distilled context into a clean window…