A pre-release verification and checklist workflow for a project. It runs quality, responsive-layout, and no-emoji checks, then drafts updates for the README version information and changelog.

Use it before a release to verify the project at several screen widths and prepare the release notes and checklist.

It catches release-blocking problems before publishing and separates verification from destructive actions such as tagging or publishing.

ship — Skill for Claude Code by plugin87/ux-ui-agent-skills

About the project

UX/UI Agent Skills is a set of instructions, design tokens, reusable components, accessibility rules, and design-system references that guide Claude in producing interface designs and code. It is intended for developers and designers who want framework-independent, token-based UI work with accessibility checks. The catalogue entries package these UX, UI, component, and validation workflows as Claude Code skills and related add-ons.

plugin87/ux-ui-agent-skills · 2,012 stars · on GitHub · plugin87.github.io

Install

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.

Any agent

npx skills add plugin87/ux-ui-agent-skills --skill ship

Clone the repo

git clone --depth 1 https://github.com/plugin87/ux-ui-agent-skills

Made for: Claude Code.

Or install ux-ui-agent-skills, the plugin that ships this one along with the rest of its 25 skills, 1 command, 1 agent, 3 hooks, 2 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/plugin87/ux-ui-agent-skills/ship/github.svg)](https://agentmods.dev/skills/plugin87/ux-ui-agent-skills/ship)

Your own site

<a href="https://agentmods.dev/skills/plugin87/ux-ui-agent-skills/ship"><img src="https://agentmods.dev/badge/skills/plugin87/ux-ui-agent-skills/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/plugin87/ux-ui-agent-skills/ship"><img src="https://agentmods.dev/badge/skills/plugin87/ux-ui-agent-skills/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 531 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00034	$0.00531
Opus 5.5	$0.00014	$0.00212
Sonnet 5.5	$0.00007	$0.00106
Haiku 4.5	$0.00003	$0.00053

Measured 10d ago against content hash b0cdad9a1c9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 10d 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.

.claude/skills/ship/SKILL.md · 36 lines

What it actually says

Step 0 — is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

Gate first, then prepare the release. Do nothing destructive without explicit confirmation (no tag, no publish) — this command verifies and drafts only.

Quality gate (must be fully green before continuing):
- node ${CLAUDE_SKILL_DIR}/../../../scripts/accuracy_report.mjs — report the real N/N.
- node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_responsive.mjs examples — no overflow at 280/320/414.
- python3 ${CLAUDE_SKILL_DIR}/../../../scripts/check_no_emoji.py — UI + taste + instruction surface. If anything fails, stop and fix; do not proceed to the checklist.
Release checklist (per the project release rule):
- Update README.md: version badge, "current" line, and changelog entry.
- Confirm the bump level (major/minor/patch) with the user — it is their call.
- Confirm examples/apple-home stays gitignored (local IP).
- List the commits since the last tag so the changelog is accurate.
Output a ready-to-review summary: the green N/N line, the proposed version, and the drafted changelog entry. Wait for the user to approve before any git tag / publish step.

Changes

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.

10d ago First seen · 36 lines · 34 tokens per session scan A b0cdad9a1c9e

Subscribe to this mod's changes

ship is a skill published in the GitHub repository plugin87/ux-ui-agent-skills (2,012 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 531 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-10-07.

Claude Code Git and workflow Releases Testing accessibility ai-agents claude claude-skills component-library

multi-version-behavior-comparator

Compare behavior across multiple versions of programs or repositories. Use when you need to analyze how functionality changes between versions, identify regressions, compare outputs and exceptions, or validate upgrades. The skill compares execution behavior, test results, outputs, exceptions, and observable states…

ArabelaTso/Skills-4-SE · 98 tokens

done

End-of-session shipping gate — "prove it works, then ship it." Runs an evidence checklist (full test suite, lint/typecheck, build, and actually running the change — output quoted, never asserted), then a fresh-context two-stage review by a sub-agent that sees only the diff and the spec: spec-compliance first…

duthaho/skillhub · 204 tokens

production-build-verification

Build the standalone Forge artifact with strict routing inputs and confirm its static output exists.

OKHP3/skillz · 21 tokens

dev-ship

Fechamento de feature — verificação goal-backward antes de declarar pronto. Roda Must-Haves do PLAN.md, executa o demo script, revisa o diff completo procurando bugs e restos (debug logs, TODOs, código morto), passa lente de segurança nos arquivos tocados, escreve SUMMARY.md e arquiva o plano. Use quando o usuário…

calneymgp/solodev · 121 tokens

release-checklist

Generates a comprehensive pre-release validation checklist for software versions covering build verification, deployment readiness, and release risk. Use when preparing to release a product version or when the user mentions release checklist or pre-release validation.

tranhieutt/software_development_department · 46 tokens

release-readiness

The go/no-go gate before shipping — a structured launch checklist across security, data, legal, operations, performance, accessibility and rollback, producing an explicit ship or do-not-ship decision with named blockers. Use when the user says "ready to launch", "go live", "ship it", "pre-launch", "launch checklist"…

Kin9Zeus/senior-engineer-skills · 124 tokens