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/andrewcigan/vibe-dev-plugin/shipnpx skills add andrewcigan/vibe-dev-plugin --skill shipgit clone --depth 1 https://github.com/andrewcigan/vibe-dev-pluginWrote 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/andrewcigan/vibe-dev-plugin/ship)<a href="https://agentmods.dev/skills/andrewcigan/vibe-dev-plugin/ship"><img src="https://agentmods.dev/badge/skills/andrewcigan/vibe-dev-plugin/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.00059 | $0.01660 |
| Opus 5 | $0.00030 | $0.00830 |
| Sonnet 5 | $0.00012 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship
Финальная доставка. Закрывает проект на текущей фазе или выпускает продукт.
Pre-flight checks
Check 1: Все фичи passing
# feature_list.json
all_done = all(f['state'] == 'passing' for f in features['active_list'] + features['up_next'])
captured_can_be_postponed = len(features['captured']) >= 0 # captured допустимо
Если есть active без passing → STOP, продолжать /feature.
Check 2: Build / Tests зелёные
./init.sh # должен пройти полностью
Validation Sample (≥90% gate)
Это главный gate ship. Без 90% — нет доставки.
Если нет валидационной выборки
validation-sample-builder subagent создаёт:
- 50-100 реалистичных сценариев (синтетика ≤20%)
- Категории: базовый интент 60-70% / edge 15-20% / error 10-15%
- Ground truth для каждого
- Бинарная оценка yes/no
→ docs/validation-sample.md + docs/validation-scenarios/S-*.md
Прогон
Запустить выборку на текущей сборке:
./validation-runs/run.sh
# или
python eval/run_validation.py
Результат:
- Pass rate: X%
- Per-category breakdown
- Failed scenarios → 5-Whys на каждый
Gate
- ≥90% pass → можно ship
- <90% → НЕ ship. Failed scenarios записать в backlog как новые фичи. Пользователю сказать прямо: «не дотянули до 90%, надо ещё N итераций».
Retrospective (полная)
Запустить skill claude-code-meta:retrospective или собрать вручную:
Что собирается
- Все error-journal записи проекта
- Все feedback_*.md из memory проекта
- Все stuck-statements
- Все decisions
Структура retrospective.md
# Retrospective: <project-name>
Date: YYYY-MM-DD
Duration: Started YYYY-MM-DD → Shipped YYYY-MM-DD (внешний календарь)
Features shipped: N (из N запланированных в Roadmap)
## Что получилось
- Features shipped: X
- Validation rate: Y%
- User satisfaction: <если есть метрика>
## Топ-3 повторяющиеся ошибки
1. <ошибка> — N раз — корневая причина — что зафиксировали в память
2. ...
3. ...
## Топ-3 удачных решений
1. <решение> — что сэкономило / улучшило
## Метрики харнеса
- Cold-start fail rate: X%
- /handoff compliance: Y%
- Auto-stuck triggers: Z (vs. ручных N)
- Cost overruns: <count>
- Recurrence rate: %
## Уроки для системы (предложение в ~/CLAUDE.md)
- <урок 1> — если confirm → промоушн в глобальные правила
- <урок 2>
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.
- 4d ago First seen · 177 lines · 59 tokens per session scan A f404877c5528
ship is a skill published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,660 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
harness
하네스를 구성합니다. 전문 에이전트를 정의하며, 해당 에이전트가 사용할 스킬을 생성하는 메타 스킬. (1) '하네스 구성해줘', '하네스 구축해줘' 요청 시, (2) '하네스 설계', '하네스 엔지니어링' 요청 시, (3) 새로운 도메인/프로젝트에 대한 하네스 기반 자동화 체계를 구축할 때, (4) 하네스 구성을 재구성하거나 확장할 때, (5) '하네스 점검', '하네스 감사', '하네스 현황', '에이전트/스킬 동기화' 등 기존 하네스 운영/유지보수 요청 시 사용.
kimchi
Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to…
compose
The mumei orchestrator. For new features, presents a vehicle picker — spec (full SDD workflow: clarification → requirements → design → tasks each auto-reviewed up to 3 iterations → single user approval → Wave-by-Wave implementation → 4-stage review) or plan (Claude Code plan-mode wrapper: hand off to plan mode…
peruse
Plan-vehicle review pipeline. Runs Stage 0 detector (semgrep + osv-scanner) plus security-reviewer and adversarial-reviewer in parallel against the current diff, validates each finding via issue-validator, aggregates a verdict, and writes a review JSON to .mumei/plans/ /reviews/ .json. Triggers when the user invokes…
release
Release a new version of the mumei repository. Invoke when the user gives an explicit release instruction ("release it", "/release", "patch release", "ship 0.2.0"). Takes no argument or "patch" / "minor" / "major" for a SemVer bump, or a direct version such as "0.2.0". Wraps any uncommitted changes into a single…
glean
This skill should be used BEFORE any feature design. It runs structured gleaning with the user — asking 5 high-leverage questions per round, up to 3 rounds, to extract Goal / Scope / Constraints / Edges / Done. Output is saved to .mumei/scratch/ .md and used as input for /mumei:compose. Triggers include "I want to add…