session:status

A way to inspect the current coding session: what context was loaded, which outputs were saved, and which tasks are active or ready. A coding session is the current working conversation and project state.

In plain words
What is it for?
Use it to check session files, archived terminal or tool results, task status, and project focus.
Why use it?
It helps when you need to understand what the agent has already seen or produced, especially after information was saved to files.

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/gh33k/session-plugin/status
Any agent
npx skills add gh33k/session-plugin --skill status
Clone the repo
git clone --depth 1 https://github.com/gh33k/session-plugin

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 494 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.00035 $0.00494
Opus 5 $0.00017 $0.00247
Sonnet 5 $0.00007 $0.00099
Haiku 4.5 $0.00003 $0.00049

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

Security

Grade A, and why

session:status 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/status/SKILL.md · 93 lines

What it actually says

session:status

Show context awareness for current session.

Instructions

1. Find Current Session

ls -t .context/sessions/*.md 2>/dev/null | head -1

2. Gather Context Info

Session basics:

# Session file
cat .context/sessions/session_*.md 2>/dev/null | head -20

# Session start time
grep "^# Session" .context/sessions/session_*.md | tail -1

Archived outputs (context saved):

# Terminal archives this session
ls -la .context/terminal/*.log 2>/dev/null | wc -l

# MCP archives this session
ls -la .context/mcp/*.md 2>/dev/null | wc -l

Beads status (if active):

bd list --status=in_progress --json 2>/dev/null | jq 'length'
bd ready --json 2>/dev/null | jq 'length'

3. Output Status

Session Status
==============

Session: .context/sessions/{file}
Started: {timestamp}
Type: {plan|build|fix|etc}

Context loaded:
  - Orientation: {from session file Context section}

Archived (saved from context):
  - Terminal outputs: {count} files
  - MCP responses: {count} files

Tasks:
  - In progress: {count}
  - Ready: {count}

Project:
  - Focus: {from state.md}
  - Blockers: {count}

4. Optional: Estimate Context Usage

If user asks for more detail:

Context Estimate
----------------
Session orientation: ~50 lines
Files read this session: (check conversation)
Archived outputs: {X} large outputs moved out of context

Tip: Large outputs (>50 lines) are auto-archived to .context/

Quick Check

For fast status, just show:

Session: {type} | Tasks: {in_progress} active, {ready} ready | Archives: {count}
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 · 93 lines · 35 tokens per session scan A ec76a10800ff

Subscribe to this mod's changes

session:status is a skill published in the GitHub repository gh33k/session-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 494 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.