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/povvo/claudikins-kernel/shipgit clone --depth 1 https://github.com/povvo/claudikins-kernelWrote 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/commands/povvo/claudikins-kernel/ship)<a href="https://agentmods.dev/commands/povvo/claudikins-kernel/ship"><img src="https://agentmods.dev/badge/commands/povvo/claudikins-kernel/ship.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.02855 |
| Opus 5 | $0.00013 | $0.01427 |
| Sonnet 5 | $0.00005 | $0.00571 |
| Haiku 4.5 | $0.00003 | $0.00285 |
Grade A, and why
claudikins-kernel: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 4d 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claudikins-kernel:ship Command
You are orchestrating a shipping workflow that takes verified code to production with human approval at every stage.
Flags
| Flag | Effect |
|---|---|
--branch NAME |
Ship specific branch (default: current) |
--target BRANCH |
Target branch for merge (default: main) |
--skip-docs |
Skip documentation updates (Stage 3) |
--squash |
Squash commits into single commit |
--preserve |
Preserve commit history |
--dry-run |
Preview ship without merging |
--session-id ID |
Resume previous session by ID |
--resume |
Resume from last checkpoint |
--status |
Show current ship status |
--list-sessions |
Show available sessions for resume |
Merge Strategy
JQ merge - documentation outputs are combined with jq -s 'add'.
Philosophy
"Ship with confidence, not hope." - Shipping philosophy
- claudikins-kernel:ship is the final gate after claudikins-kernel:verify passes
- GRFP-style: section-by-section approval at every stage
- Human decides final merge - no auto-merging
- Code integrity validation ensures we ship what was verified
- Documentation is part of shipping, not optional
State Management
State file: .claude/ship-state.json
{
"session_id": "ship-YYYY-MM-DD-HHMM",
"verify_session_id": "verify-YYYY-MM-DD-HHMM",
"verified_commit": "abc123...",
"target": "main",
"started_at": "ISO timestamp",
"status": "initialising|shipping|completed|failed",
"phases": {
"pre_ship_review": { "status": "pending|APPROVED|SKIPPED" },
"commit_strategy": { "status": "pending|APPROVED", "strategy": null },
"documentation": { "status": "pending|COMPLETED|SKIPPED" },
"pr_creation": { "status": "pending|CREATED", "pr_number": null },
"merge": { "status": "pending|MERGED", "sha": null }
},
"unlock_merge": false,
"cleanup": {
"branches_deleted": []
}
}
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.
- 4d ago First seen · 550 lines · 25 tokens per session scan A 89c1611720da
claudikins-kernel:ship is a command published in the GitHub repository povvo/claudikins-kernel (126 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 2,855 once invoked, about $0.0001 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
release
Project-local release pipeline — bump version, regenerate CHANGELOG from commits since last tag, update README docs for new features (with concrete examples + argument explanations), commit + tag + push, open a PR if on a non-main branch, then hand off a manual npm publish (no token configured yet).
release
Release a new version of recall.
ship
Complete PR workflow from commit to production with validation.
release
Generate changelog, bump version, and create git tag.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.