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 stefan-stepzero/shipkit --skill shipkit-user-instructionsgit clone --depth 1 https://github.com/stefan-stepzero/shipkitWrote 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/stefan-stepzero/shipkit/shipkit-user-instructions)<a href="https://agentmods.dev/skills/stefan-stepzero/shipkit/shipkit-user-instructions"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-user-instructions/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/stefan-stepzero/shipkit/shipkit-user-instructions"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-user-instructions.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.00038 | $0.03213 |
| Opus 5.5 | $0.00015 | $0.01285 |
| Sonnet 5.5 | $0.00008 | $0.00643 |
| Haiku 4.5 | $0.00004 | $0.00321 |
Grade A, and why
shipkit-user-instructions 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipkit-user-instructions - Task Tracking for Manual User Actions
Purpose: Prevent manual tasks from being lost in chat by maintaining a persistent JSON tracking file for tasks that require user action outside Claude's control.
What it does: Captures manual tasks the user must complete, tracks their status, and persists them in .shipkit/user-tasks.json — a structured JSON artifact readable by Claude, machine-readable by other tools, and the single source of truth for user action items.
Output format: JSON — follows the Shipkit artifact convention for dashboard integration.
When to Invoke
Auto-trigger scenarios (other skills invoke this):
- Package installation needed (implement)
- External service configuration required (Lemon Squeezy webhooks, API keys)
- Database migrations need running
- Deploy configuration needed
- Git repository setup required
Manual invocation:
- User says: "Track this task", "Add to my todo", "Remind me to..."
- Claude realizes: "I need the user to do X before I can continue"
Philosophy: If Claude can't do it directly, track it so it doesn't get forgotten.
Prerequisites
Optional:
.shipkit/directory (will create if missing)
No hard prerequisites - This skill can run anytime.
Process
Step 1: Confirm Task Details
Before creating task entry, ask user 2-3 questions:
-
What specific task needs to be done?
- "Set up Lemon Squeezy webhook?"
- "Configure webhook endpoint?"
- "Set environment variable?"
- (Let user describe or Claude infers from context)
-
Why is this needed?
- "For local webhook testing during development"
- "To enable payment processing"
- "To connect to production database"
-
How urgent is this?
- "Blocking me right now?" → High priority
- "Needed before deploy?" → Medium priority
- "Nice to have later?" → Low priority
-
Which phase does this block? (infer from context when possible)
- Read
.shipkit/why.jsonto determine current stage (poc, mvp, growth, scale) - If the task is needed for the current stage →
blocksPhase= current phase,blocking=true - If the task is needed for a future stage →
blocksPhase= that future phase,blocking=false - If unclear or not phase-specific →
blocksPhase=null,blockingbased on priority
- Read
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.
- 1mo ago First seen · 397 lines · 38 tokens per session scan A 89a924f8a34a
shipkit-user-instructions is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 3,213 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
wrap-up
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/ /log.md or career-vault/log.md, one entry per project touched, never to new-client. Use when the student…
pick-up
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when the student says pick up, where did I…
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…