spectre-ship

spectre-ship is a skill for Claude Code, Codex from joenandez/spectre. It costs 70 tokens per session (1,383 once invoked), scanned A, original, MIT.

A workflow for turning finished branch work into a pull request, a review request for code changes. It cleans and rebases the branch, observes the full test suite, handles failures, and opens the pull request.

In plain words
What is it for?
Use it when finished branch work needs to be prepared, checked, and opened as a pull request.
Why use it?
It provides a defined handoff path for completed work and records test results and any repairs or routing decisions. It is intended for reviewer-ready changes rather than implementation work.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present.

Good fit Use it when finished branch work needs to be prepared, checked, and opened as a pull request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joenandez/spectre/spectre-ship
Install

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.

Any agent
npx skills add joenandez/spectre --skill spectre-ship
Clone the repo
git clone --depth 1 https://github.com/joenandez/spectre

Made for: Claude Code, Codex.

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 spectre-ship

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

agentmods 80×15 button for spectre-ship

Your own site · 80×15
<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-ship"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,383 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00070 $0.01383
Opus 5 $0.00035 $0.00691
Sonnet 5 $0.00014 $0.00277
Haiku 4.5 $0.00007 $0.00138

Measured 2d ago against content hash 748a9363761e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

spectre-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 2d 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.

plugins/spectre-codex/skills/spectre-ship/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ship

Own cleanup, rebase, one advisory suite, and draft PR. Load focused skills; do not duplicate them.

Inputs

  • $ARGUMENTS - optional feature name/root or descendant artifact, target branch (default origin/main), feedback-focus hint, or --draft.
  • Live branch, working tree, remotes, and PR state.

Feature root

  • Reuse a managed FEATURE_ROOT only when explicit/current-thread evidence ties it to this work (physical directory wins; never branch/recency/lifecycle/scans); distinct work ignores ambient roots. Otherwise, including on collision, standalone MUST first load and follow Skill(spectre-feature-root) through DONE; orchestrated calls escalate. Keep writes beneath it and pass it unchanged.

Proof independence

Proof is optional: do not inspect, infer, invoke, or gate on it. Only authority or publication-safety impasses prevent PR creation.

Outputs + DONE

  • PR URL, clean commits, rebase summary, tested SHA, verification/repair routing, CI: pending, measurement, and PR_OPENED status PASS|REPAIRED|PRE_EXISTING_FAILURES|INDETERMINATE|KNOWN_FAILURES_REMAIN.

DONE when: Prune/Test → Sweep, rebase, one full suite, repair/routing, measurement relay/degradation, and PR URL are complete. Non-green verification never prevents DONE.

Method / guardrails

  1. Resolve once. Confirm a feature branch, target, FEATURE_ROOT, full set, and no unrelated/sensitive changes; stop on main/master. Reuse current-thread CLEANED_THROUGH_SHA only if unambiguous and ancestral; otherwise use the full set. Invoke node "${PLUGIN_ROOT}/hooks/scripts/workflow-cli.mjs" measure start --label Ship and relay its snapshot; below, measure means node "${PLUGIN_ROOT}/hooks/scripts/workflow-cli.mjs" measure.
  2. Cleanup boundary. Classify P0-P3; invoke measure start for Prune/Test, then one parallel dispatch: Skill(spectre-prune) through one prune lead and Skill(spectre-test) through one test lead with the same set, risk plan, {FEATURE_ROOT}, and --orchestrated. The test lead owns batching; neither stages/commits. At each child end invoke measure finish for its snapshot with its returned child identity when available; relay compact paths/checks and repair/route cross-boundary needs unless NEEDS_AUTHORITY.
  3. Sweep. Invoke measure start --label "Sweep"; run Skill(spectre-sweep) with --orchestrated, unchanged set, and both results. It alone integrates stale/uncovered checks, repairs attributable failures, and commits; at Sweep end invoke measure finish for the Sweep snapshot.
  4. Rebase. Invoke measure start --label "Rebase"; run Skill(spectre-rebase) with target, --orchestrated, and --verification-owner parent; retain backup summary. No checks; at Rebase end invoke measure finish for the Rebase snapshot.
  5. Observe one full suite after rebase. At rebased FULL_SUITE_SHA, derive complete EXPECTED_BASE_SHA, EXPECTED_HEAD_SHA, and EXPECTED_DIFF_SHA256; invoke measure start --label "Full suite" and measure start --label "Create PR". In parallel start the one full suite lane and Skill(spectre-create_pr) pending pass with target, --orchestrated --pr-phase pending, and that tuple; pending opens/returns a draft with local verification RUNNING. At each lane end invoke measure finish for its snapshot with its returned child identity when available. No duplicate suites or raw child output.
    • Attribute exact failures branch-caused|unrelated|indeterminate, preferring target-SHA CI and otherwise reproducing only the failing check at target.
    • Repair branch-caused families; rerun only failing/affected checks, never the full suite. Route unrelated/indeterminate findings; record repaired HEAD and CI: pending.
    • Verification is evidence, never a stop condition.
  6. Create PR and measure. After the suite, call Skill(spectre-create_pr) with target, --orchestrated --pr-phase final-update, existing URL/body, refreshed complete EXPECTED_BASE_SHA/EXPECTED_HEAD_SHA/EXPECTED_DIFF_SHA256, and FINAL_VERIFICATION_SUMMARY, changing Testing only; refresh candidate-sensitive claims first if repairs changed the tuple. On PR_CANDIDATE_STALE, refresh and retry. Invoke measure summary --rows … --outer-snapshot … --persist --project-dir … --feature-root "$FEATURE_ROOT" --base-sha "$EXPECTED_BASE_SHA" --head-sha "$EXPECTED_HEAD_SHA" --diff-sha256 "$EXPECTED_DIFF_SHA256"; relay its table, persistence status, and history path. Persistence degradation never blocks PR completion; never inspect transcripts, track clocks, or calculate. Unattributed Prune/Test and Full suite/Create PR use one exact parallel-group total; unavailable measurement never blocks Ship.

Read the full file on GitHub · 60 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago Changed · +6 lines 748a9363761e
  2. 7d ago Changed · +1 lines · -1 tokens per session e5710eb627cd
  3. 12d ago First seen · 53 lines · 71 tokens per session scan A c9d31ffda9bc

Subscribe to this mod's changes

spectre-ship is a skill published in the GitHub repository joenandez/spectre (161 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 1,383 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-08-30.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens