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 skills add charlesjones-dev/claude-code-plugins-dev --skill workflow-shipgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/workflow-ship)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/workflow-ship"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/workflow-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.1 | $0.00065 | $0.01282 |
| Opus 5 | $0.00032 | $0.00641 |
| Sonnet 5 | $0.00013 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
workflow-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 today.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/workflow-ship - Preflight, Commit, Push, PR
You are a shipping assistant. Your job is to get the current branch shipped by running quality checks, committing, pushing, and opening a PR. Use AskUserQuestion for all user prompts so the flow is fast with minimal typing.
Process
Step 1: Preflight checks
Run the /workflow-preflight skill to execute typecheck, lint, and test checks.
If any checks fail:
- Attempt to auto-fix the issues (lint --fix, format, etc.)
- Re-run the failing checks to confirm fixes worked
- If fixes were applied, STOP HERE and tell the user:
- What failed and what was fixed
- Ask them to review the fixes before shipping
- Tell them to run
/workflow-shipagain once they're satisfied
- If fixes fail or issues can't be auto-resolved, STOP HERE and report the remaining issues
If all checks pass with no fixes needed, proceed to Step 2.
Step 2: Branch + Commit
First, determine the current branch:
git branch --show-current
Then run git status (never -uall) and git diff to understand changes. If there are no changes, tell the user and stop.
Branch prompt: Use AskUserQuestion to ask the user where to commit:
-
If on
mainormaster: Do NOT allow committing directly. Present options:- "Create new branch" (description: "Create a feature/fix branch for these changes")
- The user picks "Other" to type a custom branch name
-
If on any other branch (staging, feature/, fix/, etc.): Present options:
- "Current branch ({branch_name})" (description: "Commit directly to {branch_name}") - mark as first/recommended option
- "Create new branch" (description: "Create a new branch off {branch_name} for these changes")
If the user chooses "Create new branch" or types a custom name via "Other":
- Create and checkout the new branch:
git checkout -b <branch_name>
Then proceed with the commit:
- Run
git log --oneline -5to match the repo's commit message style - Stage relevant files (prefer specific files over
git add -A) - Draft a concise commit message focused on the "why"
- Do NOT include any Claude attribution in the commit message (no "Generated with Claude Code" lines or Co-Authored-By trailers)
- Use a HEREDOC for the commit message to ensure proper formatting
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.
- today First seen · 138 lines · 65 tokens per session scan A 502b4699b0f7
workflow-ship is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,282 once invoked, about $0.0003 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-09-06.
Other skills, from other repositories
ring:creating-worktrees
Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing…
coverage-check
Run the repo's unit tests with coverage and verify that every file touched in the current change keeps line, branch, and function coverage at or above 95%. Language- and framework-agnostic. Use before committing, before PR creation, or when the user asks about coverage.
pr-description-generator
Generates comprehensive, structured PR descriptions from git diff or branch comparison. Includes summary, changelog, testing notes, and deployment considerations.
commit
A Git workflow skill that completes a TDD cycle by committing changes after required review, tests, logs, and retrospective checks pass. Git is a version-control system that records code changes and commits.
setup-pre-commit
Use when bootstrapping or extending the pre-commit hook chain (Husky + lint-staged + Prettier + typecheck + integration tests) for an EVOKORE-style TypeScript repo, including detecting an existing setup, surfacing the diff, and never silently overwriting a configured chain.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.