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 tasted-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/tasted-ship)<a href="https://agentmods.dev/skills/sssstwee/tastedistill/tasted-ship"><img src="https://agentmods.dev/badge/skills/sssstwee/tastedistill/tasted-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/sssstwee/tastedistill/tasted-ship"><img src="https://agentmods.dev/badge/skills/sssstwee/tastedistill/tasted-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.00059 | $0.00676 |
| Opus 5 | $0.00030 | $0.00338 |
| Sonnet 5 | $0.00012 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
tasted-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 9d 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.
This is a copy
97% identical to ship — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 ships with it
1 file 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.
- 9d ago First seen · 63 lines · 59 tokens per session scan A 56597facbfcc
tasted-ship is a skill published in the GitHub repository sssstwee/tastedistill (2 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 676 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to ship, differing in 2 lines, and is treated as a copy.
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…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.