Skip to content
Back to skills

Session Timer

ASecurity

Check how long the current session has been running. Use when asking about session length, duration, "how long have I been at this", "how long have I been working", whether it's time to checkpoint, or any time-since-start question.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 12, 2026
ai-agentsgo

Works with

  • claude code

Security analysis

A100/100

Scanned October 12, 2026

npx -y skills add AfterRealm/father-time --skill session-timer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Session Timer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Session Timer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/afterrealm-session-timer/badge)](https://www.skillsdirectory.com/skills/afterrealm-session-timer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: session-timer
description: Check how long the current session has been running. Use when asking about session length, duration, "how long have I been at this", "how long have I been working", whether it's time to checkpoint, or any time-since-start question.
license: MIT
metadata:
  author: AfterRealm
  version: "1.9.1"
---

# Session Timer

Show the user how long their current Claude Code session has been active.

## How It Works

The `SessionStart` hook writes a timestamp to `${CLAUDE_PLUGIN_DATA}/session_start.txt` when the session begins. The `UserPromptSubmit` hook calculates elapsed time on every prompt and includes it in the time injection.

## What to Show

1. **Session duration** — hours and minutes since session start
2. **Checkpoint suggestion** — if over 2 hours, suggest checkpointing state
3. **Context health** — longer sessions use more context. After 3+ hours, suggest `/compact` if context is getting heavy.

## Response Format

Short and direct:
- "Session: 1h 23m. No action needed."
- "Session: 3h 45m. Consider checkpointing or compacting if things feel sluggish."
- "Session: 6h+. Marathon territory. Your context might benefit from a `/compact`."

## Milestone Nudges (Optional)

If the user has been going for a while, a brief note is fine:
- **2 hours**: "2 hours in. Good checkpoint moment if you want to save state."
- **4 hours**: "4 hours. Your context window is holding up but a checkpoint preserves your progress."
- **6+ hours**: "6+ hours. Legendary session. Checkpoint highly recommended."

These are suggestions, not demands. Never block the user from working.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.