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 bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/ship)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/ship"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/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/skills/bdfinst/agentic-dev-team/ship"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/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.00119 | $0.03402 |
| Opus 5.5 | $0.00048 | $0.01361 |
| Sonnet 5.5 | $0.00024 | $0.00680 |
| Haiku 4.5 | $0.00012 | $0.00340 |
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 17d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Role: orchestrator. This command chains the existing pipeline skills end to end; it does not implement, review, or merge anything itself — each phase is delegated to the skill that owns it, and the existing human approval gates are preserved.
You have been invoked with the /ship command.
Orchestrator constraints
- Delegate every phase. Call the owning skill (
/specs,/plan,/build,/code-review,/pr); do not re-implement their logic here. - Honor the human gates. Do not advance past a gate without explicit approval — this command sequences phases, it does not remove their review points.
- Confirm the approach first. Before planning, screen the request against
${CLAUDE_PLUGIN_ROOT}/knowledge/decision-defaults.mdand confirm any ambiguous high-reversal-cost axis (replace-vs-merge, format fidelity, migrate-vs-edit-stub, scope) in one batch. - Be concise. Report each phase's outcome and the next gate, nothing more.
- Agent-dispatch capability is a pipeline-wide precondition, enforced by the delegated skills, not duplicated here (issue #1461).
/plan(Step 5b),/build(Steps 3, 4, 6), and/code-review(Step 4) each independently confirm theAgent/Tasktool is present before dispatching any review agent, and each hard-fails — STOP, no self-applied review, no gate file written — when it is missing./shipdoes not re-check or restate that logic; if a delegated phase halts on missing dispatch capability,/shipreports that halt and stops with it (per constraint 2, "Honor the human gates") rather than working around it or advancing past the phase that failed. - Idempotent per issue. Never re-run the pipeline for an issue that is
already shipped or in-flight. The Step 1 resume guard decides this from
durable tracker/PR state — not conversation memory — so a re-fired command
string (e.g. a
ScheduleWakeup/loop prompt that repeats) lands on resume/monitor, not a second spec→plan→build→PR pass.
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.
- 17d ago Changed · -64 lines f3bc7d4bc867
- 1mo ago First seen · 305 lines · 119 tokens per session scan A 5fc089f32ac9
ship is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 119 tokens to every session and 3,402 once invoked, about $0.0005 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-03.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.