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/stefan-stepzero/shipkit/shipkit-work-memorynpx skills add stefan-stepzero/shipkit --skill shipkit-work-memorygit clone --depth 1 https://github.com/stefan-stepzero/shipkitWhat 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.00042 | $0.02821 |
| Opus 5 | $0.00021 | $0.01411 |
| Sonnet 5 | $0.00008 | $0.00564 |
| Haiku 4.5 | $0.00004 | $0.00282 |
Grade A, and why
shipkit-work-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 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.
How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipkit-work-memory - Session Progress & Resume State
Purpose: Capture structured session progress — milestones, blockers, decisions, and resume state — by inferring from conversation and git. User confirms, Claude does the work.
Note: Claude Code's auto-memory (v2.1.59+) automatically saves basic session context. This skill is for structured progress tracking that auto-memory doesn't capture: explicit milestones, decision rationale, blocker status, and handoff state for session continuity.
Output: .shipkit/progress.json — A timeline graph artifact ideal for session history visualization.
When to Invoke
User triggers:
- "End session"
- "Log progress"
- "Save checkpoint"
- "What did we do?"
- "Save session"
Suggested after:
- Long implementation sessions
- Before context gets full
- Before switching tasks
- End of work session
Prerequisites
None required - Can start fresh.
Uses if available:
.shipkit/progress.json- Merge with existing sessions- Git - For modified files detection
JSON Schema (Quick Reference)
This skill outputs .shipkit/progress.json using the Shipkit JSON Artifact Convention.
{
"$schema": "shipkit-artifact",
"type": "work-memory",
"version": "1.0",
"lastUpdated": "2025-01-15T10:00:00Z",
"source": "shipkit-work-memory",
"summary": { "totalSessions", "currentPhase", "lastSessionDate", "activeWorkstream", "blockers", "momentum" },
"sessions": [{ "id", "date", "duration", "workstream", "phase", "accomplished", "filesModified", "decisions", "gotchas", "blockers", "nextSteps", "status" }],
"workstreams": [{ "id", "name", "status", "startDate", "sessions", "completionEstimate" }],
"resumePoint": { "lastSession", "immediateNextStep", "context", "openFiles", "relatedArtifacts" },
"timeline": [{ "date", "event", "type" }]
}
Full schema and field reference: See references/output-schema.md
Realistic example: See references/example.json
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 420 lines · 42 tokens per session scan A f4971b6c3321
shipkit-work-memory is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 2,821 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.