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 dev-session-closuregit 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/dev-session-closure)<a href="https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-session-closure"><img src="https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-session-closure.svg" alt="Measured on agentmods" 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.00040 | $0.01273 |
| Opus 5 | $0.00020 | $0.00636 |
| Sonnet 5 | $0.00008 | $0.00255 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
dev-session-closure 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 8d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Session Closure
This skill handles the proper closure of development sessions.
When to Use
- During
/endcommand - When finalizing a development session
- When computing final session status
- When clearing
.current-session
Input
sessionPath: Path to the current session (or read from.current-session)options:triggerCommit: boolean - Whether to trigger git commitstriggerDocs: boolean - Whether to trigger documentation generationtriggerQuality: boolean - Whether to trigger quality checkmodifiedFiles: string[] - List of files modified in session (for quality check)
Responsibilities
- Load session via
session-manager - Read
session.md(andplan.mdif needed) viaartifact-fs-manager - Compute final Status based on step completion:
- All steps
COMPLETED→COMPLETED - Some steps
FAILED→FAILED - Some
COMPLETEDand someNOT_STARTED→PARTIALLY_COMPLETED - No plan exists (planning phase only) →
READY
- All steps
- Update
session.md:Status: Final computed statusEnd Time: Current timestampDuration: Calculated from Start TimeLast Updated: Current timestamp
- Optionally trigger (based on flags):
- Git commits via
git-and-docsskill - Documentation generation via
git-and-docsskill - Quality report via
dev-quality-reportskill
- Git commits via
- Clear
.current-sessioncontent viasession-manager
MUST NOT
- Modify
plan.mdcontent - Execute development steps
- Re-run planning
- Modify source code
Process
Step 1: Load Session
- Use
session-managerto load current session - Verify session exists and is in a closeable state
Step 2: Read Session State
- Use
artifact-fs-managerto readsession.md - Check if
plan.mdexists - Extract current Status
- Extract all step statuses from "All Steps Overview"
Step 3: Handle Based on Current Status
If Status is PLANNING:
- No steps to evaluate
- Set Status to
READY - Update timestamps only
- Do NOT trigger commits, docs, or quality check
- Suggest
/runto execute
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.
- 8d ago First seen · 182 lines · 40 tokens per session scan A 2751e2dbc516
dev-session-closure is a skill published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 40 tokens to every session and 1,273 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.
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.