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 agentmods add skills/brenbuilds1/cutweight/session-cutnpx skills add brenbuilds1/cutweight --skill session-cutgit clone --depth 1 https://github.com/brenbuilds1/cutweightWrote 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/brenbuilds1/cutweight/session-cut)<a href="https://agentmods.dev/skills/brenbuilds1/cutweight/session-cut"><img src="https://agentmods.dev/badge/skills/brenbuilds1/cutweight/session-cut.svg" alt="Measured on agentmods" 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.00071 | $0.00387 |
| Opus 5 | $0.00036 | $0.00193 |
| Sonnet 5 | $0.00014 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00039 |
Grade A, and why
session-cut 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 5d 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
Session Cut
Every message you send re-sends the conversation so far. The longer the session, the heavier each message gets, and the older context starts working against you. Knowing when to cut a session saves more tokens than any single trim.
The Calls
- One task, one session. Starting an unrelated task in an old session makes the new task carry the old one's weight.
/clearbetween unrelated tasks. It is the cheapest reset there is./compactonly to continue the SAME task past context limits. Compaction is a summary; treat it as lossy, because it is.- Fresh session with a handoff note beats a compacted haze. Before you clear, have the agent write five lines: what was done, what is next, which files matter. Paste that into the new session.
The Tells
Cut the session when:
- The agent re-reads files it already read this session.
- It forgets or contradicts a decision made earlier in the session.
- Replies slow down or drift off the task you actually asked for.
- The work left is unrelated to the transcript behind it.
Hard Rules
- Never /compact as a reflex. Ask first: is this the same task?
- The handoff note gets written before the clear, not remembered after.
- If the agent is fighting the context instead of the problem, cut the session. Reset.
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.
- 5d ago First seen · 44 lines · 71 tokens per session scan A 6cd5c0694bf2
session-cut is a skill published in the GitHub repository brenbuilds1/cutweight (2 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 387 once invoked, about $0.0004 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-31.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
daily-journal
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say…
general
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember something, or requests skill search and…
project-memory-keeper
Analyzes the last session to log progress, extract lessons learned, and save them to the project memory instructions.
Promote
Take a slice of the current conversation and promote it to a durable vault artifact — concept note, project update, person profile, or doctrine entry. Pairs with /close. /close writes the daily note (transient outcome record); /promote elevates specific insights to permanent vault content the framework can refer back…
open
Boot the session, load context from the vault, and surface what matters.