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/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/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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.01290 |
| Opus 5.5 | $0.00025 | $0.00516 |
| Sonnet 5.5 | $0.00012 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
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 14d 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 — 135 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
Invoke the workflow-preflight skill with the Skill tool, passing --fix as its arguments, to run the typecheck, lint, format, security and test checks. With --fix, preflight applies the auto-fixes it can (lint --fix, format, etc.) without asking and re-runs the failing checks.
- If preflight applied fixes, 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 issues remain that preflight couldn't fix, STOP HERE and report them
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.
- 14d ago Changed · -3 lines 17cfb6caaf4f
- 18d ago Changed · -3 tokens per session ef5dedd94e32
- 1mo ago 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 (35 stars, last pushed 14d ago), licensed MIT. It adds 62 tokens to every session and 1,290 once invoked, about $0.0002 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-06.
Other skills, from other repositories
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
verify-commit
Verify that commits for a GitHub issue include tests and that those tests fail without the implementation changes. Given an issue ID, finds commits, checks for test files, then reverts src/main changes and runs the tests to confirm they fail.
verify-akashic-plugin
A plugin acceptance skill that commits a plugin, installs it into the running application, checks its status, and uses it once to confirm whether it works.
coverage-drop-investigator
Use when test coverage has dropped and you need to find which changes caused it and what tests to add. Traces coverage regressions to specific commits and files.