save-transcript

A session tool that saves the current coding conversation as a readable Markdown file.

In plain words
What is it for?
Use it to export or snapshot a session, or preserve the conversation before it is shortened during context compaction.
Why use it?
It gives you a lasting copy of the conversation instead of leaving it only in the current session.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/idisposable/claude-transcript-plugin/save-transcript
Any agent
npx skills add IDisposable/claude-transcript-plugin --skill save-transcript
Clone the repo
git clone --depth 1 https://github.com/IDisposable/claude-transcript-plugin

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 201 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.00201
Opus 5 $0.00015 $0.00101
Sonnet 5 $0.00006 $0.00040
Haiku 4.5 $0.00003 $0.00020

Measured yesterday against content hash 1e9da88b07ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

save-transcript 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 yesterday.

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.

skills/save-transcript/SKILL.md · 26 lines

What it actually says

Save Transcript

Save the current session's conversation to a readable Markdown file.

Steps

  1. Find the current session's JSONL transcript file. It is located at the path shown in the session metadata, typically under ~/.claude/projects/.

  2. Run the transcript converter:

    echo '{"session_id": "<session-id>", "transcript_path": "<path-to-jsonl>", "cwd": "<current-working-dir>"}' | ${CLAUDE_PLUGIN_ROOT}/scripts/run
    
  3. Report the output file path to the user.

Notes

  • Transcripts are saved to ~/.claude/transcripts/ by default.
  • Override with TRANSCRIPT_OUTPUT_DIR environment variable.
  • The hook also runs automatically before every context compaction.
Changes

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.

  1. yesterday First seen · 26 lines · 30 tokens per session scan A 1e9da88b07ba

Subscribe to this mod's changes

save-transcript is a skill published in the GitHub repository IDisposable/claude-transcript-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 201 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens