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/maxtechera/ship/criticnpx skills add maxtechera/ship --skill criticgit clone --depth 1 https://github.com/maxtechera/shipWhat 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.00026 | $0.01881 |
| Opus 5 | $0.00013 | $0.00941 |
| Sonnet 5 | $0.00005 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
ship-critic 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 2d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Critic — Self-Sufficient Evaluator
Deterministic evaluation contract for Ship Engine. A supervisor (or evaluator agent) runs this logic by following this document and the rubric files — no Python required.
Decision lock: critic runs before every gate and before any deliverable can move to verified.
REVISE blocks advancement unless a valid override is present.
Invocation Contract
| Argument | Description |
|---|---|
--ticket <ID> |
Linear ticket identifier to evaluate |
--stage <stage> |
Stage name for rubric lookup in deliverable mode (validate, strategy, awareness, lead-capture, nurture, closing, launch, measure) |
--deliverable <type> |
Artifact key being checked (validation_report, icp, ship_plan, etc.) |
--run-id <ID> |
Parent run ticket identifier (required for cross-check) |
--gate <gate> |
Gate mode selector (gate-v, gate-s, gate-l) |
--cross-check |
Run full cross-deliverable consistency review for the run |
--list-rubrics |
List available rubric names from supervisors/critic/rubrics/*.md |
Mode selection
--list-rubricsonly: print rubric names and stop--cross-checkrequires--run-id--gatemode requires--ticket- Deliverable mode requires
--ticket,--stage, and--deliverable - Invalid combination → return usage error
Rubric Loading Rules
Rubric directory: supervisors/critic/rubrics/
- Deliverable mode loads
rubrics/{stage}.md - Gate mode loads
rubrics/{gate}.md(e.g.,gate-v,gate-s,gate-l) - Cross-check mode loads
rubrics/cross-check.md
Missing rubric fallbacks:
- Deliverable mode:
No specific rubric found. Check that the artifact is linked, non-empty, and uses VoC language. - Gate mode:
Verify: (1) all hard-gate required fields present, (2) evidence links resolve, (3) kanban proof blocks complete, (4) all deliverables in this stage have critic PASS. - Cross-check mode: emit warning, skip with non-blocking exit.
What ships with it
13 files 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.
- rubrics/awareness.md 2.6 KB
- rubrics/closing.md 2.1 KB
- rubrics/cross-check.md 2.5 KB
- rubrics/gate-l.md 1.5 KB
- rubrics/gate-s.md 1.5 KB
- rubrics/gate-v.md 1.6 KB
- rubrics/intake.md 1.2 KB
- rubrics/launch.md 1.5 KB
- rubrics/lead-capture.md 1.7 KB
- rubrics/measure.md 1.8 KB
- rubrics/nurture.md 1.5 KB
- rubrics/strategy.md 1.6 KB
- rubrics/validate.md 2.2 KB
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.
- 2d ago First seen · 219 lines · 26 tokens per session scan A c8aa2baaa6f6
ship-critic is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,881 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.