Borrowing it
Nothing to install: this file belongs to alfredoperez/speckit-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alfredoperez/speckit-companion/main/.claude/commands/ship.mdgit clone --depth 1 https://github.com/alfredoperez/speckit-companionWrote 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/commands/alfredoperez/speckit-companion/ship)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/ship"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/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/commands/alfredoperez/speckit-companion/ship"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/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.00014 | $0.01051 |
| Opus 5 | $0.00007 | $0.00526 |
| Sonnet 5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00001 | $0.00105 |
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 12d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current git status: !
git status --porcelain - Current version: !
node -p "require('./package.json').version" - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -10
Your task
Scope: the VS Code extension only. For the spec-kit extension (
speckit-extension/) use/publish-speckit-ext— it has its own README/CHANGELOG/extension.ymlversion and aspeckit-ext-v*tag.
Help the user prepare and package a new version of the extension.
Note: Arguments passed to this command are optional context/description (e.g., "refactoring and cleanup"). They are NOT the commit message or version number - those will be determined during the process.
Steps:
1. Code Quality Review
Check for unwanted code patterns:
- Search for
TODO,FIXME,XXXcomments - Search for
console.log,console.debug,debuggerstatements - Search for commented-out code blocks
- Flag any issues found and ask user if they should be addressed first
2. Documentation Check
Review if documentation needs updates:
- Check README.md for accuracy with current features
- Check CLAUDE.md for outdated instructions
- If recent commits touched UI or features, suggest documentation updates
- Ask user if any docs need updating before proceeding
3. Screenshot Check
If recent commits modified files in webview/ or src/features/:
- Suggest the user may want to update screenshots
- List files in
docs/screenshots/that might be outdated - This is informational only - proceed regardless
4. Commit Changes
If there are uncommitted changes:
- Show a summary of what will be committed
- Suggest a commit message using conventional commit format:
feat:- New featurefix:- Bug fixrefactor:- Code refactoring (no functional change)docs:- Documentation onlychore:- Maintenance tasksstyle:- Formatting, whitespace
- Include a body with bullet points for significant changes
- Ask user to confirm or modify the commit message
- Create the commit WITHOUT Claude Code attribution (no co-author, no generated-by footer)
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.
- 12d ago First seen · 119 lines · 14 tokens per session scan A 611b89a1c9b2
ship is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 1,051 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-30.
Other commands, from other repositories
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
devs-team
Parallel multi-lens critique of a solution design (the active spec if present, else the decision brief). Dispatches 5 engineering lenses, merges findings, reports a verdict. Report-only, never blocks.
quiz-gate
The ★-tap NUDGE before merging a significant+worthy gate PR: a 5-question quiz built from the ACTUAL diff+tests, handed to the operator's configured teacher seam. Three logged responses (engage/defer/wave); advisory, never must-pass. Gates the human's attention, not the merge.
review
Multi-agent code review with parallel validation.
pr-feedback-ingest
Turn PR feedback (Greptile, CI, bots, humans) into a structured traceable backlog aligned with TASKSTATE.md, DECISIONS.md, and IMPLEMENTATIONPLAN.md so the next execution step can be a narrow implement-approved-slice or a small planning touch without losing alignment. Corrective scope only. Use when a PR is open or…
review-hard
Review the current task changes for real correctness, safety, and maintainability risks before slice closure or PR prep, and recommend the smallest safe next step. Surfaces meaningful issues (not cosmetic feedback); not a replacement for external review systems. Returns no-op when the review would not materially…