ccc-session SKILL.md skillA
ccc-session from kevinzai/commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kevinzai/commander/ccc-session@git:20261013.fbe187dPins git:20261013.fbe187d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kevinzai/commander
- Path
commander/cowork-plugin-codex/skills/ccc-session/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261013.fbe187d, committed Oct 13, 2026
- First version recorded
- May 14, 2026
- Size
- 3,166 bytes
- Repository stars
- 6
- License
- MIT
Alias that routes session work to the canonical skills: save the current session with $ccc-save-session, or reload a saved one with $ccc-resume-session. Use when the user says resume session, continue where I left off, save this session, or types $ccc-session.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# $ccc-session — save or resume, routed
**CC Commander** · $ccc-session · one picker, then the canonical session skill does the work.
This is an alias kept so `$ccc-session` and older references still resolve. It holds no session logic of its own: `$ccc-save-session` writes the handoff, `$ccc-resume-session` loads it.
On Codex, AskUserQuestion becomes a plain-text question and skills are invoked as `$ccc-save-session` / `$ccc-resume-session`.
## When to use / when not to
- Use when the user asks to save, resume, review or browse sessions without naming the exact skill.
- Use `$ccc-handoff` instead when context is large mid-task and work should continue in a fresh chat.
## What happens
1. Route by argument:
- `save` or `export` → invoke the `ccc-save-session` skill.
- `resume` or `review` → invoke the `ccc-resume-session` skill with no argument (most recent session).
- `history` → step 2.
- No argument → ask with AskUserQuestion:
```yaml
question: "What do you want to do with this session?"
header: "CC Commander — Session"
multiSelect: false
options:
- label: "🟢 Resume the last session"
…Read the whole file at its exact version.
How to install
mdr add kevinzai/commander/ccc-session@sha256:d285b2469873ec33The line at the top of this page pins the label git:20261013.fbe187d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_tayqnxmaczqsrclv)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 14, 2026 and Oct 13, 2026, about one every 38 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261013.fbe187d latest | 2026-10-13 | fbe187d | 3,166 B | A | view · diff |
| git:20260722.9d3ab82 | 2026-07-22 | 9d3ab82 | 1,074 B | A | view · diff |
| git:20260707.947ab2f | 2026-07-07 | 947ab2f | 942 B | A | view · diff |
| git:20260701.1f4accc | 2026-07-01 | 1f4accc | 773 B | A | view · diff |
| git:20260514.2648602 | 2026-05-14 | 2648602 | 3,854 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3166 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kevinzai/commander · 6 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tayqnxmaczqsrclv GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-session GET https://markdownregistry.com/api/v1/blob/d285b2469873ec33654e9994f72332c7eaec7714aa9f18bafaa81e0190d54aa1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kevinzai/commander
Every file in kevinzai/commander