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 skills/bryanweaver/claude-agent-kit/team-shipnpx skills add bryanweaver/claude-agent-kit --skill team-shipgit clone --depth 1 https://github.com/bryanweaver/claude-agent-kitWrote 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/bryanweaver/claude-agent-kit/team-ship)<a href="https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-ship"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-ship.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 | $0.00024 | $0.01123 |
| Opus 5 | $0.00012 | $0.00562 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
team-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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship — Build and Deploy Features
Implement a new feature or enhancement from start to production.
Feature to implement: $ARGUMENTS
Execution
With Agent Teams (recommended)
Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Create a team and spawn teammates:
- Create team named
ship-<feature-slug> - Define acceptance criteria before implementation begins:
- Break the feature into testable behaviors and success conditions
- Write these criteria into claude-progress.json so all agents share the same definition of "done"
- This prevents self-evaluation bias where agents confidently approve their own mediocre work
- Spawn teammates: shipper, full-stack-developer, database-admin (if data changes needed), reviewer, documentor
Create the following task list with dependencies:
| # | Task | Owner | Blocked By |
|---|---|---|---|
| 1 | Create feature branch feature/<name> from main |
shipper | — |
| 2 | Implement the feature end-to-end | full-stack-developer | 1 |
| 3 | Implement database/data layer changes (if needed) | database-admin | 1 |
| 4 | Commit all changes with conventional message | shipper | 2, 3 |
| 5 | Review implementation for security, bugs, performance | reviewer | 4 |
| 6 | Fix review findings (only if reviewer returns REQUEST_CHANGES) |
full-stack-developer + database-admin | 5 |
| 7 | Run full test suite | shipper | 5 (verdict APPROVE or APPROVE_WITH_WARNINGS) |
| 8 | Fix regressions (if tests fail — loop back to 7) | full-stack-developer | 7 |
| 9 | Update documentation for feature changes | documentor | 7 |
| 10 | Deploy and create PR to main | shipper | 7, 9 |
Parallelism:
- Tasks 2 and 3 run simultaneously after task 1.
- If task 6 fires, application and data fixes can run simultaneously.
Loops:
- Review gate: If task 5 returns
REQUEST_CHANGES, create task 6 (fix findings) and re-run task 5. Repeat until the verdict isAPPROVEorAPPROVE_WITH_WARNINGS. Tasks 7+ stay blocked until the gate clears. - Test gate: If task 7 finds failures, create task 8 (fix regressions) and re-run task 7.
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.
- 5d ago First seen · 83 lines · 24 tokens per session scan A f0e1edd78f03
team-ship is a skill published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 1,123 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-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…