shipwright: Skill for Claude Code

.claude/skills/port-bash-command/SKILL.md

port-bash-command is a skill for Claude Code from sethdford/shipwright. It costs 52 tokens per session (772 once invoked), scanned A, original, MIT.

A guided task for porting one Shipwright Bash command to TypeScript while preserving its existing behavior. It uses the Bash test suite as the comparison standard and asks for tests first, which is called test-driven development (TDD).

In plain words
What is it for?
Use it to migrate a listed command, create missing behavior tests, implement the TypeScript command, register its aliases and route, and verify Bash-versus-TypeScript parity.
Why use it?
It reduces the risk that a migration changes arguments, output, exit codes, or files written. The parity tests show whether the TypeScript command still behaves like Bash.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is sethdford/shipwright's own configuration. It tells Claude Code how to work on shipwright itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything shipwright configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sethdford/shipwright. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sethdford/shipwright/main/.claude/skills/port-bash-command/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/sethdford/shipwright

Made for: Claude Code.

Wrote 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.

agentmods badge for port-bash-command

README.md
[![agentmods](https://agentmods.dev/badge/skills/sethdford/shipwright/port-bash-command/github.svg)](https://agentmods.dev/skills/sethdford/shipwright/port-bash-command)
Your own site
<a href="https://agentmods.dev/skills/sethdford/shipwright/port-bash-command"><img src="https://agentmods.dev/badge/skills/sethdford/shipwright/port-bash-command/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.

agentmods 80×15 button for port-bash-command

Your own site · 80×15
<a href="https://agentmods.dev/skills/sethdford/shipwright/port-bash-command"><img src="https://agentmods.dev/badge/skills/sethdford/shipwright/port-bash-command.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 772 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.00772
Opus 5.5 $0.00021 $0.00309
Sonnet 5.5 $0.00010 $0.00154
Haiku 4.5 $0.00005 $0.00077

Measured 14d ago against content hash b5d8c1292b1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

port-bash-command 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.

.claude/skills/port-bash-command/SKILL.md · 37 lines

What it actually says

Never run a bash suite (scripts/*-test.sh) directly: many drive tmux and touch HOME and the repo. Run suites only through the hermetic runners: bash scripts/sw-test-all.sh --pattern <name> (against bash) or bun run parity (against TypeScript, in a sealed sandbox).

  1. Check the don't-port list in §7.5 of docs/superpowers/specs/2026-10-13-shipwright-ts-migration-design.md. If the command (or the engine it belongs to) is listed there, stop and report it; do not port it.
  2. Read the entry in docs/plans/port/progress.json (command, aliases, script, context, parity). Leave status at bash for now.
  3. If parity is null, write scripts/sw-<name>-test.sh that pins today's behavior (arguments, exit codes, output, files written) and record it in the entry.
  4. Baseline against bash: bash scripts/sw-test-all.sh --pattern sw-<name>-test.sh must pass before you change anything.
  5. Implement in src/contexts/<context>/: pure rules in domain/, the use case in application/, ports for any I/O, adapters in src/adapters/. Write bun:test tests first (TDD).
  6. Add the command in src/cli/commands/ (old names in aliases) and register it in src/cli/commands/index.ts.
  7. Set status to porting and git add the new files (the parity sandbox copies tracked files only). Run bun run parity. It copies the repo into a temporary sandbox with a private HOME, tmux socket and TMPDIR and fail-closed claude/gh shims, replaces the script of every entry at porting or later with a stub (exec bun <sandbox>/src/cli.ts <command> "$@"), runs the suite there, and fails if the real repo changed. A script shared with a command still at bash cannot be stubbed; parity reports that. Do not edit or replace the bash script: it stays as the reference implementation until the entry is bash-deleted (a separate change).
  8. If an old assertion checks implementation (e.g. greps the script source), rewrite it to check behavior so it passes against both bash (step 3) and TypeScript (step 6), and say so in the commit message.
  9. When parity is green, set status to parity-green, then flip the router: in scripts/sw replace the entry's exec "$SCRIPT_DIR/<script>" "$@" body with run_ts <name> "$@", keeping every alias in the label, e.g. name|alias) run_ts name "$@" ;;. bun run port:check rejects a run_ts route whose entry is not parity-green or bash-deleted.
  10. bun run docs:gen, then bun run check (it includes port:check and parity). Commit.
Changes

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.

  1. 14d ago First seen · 37 lines · 52 tokens per session scan A b5d8c1292b1b

Subscribe to this mod's changes

port-bash-command is a skill published in the GitHub repository sethdford/shipwright (21 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 772 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-10-15.

Related

Other skills, from other repositories