Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Houseofmvps/ultraship/plugin install ultrashipWrote 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/houseofmvps/ultraship/deploy)<a href="https://agentmods.dev/skills/houseofmvps/ultraship/deploy"><img src="https://agentmods.dev/badge/skills/houseofmvps/ultraship/deploy.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.1 | $0.00033 | $0.03721 |
| Opus 5 | $0.00016 | $0.01861 |
| Sonnet 5 | $0.00007 | $0.00744 |
| Haiku 4.5 | $0.00003 | $0.00372 |
Grade A, and why
deploy 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 8d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy
Full pre-flight validation → deploy pipeline. Closes the audit-to-production loop.
Process
Step 1: Detect Deploy Target
Check project for deploy configuration:
vercel.jsonor.vercel/→ Vercel (git push)railway.tomlorrailway.json→ Railwayfly.toml→ Fly.iowrangler.toml→ Cloudflare Workers.github/workflows/with deploy steps → CI/CD pipelineDockerfile→ Container-based deploy- None found → ask user for deploy target
Step 2: Pre-Flight Checks
Run these checks BEFORE deploying (fail fast):
2a. Environment Validation
node ${CLAUDE_PLUGIN_ROOT}/tools/env-validator.mjs <project-directory>
If deploy_ready: false → STOP. Show missing vars. Do not deploy.
2b. Migration Safety
node ${CLAUDE_PLUGIN_ROOT}/tools/migration-checker.mjs <project-directory>
If deploy_safe: false → WARN. Show pending migrations. Ask user to confirm.
If a Supabase MCP server is connected (check your available tools for supabase), verify migration state against the actual database before deploying, not just the local migration files: list applied migrations and confirm the pending ones aren't already applied or in conflict. This catches the "migration ran on the dashboard but not in the repo" drift that breaks deploys.
If there are pending migrations, verify they are reversible:
- For Drizzle: check that corresponding
downSQL or rollback logic exists - For Prisma: confirm
prisma migrate resolvecan undo the migration - For Knex: verify the
down()function exists and is not empty - If the migration is destructive (dropping columns, renaming tables, deleting data) and has no rollback path → STOP. This is not safe to deploy without a manual rollback plan.
2c. Bundle Size Check
node ${CLAUDE_PLUGIN_ROOT}/tools/bundle-tracker.mjs <project-directory> --save
If bundle grew >50KB since last check → WARN. Show diff.
2d. Git Status Check for uncommitted changes:
git status --porcelain
If dirty working tree → WARN. Suggest committing first.
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.
- 8d ago First seen · 293 lines · 33 tokens per session scan A 21d99ddafc6c
deploy is a skill published in the GitHub repository Houseofmvps/ultraship (121 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 3,721 once invoked, about $0.0002 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 skills, from other repositories
version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
git-branchless
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.
atomic-issues-prs
Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don't use for single-change pushes or uncommitted change-sets.
post-merge-cleanup
Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.
git-workflow-and-versioning
Use when the user asks for release, version bump, changelog, or branch workflow beyond a single commit. Don't use for single commits or for publishing to a package registry.
lockstep-version-guard
Use when a human invokes the release gate to prove all 28 ODIN plugins share one canonical version. Emits a per-file comparison and exits non-zero on mismatch. Don't use to edit release metadata or for remote, credential, publish, deploy, or irreversible changes.