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 Vimalk0703/shipworthy --skill session-memorygit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/session-memory)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/session-memory"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/session-memory/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/vimalk0703/shipworthy/session-memory"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/session-memory.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.00046 | $0.01428 |
| Opus 5.5 | $0.00018 | $0.00571 |
| Sonnet 5.5 | $0.00009 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
session-memory 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Memory
Purpose
Claude Code sessions are stateless — each new session starts fresh. But projects are not stateless. Work in progress, architectural decisions, feature specs, and implementation plans need to survive between sessions. This skill formalizes .shipworthy/ as the persistent memory layer.
Memory Structure
.shipworthy/
├── INDEX.md # Auto-generated index of all project memory (refreshed each session + after /retro)
├── architecture.md # Project architecture spec (managed by architecture-awareness skill)
├── tech-debt.md # Tech debt tracker (managed by tech-debt-tracking skill)
├── config.json # Per-project configuration and overrides
├── specs/ # Feature specifications (managed by intent-to-spec skill)
│ ├── user-auth.md
│ ├── invoice-system.md
│ └── ...
├── plans/ # Implementation plans (managed by writing-plans skill)
│ ├── user-auth.md
│ └── ...
├── decisions/ # Architecture Decision Records (ADRs)
│ ├── 001-database-choice.md
│ └── ...
├── learnings/ # What this project has taught us (managed by retrospective skill)
│ ├── database-preferences.md
│ ├── api-patterns.md
│ └── ...
└── sessions/ # Session summaries for continuity
├── 2026-03-29.md
└── ...
Session Summary
At the END of each session (when the user says goodbye, closes the conversation, or you detect natural completion), write a brief session summary:
Format: .shipworthy/sessions/[YYYY-MM-DD].md
# Session Summary — [YYYY-MM-DD]
## What Was Done
- [Completed task 1]
- [Completed task 2]
## What's In Progress
- [Task that was started but not finished]
- [Relevant context for picking it up]
## Decisions Made
- [Any architectural or design decisions — link to ADR if created]
## Next Steps
- [What should happen next]
- [Any blockers or open questions]
Keep it under 20 lines. This is a breadcrumb trail, not a novel.
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.
- 1mo ago First seen · 135 lines · 46 tokens per session scan A 474198d4c9bb
session-memory is a skill published in the GitHub repository Vimalk0703/shipworthy (6 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 1,428 once invoked, about $0.0002 per session on Opus 5.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
report
Writes the session final report to a file, then prints only the path and a one-line summary. Fires when the prompt contains "Report per memstack:report", and also when the prompt begins with a standing trigger configured through MEMSTACKREPORTONTASKPROMPTS or MEMSTACKREPORTTRIGGERS. Dormant otherwise.
token-optimization
Use when the user says 'token optimization', 'save tokens', 'context window', 'reduce tokens', 'token stack', or 'TokenStack', or asks about extending context window capacity. Covers TokenStack, the built-in compression proxy that shrinks Claude Code tool output before it reaches the Anthropic API. Do NOT use for…
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
catchup
Restore context after /clear by summarizing recent work and project state.
hedgehog-planning-intake
Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…
bmad-product-brief
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.