replay

replay is a skill for Claude Code from tuo-lei/vibe-replay. It costs 56 tokens per session (3,093 once invoked), scanned B, original, MIT.

A skill for finding, reviewing, and sharing past AI coding sessions from Claude Code, Cursor, or Codex.

In plain words
What is it for?
It searches sessions, creates replays and pull-request summaries, attaches session context to PRs, and reviews prompts, tool use, errors, and efficiency.
Why use it?
It helps recover context that is difficult to reconstruct from memory or from scattered conversation records.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Part of the vibe-replay plugin — 1 skill, 1 hook shipped together

Good fit It searches sessions, creates replays and pull-request summaries, attaches session context to PRs, and reviews prompts, tool use, errors, and efficiency.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tuo-lei/vibe-replay/replay
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.

Any agent
npx skills add tuo-lei/vibe-replay --skill replay
Clone the repo
git clone --depth 1 https://github.com/tuo-lei/vibe-replay

Made for: Claude Code.

Or install vibe-replay, the plugin that ships this one along with the rest of its 1 skill, 1 hook.

Wrote 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.

agentmods badge for replay

README.md
[![agentmods](https://agentmods.dev/badge/skills/tuo-lei/vibe-replay/replay/github.svg)](https://agentmods.dev/skills/tuo-lei/vibe-replay/replay)
Your own site
<a href="https://agentmods.dev/skills/tuo-lei/vibe-replay/replay"><img src="https://agentmods.dev/badge/skills/tuo-lei/vibe-replay/replay/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for replay

Your own site · 80×15
<a href="https://agentmods.dev/skills/tuo-lei/vibe-replay/replay"><img src="https://agentmods.dev/badge/skills/tuo-lei/vibe-replay/replay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,093 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 14 findings, up to high

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 →

  • high Agent Snooping · line 50
    Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.
    Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
  • medium Rogue Agent · line 23
    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.
  • medium MCP Rug Pull · line 60
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 66
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 67
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 68
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 69
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 70
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 87
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 104
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 118
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 203
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 209
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium Rogue Agent · line 156
    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.
How audits are shown
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.1 $0.00056 $0.03093
Opus 5 $0.00028 $0.01546
Sonnet 5 $0.00011 $0.00619
Haiku 4.5 $0.00006 $0.00309

Measured 12d ago against content hash 6c37bd4b2b86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

replay scanned grade B with 1 finding 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 12d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

grep -l '"sessionId":"${CLAUDE_SESSION_ID}"' ~/.claude/projects/*/*.jsonl 2>/dev/null
skills/replay/SKILL.md · 264 lines

How it starts

The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.

This skill helps agents find local AI coding sessions, generate shareable replay artifacts, and paste polished session context into PRs. It uses vibe-replay for the raw session discovery, parsing, redaction, analytics, and export work, then uses agent judgment for review, cleanup, and sharing decisions.

What this skill is for

Use this skill when the user asks to:

  • Generate a replay or GitHub-ready summary of an AI coding session.
  • Attach Claude Code, Cursor, or Codex session context to a PR.
  • Find a previous session, transcript, replay, branch discussion, bug investigation, PR, or design thread.
  • Remember what happened in a past agent conversation.
  • Run a retro on prompt quality, tool usage, errors, compactions, cost, or agent efficiency.
  • Compare sessions or choose which session should be replayed/shared.

Plain text summaries of an AI session - stats, tool breakdown, per-prompt details - are hard for an agent to write from scratch. Delegate that to vibe-replay, then use agent reasoning to handle the things a CLI cannot decide well:

  • Ranking session search results - choosing the likely match from metadata and brief scan signals.
  • Reviewing flagged credentials - deciding whether a regex hit is a real secret or a false positive.
  • Translating session prompts that are not in the audience's language.
  • Softening tone in prompts written when the user was frustrated.
  • Appending to PRs safely - preserving existing PR descriptions instead of overwriting them.

Each cleanup step is opt-in. Ask the user before rewriting their content.

Step 1 - Choose the session

Prefer structured discovery over manually browsing local history.

If the user provides a session path

Use the provided path. Infer the provider when possible:

  • Cursor transcripts usually live under ~/.cursor/projects/.../agent-transcripts/....
  • Claude Code transcripts usually live under ~/.claude/projects/.../*.jsonl.
  • Codex sessions are discoverable through vibe-replay sessions; if the path is not obviously Claude or Cursor, pass the provider returned by search or ask the user.

Read the full file on GitHub · 264 lines

Files

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.

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. 12d ago First seen · 264 lines · 56 tokens per session scan B 6c37bd4b2b86

Subscribe to this mod's changes

replay is a skill published in the GitHub repository tuo-lei/vibe-replay (37 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 3,093 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.