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 skills add cicababba/claude-plugins-marketplace --skill session-managergit clone --depth 1 https://github.com/cicababba/claude-plugins-marketplaceWrote 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/cicababba/claude-plugins-marketplace/session-manager)<a href="https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/session-manager"><img src="https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/session-manager/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.
<a href="https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/session-manager"><img src="https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/session-manager.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.01016 |
| Opus 5 | $0.00027 | $0.00508 |
| Sonnet 5 | $0.00011 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
session-manager 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Manager
This skill is the single source of truth for development session lifecycle management.
When to Use
- When creating a new development session
- When loading an existing session (by path or by filtering Status)
- When updating session metadata (Status, Last Updated, End Time, Duration)
- When closing a session and clearing
.current-session - At the start of
/init,/run, or/endcommands
Responsibilities
- Create session directory:
.claude/dev-sessions/YYYY-MM-DD-HHMM-${slug}/ - Initialize/update
session.mdheaders (Session Overview section only) - Read and update
.claude/dev-sessions/.current-session - Load existing sessions (with optional Status filtering)
- Update in
session.md:Status: PLANNING, READY, IN_PROGRESS, COMPLETED, PARTIALLY_COMPLETED, FAILEDStart Time: When session is createdLast Updated: On any modificationEnd Time: When session is closedDuration: Calculated from Start Time to End Time
- Close session and clear
.current-sessioncontent (file remains)
MUST NOT
- Generate context analysis, specification, plan, documentation, or code
- Modify any source code files
- Read or write
plan.mdcontent (only track its existence) - Execute development steps
- Trigger sub-agents
Process
Creating a New Session
-
Generate slug from task description (lowercase, hyphens, max 50 chars)
-
Generate timestamp:
YYYY-MM-DD-HHMM -
Create directory:
.claude/dev-sessions/{timestamp}-{slug}/ -
Initialize
session.mdwith Session Overview:## Session Overview **Start Time:** [YYYY-MM-DD HH:MM AM/PM] **Last Updated:** [YYYY-MM-DD HH:MM AM/PM] **Status:** PLANNING **Progress:** 0/0 steps completed **Task:** [task description] **Duration:** **End Time:** -
Write session path to
.claude/dev-sessions/.current-session
Loading an Existing Session
- Read
.claude/dev-sessions/.current-session - If file contains a valid path:
- Verify the session directory exists
- Return the session path
- If file is empty or path invalid:
- Scan
.claude/dev-sessions/for session directories - For each directory, read
session.mdand extract Status - Filter by requested status (e.g., READY, PLANNING, IN_PROGRESS)
- Present filtered list to user for selection
- Update
.current-sessionwith selected path - Return the session path
- Scan
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.
- 9d ago First seen · 114 lines · 54 tokens per session scan A 22093c089ff8
session-manager is a skill published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 54 tokens to every session and 1,016 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.