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/benshapyro/cadre-devkit-claude/shipgit clone --depth 1 https://github.com/benshapyro/cadre-devkit-claudeWrote 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/commands/benshapyro/cadre-devkit-claude/ship)<a href="https://agentmods.dev/commands/benshapyro/cadre-devkit-claude/ship"><img src="https://agentmods.dev/badge/commands/benshapyro/cadre-devkit-claude/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.00005 | $0.00415 |
| Opus 5 | $0.00003 | $0.00208 |
| Sonnet 5 | $0.00001 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 4d 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.
What it actually says
Ship Command
Commit validated changes with proper formatting.
Pre-Ship Checks
Verify validation passed:
- Has
/validatebeen run? - Were there any failures?
Check git status:
!git status
Gather Information
Staged changes:
!git diff --staged --stat
Recent commits for style:
!git log --oneline -5
Current branch:
!git branch --show-current
Generate Commit
Analyze Changes
Based on the diff, determine:
- Type: feat, fix, docs, style, refactor, test, chore
- Scope: Component or module affected
- Subject: What the commit does (imperative mood)
Commit Format
type(scope): subject
Body explaining why this change was made.
- Detail 1
- Detail 2
🤖 Generated with Claude Code
Co-Authored-By: Claude <[email protected]>
If Argument Provided
Use $1 as the commit message subject.
Execute Commit
Stage all changes (if not already staged): Ask user before staging untracked files.
Create commit:
git commit -m "$(cat <<'EOF'
[generated message]
EOF
)"
Verify success:
!git log -1 --oneline
Report
## Ship Complete
✅ Commit created successfully
**Commit:** [hash]
**Message:** [subject]
**Files changed:** [count]
### Next Steps
- Push to remote: `git push`
- Create PR: `gh pr create`
- Continue developing
Safety Rules
- Never force push
- Never push to main/master without approval
- Always verify commit authorship before amend
- Report any pre-commit hook failures
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.
- 4d ago First seen · 97 lines · 5 tokens per session scan A 64e6fc87f997
ship is a command published in the GitHub repository benshapyro/cadre-devkit-claude (9 stars, last pushed 9mo ago), licensed MIT. It adds 5 tokens to every session and 415 once invoked, about $0.0000 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 commands, from other repositories
speckit.aftercode
Automatically execute the subsequent code delivery pipeline: skilltypesync → changelog → commit → prgenerate, in strict sequential order.
commit
Automatically generate commit message based on changes and push to current branch. Analyzes git diff to create meaningful commit following conventional commits format. Optionally creates and pushes a git tag.
changelog-update
Actualiza CHANGELOG.md automáticamente analizando los commits desde la última versión/release. Clasifica los cambios por tipo (feat, fix, docs, etc.) usando los commits convencionales del workspace. Opcionalmente sugiere bump de versión semántica. Delega la redacción final a tech-writer.
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
publish-essay
Create MDX file, commit to id8labs-hub repo, and trigger Vercel deploy.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.