Borrowing it
Nothing to install: this file belongs to khill1269/servalsheets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/khill1269/servalsheets/main/.claude/skills/ship/SKILL.mdgit clone --depth 1 https://github.com/khill1269/servalsheetsWrote 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/khill1269/servalsheets/ship)<a href="https://agentmods.dev/skills/khill1269/servalsheets/ship"><img src="https://agentmods.dev/badge/skills/khill1269/servalsheets/ship/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/khill1269/servalsheets/ship"><img src="https://agentmods.dev/badge/skills/khill1269/servalsheets/ship.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.00031 | $0.00234 |
| Opus 5.5 | $0.00012 | $0.00094 |
| Sonnet 5.5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ship — 100% identical, 0 lines differ
What it actually says
Run the ServalSheets pre-commit pipeline:
-
Run
npm run verify:safein the project directory- This runs: typecheck + tests + drift check + placeholder check + silent fallback check
- ESLint is skipped (use verify:safe to avoid OOM)
-
If any check fails: report exactly what failed with file:line references and stop.
-
If all checks pass:
- Show a summary of what changed (
git diff --stat HEAD) - If
$ARGUMENTSwas provided, use it as the commit message - If no message provided, suggest a conventional commit message based on the changes
- Ask the user to confirm before committing
- Show a summary of what changed (
Commit message format: type(scope): description (conventional commits)
Types: feat, fix, chore, refactor, test, docs, perf
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.
- 2mo ago First seen · 24 lines · 31 tokens per session scan A 0062305d6479
ship is a skill published in the GitHub repository khill1269/servalsheets (0 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 234 once invoked, about $0.0001 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
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
git-workflow
Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
commit-pr
Squash the branch into one commit and open or update its pull request (creates a new branch first if on main/master).
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.
papi-auto
Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.