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/sakhilchawla/skillkit/shipnpx skills add sakhilchawla/skillkit --skill shipgit clone --depth 1 https://github.com/sakhilchawla/skillkitWrote 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/sakhilchawla/skillkit/ship)<a href="https://agentmods.dev/skills/sakhilchawla/skillkit/ship"><img src="https://agentmods.dev/badge/skills/sakhilchawla/skillkit/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.00021 | $0.00382 |
| Opus 5 | $0.00010 | $0.00191 |
| Sonnet 5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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
Ship
Automated end-to-end shipping workflow.
Pre-flight
- Verify NOT on main/master — STOP if so
- Verify there are changes to ship (staged, unstaged, or unpushed commits)
Step 1: Sync with main
git fetch origin && git merge origin/main --no-edit
If merge conflicts, STOP and report them.
Step 2: Run checks
Detect project type and run appropriate commands:
| File | Test | Lint |
|---|---|---|
| package.json | npm test | npm run lint |
| Makefile | make test | make lint |
| pyproject.toml | pytest | ruff check . |
| Cargo.toml | cargo test | cargo clippy |
| go.mod | go test ./... | golangci-lint run |
STOP on any failure.
Step 3: Self-review diff
Scan git diff origin/main...HEAD for: debug code, TODO/FIXME, hardcoded secrets, large binaries.
If found, report and STOP.
Step 4: Commit (if uncommitted changes)
Stage and commit. Use $ARGUMENTS as message or auto-generate conventional commit.
Step 5: Push
git push -u origin <current-branch>
Step 6: Create PR
gh pr create --fill (fall back to URL if gh not installed)
Failure Protocol
On ANY failure: print error, print which step failed, do NOT continue, do NOT use --force or --no-verify.
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.
- 3d ago First seen · 53 lines · 21 tokens per session scan A b5617605cad5
ship is a skill published in the GitHub repository sakhilchawla/skillkit (6 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 382 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-31.
Other skills, from other repositories
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…
commit-changes
Create a git commit for the current changes. Use when asked to commit changes, make a commit, generate a commit message, or commit the current worktree with optional user-provided context.
commit
Create a signed git commit following Conventional Commits, after running /pre-commit and /changelog when appropriate.
commit
Read this skill before making git commits.