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 commands/marcusgoll/spec-flow/shipgit clone --depth 1 https://github.com/marcusgoll/Spec-FlowWhat 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.00013 | $0.09631 |
| Opus 5 | $0.00006 | $0.04816 |
| Sonnet 5 | $0.00003 | $0.01926 |
| Haiku 4.5 | $0.00001 | $0.00963 |
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 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 — 1,218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship — Unified Deployment Orchestrator (Thin Wrapper)
v11.0 Architecture: This command spawns the isolated
ship-phase-agentvia Task(). Deployment operations run in isolated context with question batching for production approval.
Active Feature: !ls -td specs/[0-9]*-* 2>/dev/null | head -1 || echo "none"
Interaction State: !cat specs/*/interaction-state.yaml 2>/dev/null | head -10 || echo "none"
Deployment Model: !test -f .github/workflows/deploy-staging.yml && echo "staging-prod" || (git remote 2>/dev/null && echo "direct-prod" || echo "local-only")
Architecture (v11.0 - Phase Isolation):
/ship → Task(ship-phase-agent) → Q&A for prod approval → deployment
Agent responsibilities:
- Auto-detect deployment model (staging-prod, direct-prod, local-only)
- Execute pre-flight validation
- Deploy to staging (auto-proceed)
- Request approval for production deployment (returns question)
- Create GitHub release
- Record deployment metadata
Deployment Models (auto-detected):
-
staging-prod: Automated staging validation before production (recommended)
- Detection: Git remote + staging branch +
.github/workflows/deploy-staging.yml - Workflow: pre-flight + optimize (parallel) → deploy-staging → automated validation → deploy-prod → finalize
- Detection: Git remote + staging branch +
-
direct-prod: Direct production deployment without staging
- Detection: Git remote + no staging branch
- Workflow: pre-flight + optimize (parallel) → deploy-prod → finalize
-
local-only: Local build and integration only
- Detection: No git remote
- Workflow: pre-flight + optimize (parallel) → build-local → merge to main → finalize
Automation Features:
- Pre-flight + optimize run in parallel (saves ~10 minutes)
- Zero manual gates (removed /preview, interactive version selection)
- Auto-generated validation reports (E2E, Lighthouse, rollback tests)
- Platform API-based deployment ID extraction (no log parsing)
- Auto-fix CI failures via GitHub Actions
Arguments:
- (empty): Start deployment workflow from beginning
continue: Resume from last completed phase (if failure occurred)status: Display current deployment status and exitrollback [version]: Rollback to previous deployment version (v10.14+)recover: Recover corrupted state.yaml from git history (v10.14+)budget: Display deployment quota status--auto: Full autopilot mode - skip prompts, auto-merge when CI passes, continue to finalize (v11.7)
Dependencies: Requires completed /implement phase
Timing: 25-35 minutes fully automated
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 · 1,218 lines · 13 tokens per session scan A 71c17fe222a5
ship is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 9,631 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
test-pr-docker
Test PR with Docker image build workflow.
r-util-ci-gen
Generate a GitHub Actions CI workflow from the project's test.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
sync-linear
Sync current work with Linear ticket status.
quality-gate
Command "quality-gate" from VoDaiLocz/kilo-kit-mcp, covering ✅ quality gate command, workflow, gates, gate 1: pre-execution and gate 2: per-behavior.