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 agentmods add skills/vimalk0703/shipworthy/session-memorynpx skills add Vimalk0703/shipworthy --skill session-memorygit clone --depth 1 https://github.com/Vimalk0703/shipworthyWhat 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 | $0.00046 | $0.01428 |
| Opus 5 | $0.00023 | $0.00714 |
| Sonnet 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 2d 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.
- 2d ago First seen · 135 lines · 46 tokens per session scan A 474198d4c9bb
session-memory is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 1,428 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
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:opening-pull-requests
Open a GitHub Pull Request with automatic base branch detection, scope allowlist enforcement, PR template filling, and post-create base verification. Replaces ring:generating-pr-descriptions. Use after pushing a branch when ready to open a PR. Skip if the branch is not yet pushed or there are uncommitted changes …
ring:cleaning-comments
Cleaning redundant and obvious comments following clean code principles while preserving meaningful documentation. Supports git scope filtering (staged, unstaged, branch, commit-range). Use when code has excessive comments, during code review, or post-refactor cleanup. Skip when reviewing documentation files or…
ring:fixing-lint
Fixing lint to a clean state: runs the linter, groups reported issues into independent streams, and dispatches one parallel fixer agent per stream (ring:backend-go for Go, ring:general-purpose otherwise), iterating until clean. Use when a codebase has lint errors across multiple files. Skip for a single error (fix…