agentmods.dev

ship

ship is a skill for Claude Code, Codex from suboss87/FDEOps. It costs 29 tokens per session (245 once invoked), scanned A, original, MIT.

A controlled release checklist and procedure for putting a completed customer change into use. It covers required checks, recovery steps, authorization, and who will operate it afterward.

In plain words
What is it for?
Use it to prepare or carry out an approved deployment, verify its checks, identify the operating owner, and document what happens if the release fails.
Why use it?
It reduces the risk of deploying an unverified change or leaving nobody responsible for it. It also makes recovery plans explicit before release.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the fdeops plugin — 35 skills, 5 commands, 3 hooks shipped together

not rated 965repo +7 changed 10d ago A scan 29 tokens original MIT

Good fit Use it to prepare or carry out an approved deployment, verify its checks, identify the operating owner, and document what happens if the release fails.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/suboss87/fdeops/ship
View source ↗ suboss87/FDEOps fdeops.io
Install

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.

Any agent
npx skills add suboss87/FDEOps --skill ship
Clone the repo
git clone --depth 1 https://github.com/suboss87/FDEOps

Made for: Claude Code, Codex.

Or install fdeops, the plugin that ships this one along with the rest of its 35 skills, 5 commands, 3 hooks.

Wrote 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.

agentmods badge for ship

README.md
[![agentmods](https://agentmods.dev/badge/skills/suboss87/fdeops/ship/github.svg)](https://agentmods.dev/skills/suboss87/fdeops/ship)
Your own site
<a href="https://agentmods.dev/skills/suboss87/fdeops/ship"><img src="https://agentmods.dev/badge/skills/suboss87/fdeops/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.

agentmods 80×15 button for ship

Your own site · 80×15
<a href="https://agentmods.dev/skills/suboss87/fdeops/ship"><img src="https://agentmods.dev/badge/skills/suboss87/fdeops/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 245 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00245
Opus 5.5 $0.00012 $0.00098
Sonnet 5.5 $0.00006 $0.00049
Haiku 4.5 $0.00003 $0.00024

Measured 10d ago against content hash fdbbf24a9268, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 10d 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.

skills/ship/SKILL.md · 26 lines

What it actually says

ship

Purpose

A controlled release result with recovery and ownership.

Before investigating or acting:

  1. Read the task context contract.
  2. Read the method.

Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.

Principles

  • Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
  • If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
  • The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
  • Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.
Files

What ships with it

11 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.

Changes

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.

  1. 10d ago Changed fdbbf24a9268
  2. 28d ago Changed · +4 lines 545fa51462ad
  3. 1mo ago First seen · 22 lines · 29 tokens per session scan A 3ed6862aac29

Subscribe to this mod's changes

ship is a skill published in the GitHub repository suboss87/FDEOps (965 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 245 once invoked, about $0.0001 per session on Opus 5.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-09-16.

DevOps and cloudGit and workflowReleasesai-agentsclaude-skillscodex-skillcursorfdeforward-deployed-engineering
Related

Other skills, from other repositories

publish

Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.

code-yeongyu/oh-my-openagent · 68 tokens

pre-publish-review

Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…

code-yeongyu/oh-my-openagent · 161 tokens

get-unpublished-changes

Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.

code-yeongyu/oh-my-openagent · 38 tokens

log-changes

Use before creating, drafting, editing, or reviewing changelog entries (CHANGELOG.md or the project's equivalent), including when this is a subtask of implementing a feature, fixing a bug, or preparing a release and the user did not explicitly ask for this skill. Also use for requests to 'document this change' or 'add…

sergeyklay/.agents · 115 tokens

semantic-release-automation

Automate versioning, changelog, tags, GitHub Releases, and npm publishing from Conventional Commits with semantic-release. Use when setting up or debugging automated releases, wiring a .releaserc / release config and the plugin pipeline (commit-analyzer, release-notes-generator, changelog, npm, git, github), making…

stealth-factory/skills · 161 tokens

production-release-gating

Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel…

stealth-factory/skills · 191 tokens