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 commands/stefan-jansen/claude-code-toolkit/shipgit clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkitWhat 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.00007 | $0.00440 |
| Opus 5 | $0.00003 | $0.00220 |
| Sonnet 5 | $0.00001 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
ship 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 3d 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.
What it actually says
Work Delivery
Validate, document, and deliver completed work.
Options: $ARGUMENTS
Modes
--preview: Show what would be delivered (no changes)--pr: Create pull request with documentation--commit: Commit to current branch--deploy: Prepare for production deployment
Process
-
Readiness Check
- Find active work unit
- Verify all tasks completed
- Check git status (clean/dirty)
-
Quality Validation
- Run test suite (>80% coverage required)
- Execute linting/type checking
- Security scan
- Build verification
-
Generate Documentation
- DELIVERY.md: What was built, architecture, metrics
- CHANGELOG.md: Added/changed/fixed
- DEPLOYMENT.md: Prerequisites, steps, rollback
-
Execute Delivery
- PR: Generate description, include metrics, link issues
- Commit: Stage changes, create conventional commit
- Deploy: Final validation, env config, monitoring setup
-
Memory Reflection
- Analyze work unit for learnings
- Prompt for
/memory-updateto capture:- Decisions made
- Lessons learned
- New conventions
- Dependencies added
-
Archive Work Unit
- Update status to completed
- Record delivery method
- Move to archives
Quality Gates
All must pass:
- ✅ Tests pass with >80% coverage
- ✅ No critical lint/security issues
- ✅ Documentation complete
- ✅ Build successful
Commit Format
feat|fix|docs: Brief description
Detailed explanation of changes.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
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.
- 3d ago First seen · 74 lines · 7 tokens per session scan A 6f2e1bf3a3fd
ship is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (85 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 440 once invoked, about $0.0000 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-30.
Other commands, from other repositories
OpenSpec: Archive
name: OpenSpec: Archive description: Archive a deployed OpenSpec change and update specs. category: OpenSpec tags: [openspec, archive].
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
harn-release
Run the tag-first Harn release workflow.
changelog
Create engaging changelogs for recent merges to main branch.
enrich
Enrich project memory by mining 100 recently merged PRs: extracts decisions, conventions, gotchas, and architectural facts from PR discussions, review comments, and PR bodies.
reportloop
Interactively walk through all issues in REVIEWREPORT.md: explains each issue, asks to fix or skip, handles follow-up questions, and applies fixes one by one in severity order.