Development
Skill
/treat
Prune bloated session with a prescription. Removes progress ticks, stale reads, duplicate content, and more.
Claude Code
$ npx -y skills add Ruya-AI/cozempic --skill treat --agent claude-code
Codex
$ npx skills add Ruya-AI/cozempic --skill treat -a codex -y
Cursor
$ npx skills add Ruya-AI/cozempic --skill treat -a cursor -y
Gemini CLI
$ npx skills add Ruya-AI/cozempic --skill treat -a gemini-cli -y
GitHub Copilot
$ npx skills add Ruya-AI/cozempic --skill treat -a github-copilot -y
OpenCode
$ npx skills add Ruya-AI/cozempic --skill treat -a opencode -y
Windsurf
$ npx skills add Ruya-AI/cozempic --skill treat -a windsurf -y
SKILL.md
treat.SKILL.mdname: treat
description: Prune bloated session with a prescription. Removes progress ticks, stale reads, duplicate content, and more.
argument-hint: "[gentle|standard|aggressive]"
disable-model-invocation: true
allowed-tools: Bash(cozempic *), AskUserQuestion
Apply a pruning prescription to the current session. Default is `standard` if no argument given.
**When to use `treat` vs `reload`:** prefer the `reload` skill — it does the same prune plus auto-resume in one step (`/exit` → new terminal opens with the pruned session). Use `treat` only when the user explicitly wants to stay in the current session, work in a multi-pane setup, or resume manually.
Steps
1. **Diagnose first** — show the user what they're working with:
cozempic current --diagnose
2. **Dry-run the treatment** — show savings without applying:
cozempic treat current -rx $ARGUMENTS
If no argument was provided, use `standard`:
cozempic treat current -rx standard
3. **Show results** — present the dry-run output including token savings (the `Tokens:` line). Always surface both byte and token savings.
4. **Ask confirmation** — use AskUserQuestion to confirm before applying.
5. **Apply on confirmation**:
cozempic treat current -rx $ARGUMENTS --execute
6. **Tell the user**: "Treatment applied. A backup was created automatically. To resume with the pruned session, exit and run `claude --resume`. (Tip: next time, the `reload` skill does this in one step — `/exit` and a fresh terminal opens automatically.)"
Prescriptions
| Rx | Strategies | Typical Savings | |----|-----------|----------------| | `gentle` | progress-collapse, file-history-dedup, metadata-strip | 40-55% | | `standard` | gentle + thinking-blocks, tool-output-trim, stale-reads, system-reminder-dedup | 50-70% | | `aggressive` | standard + error-retry-collapse, document-dedup, mega-block-trim, envelope-strip | 70-95% |
Safety
- Always dry-run first — never execute without showing the user what will change
- Backups are automatic (timestamped .bak files)
- Never touches uuid/parentUuid — conversation DAG stays intact
Read more
name: treat description: Prune bloated session with a prescription. Removes progress ticks, stale reads, duplicate content, and more. argument-hint: "[gentle|standard|aggressive]" disable-model-invocation: true allowed-tools: Bash(cozempic *), AskUserQuestion
Apply a pruning prescription to the current session. Default is `standard` if no argument given.
**When to use `treat` vs `reload`:** prefer the `reload` skill — it does the same prune plus auto-resume in one step (`/exit` → new terminal opens with the pruned session). Use `treat` only when the user explicitly wants to stay in the current session, work in a multi-pane setup, or resume manually.
Steps
1. **Diagnose first** — show the user what they're working with:
cozempic current --diagnose
2. **Dry-run the treatment** — show savings without applying:
cozempic treat current -rx $ARGUMENTS
If no argument was provided, use `standard`:
cozempic treat current -rx standard
3. **Show results** — present the dry-run output including token savings (the `Tokens:` line). Always surface both byte and token savings.
4. **Ask confirmation** — use AskUserQuestion to confirm before applying.
5. **Apply on confirmation**:
cozempic treat current -rx $ARGUMENTS --execute
6. **Tell the user**: "Treatment applied. A backup was created automatically. To resume with the pruned session, exit and run `claude --resume`. (Tip: next time, the `reload` skill does this in one step — `/exit` and a fresh terminal opens automatically.)"
Prescriptions
| Rx | Strategies | Typical Savings | |----|-----------|----------------| | `gentle` | progress-collapse, file-history-dedup, metadata-strip | 40-55% | | `standard` | gentle + thinking-blocks, tool-output-trim, stale-reads, system-reminder-dedup | 50-70% | | `aggressive` | standard + error-retry-collapse, document-dedup, mega-block-trim, envelope-strip | 70-95% |
Safety
- Always dry-run first — never execute without showing the user what will change
- Backups are automatic (timestamped .bak files)
- Never touches uuid/parentUuid — conversation DAG stays intact
Stats
430
Stars
40
Forks
Maintained
Maintenance
Python
Language
MIT
License
Last commit
Created
In this plugin
See everything inside 
Ships withcozempic
100,000+ power users trust Cozempic to keep their Claude Code sessions lean. Context cleaning for Claude Code — remove the bloat, keep everything that matters, protect Agent Teams from context loss.
4275 skills1 MCP
Stars on GitHub
Momentum
- stars in total
- 427
More skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about treat.
- Which coding agents can use treat?
- treat installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.