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 sssstwee/tastedistill --skill shipgit clone --depth 1 https://github.com/sssstwee/tastedistillWrote 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/sssstwee/tastedistill/ship)<a href="https://agentmods.dev/skills/sssstwee/tastedistill/ship"><img src="https://agentmods.dev/badge/skills/sssstwee/tastedistill/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.1 | $0.00056 | $0.00674 |
| Opus 5 | $0.00028 | $0.00337 |
| Sonnet 5 | $0.00011 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00067 |
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 7d 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:
- tasted-ship — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship: Verify Before Delivery
Use this skill when an artifact exists and needs a delivery decision.
Prefix your first response line with ⚗️ inline, not as its own paragraph.
Before the workflow, apply ../../shared-rules/personalization.md for explicit TasteD/TasteDistill invocations.
Apply ../../shared-rules/runtime-hygiene.md when delivery verification uses helper scripts, browser checks, local servers, screenshots, traces, package artifacts, or other generated outputs.
Outcome Contract
- Outcome: a delivery decision grounded in current evidence.
- Done when: review findings, acceptance state, release state, or blockers are stated with proof.
- Evidence: worktree status, diff, tests, CI, manifests, docs, release artifacts, package contents, and remote state.
Worktree Safety
Before review, release, or destructive repository action:
git status --short --branch -uall
Treat modified, staged, and untracked files as user work. Do not reset, clean, stash, switch branches, or overwrite files unless the user explicitly asks for that operation.
Workflow
- Extract the delivery surface: diff, PR, release candidate, issue queue, package, or generated artifact.
- Read public project context: README, agent instructions, manifests, test config, CI, release docs, and changed files.
- Identify correctness, safety, compatibility, UX, and release risks.
- Run the narrowest meaningful verification first, then broader checks when needed.
- Fix only small, clearly scoped issues when the user authorized implementation.
- For release or publish actions, verify artifact contents and remote state before claiming success.
Coding Guardrails
For review and delivery, apply ../../shared-rules/coding-guardrails.md:
- Think before coding: identify any hidden assumptions in the diff or release path.
- Simplicity first: flag unnecessary abstraction, dependencies, or configuration surface.
- Surgical changes: every changed line should connect to the requested outcome; flag drive-by refactors separately.
- Goal-driven execution: acceptance should be tied to explicit checks, artifacts, or remote state.
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.
- 7d ago First seen · 63 lines · 56 tokens per session scan A cc7d8e284fa8
ship is a skill published in the GitHub repository sssstwee/tastedistill (2 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 674 once invoked, about $0.0003 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
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…