Borrowing it
Nothing to install: this file belongs to eddiesanjuan/markupr. 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/eddiesanjuan/markupr/main/.claude/commands/ship.mdgit clone --depth 1 https://github.com/eddiesanjuan/markuprWrote 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/eddiesanjuan/markupr/ship)<a href="https://agentmods.dev/commands/eddiesanjuan/markupr/ship"><img src="https://agentmods.dev/badge/commands/eddiesanjuan/markupr/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/eddiesanjuan/markupr/ship"><img src="https://agentmods.dev/badge/commands/eddiesanjuan/markupr/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.00000 | $0.01104 |
| Opus 5.5 | $0.00000 | $0.00442 |
| Sonnet 5.5 | $0.00000 | $0.00221 |
| Haiku 4.5 | $0.00000 | $0.00110 |
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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship -- Full Release Prep
Run a comprehensive release readiness assessment for markupr. This goes beyond release-check by generating changelogs, scanning for tech debt markers, checking dependency health, and producing a final go/no-go verdict.
Instructions
1. Run the Full Test Suite with Coverage
cd ~/Projects/markupr && npm run test:ci -- --run
Report: total tests, passed, failed, skipped, and coverage percentages for lines/functions/branches/statements. Compare against the thresholds in vitest.config.ts (lines 8%, functions 30%, branches 55%, statements 8%). Flag if any threshold is missed.
2. Lint and Type Check
cd ~/Projects/markupr && npm run lint 2>&1; npm run typecheck 2>&1
Report error count and warning count separately. Zero errors required for ship. Warnings are acceptable but list them.
3. Version Consistency Check
Read and compare the version string across all of these sources:
package.json"version"fieldCLAUDE.md**Version:**lineelectron-builder.yml(check ifartifactNamepatterns reference a hardcoded version)- Any version constant in
src/main/index.tsorsrc/shared/if present
Flag any mismatch. All must agree before shipping.
4. Build Validation
Run all three build targets and confirm each succeeds:
cd ~/Projects/markupr && npm run build 2>&1
This runs node scripts/build.mjs which builds desktop (electron-vite), CLI (esbuild), and MCP (esbuild). All three must succeed. Report output sizes for:
dist/main/index.mjsdist/cli/index.mjsdist/mcp/index.mjsdist/renderer/total size
5. Git Status and Unpushed Commits
cd ~/Projects/markupr && git status --short 2>&1
cd ~/Projects/markupr && git log origin/main..HEAD --oneline 2>&1
Flag: uncommitted changes, untracked files, unpushed commits. The working tree should be clean and fully pushed before a release.
6. Changelog Generation
cd ~/Projects/markupr && git log $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~30)..HEAD --oneline --no-merges
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.
- 1mo ago First seen · 132 lines · 0 tokens per session scan A 7796a1be5247
ship is a command published in the GitHub repository eddiesanjuan/markupr (18 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,104 tokens. 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
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.