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 joenandez/spectre --skill spectre-shipgit clone --depth 1 https://github.com/joenandez/spectreWrote 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/joenandez/spectre/spectre-ship)<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.
<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>- 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.00070 | $0.01383 |
| Opus 5 | $0.00035 | $0.00691 |
| Sonnet 5 | $0.00014 | $0.00277 |
| Haiku 4.5 | $0.00007 | $0.00138 |
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.
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 (defaultorigin/main), feedback-focus hint, or--draft.- Live branch, working tree, remotes, and PR state.
Feature root
- Reuse a managed
FEATURE_ROOTonly 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 followSkill(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, andPR_OPENEDstatusPASS|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
- Resolve once. Confirm a feature branch, target,
FEATURE_ROOT, full set, and no unrelated/sensitive changes; stop onmain/master. Reuse current-threadCLEANED_THROUGH_SHAonly if unambiguous and ancestral; otherwise use the full set. Invokenode "${PLUGIN_ROOT}/hooks/scripts/workflow-cli.mjs" measure start --label Shipand relay its snapshot; below,measuremeansnode "${PLUGIN_ROOT}/hooks/scripts/workflow-cli.mjs" measure. - Cleanup boundary. Classify P0-P3; invoke
measure startfor Prune/Test, then one parallel dispatch:Skill(spectre-prune)through one prune lead andSkill(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 invokemeasure finishfor its snapshot with its returned child identity when available; relay compact paths/checks and repair/route cross-boundary needs unlessNEEDS_AUTHORITY. - Sweep. Invoke
measure start --label "Sweep"; runSkill(spectre-sweep)with--orchestrated, unchanged set, and both results. It alone integrates stale/uncovered checks, repairs attributable failures, and commits; at Sweep end invokemeasure finishfor the Sweep snapshot. - Rebase. Invoke
measure start --label "Rebase"; runSkill(spectre-rebase)with target,--orchestrated, and--verification-owner parent; retain backup summary. No checks; at Rebase end invokemeasure finishfor the Rebase snapshot. - Observe one full suite after rebase. At rebased
FULL_SUITE_SHA, derive completeEXPECTED_BASE_SHA,EXPECTED_HEAD_SHA, andEXPECTED_DIFF_SHA256; invokemeasure start --label "Full suite"andmeasure start --label "Create PR". In parallel start the one full suite lane andSkill(spectre-create_pr)pending pass with target,--orchestrated --pr-phase pending, and that tuple; pending opens/returns a draft with local verificationRUNNING. At each lane end invokemeasure finishfor 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.
- Attribute exact failures
- Create PR and measure. After the suite, call
Skill(spectre-create_pr)with target,--orchestrated --pr-phase final-update, existing URL/body, refreshed completeEXPECTED_BASE_SHA/EXPECTED_HEAD_SHA/EXPECTED_DIFF_SHA256, andFINAL_VERIFICATION_SUMMARY, changing Testing only; refresh candidate-sensitive claims first if repairs changed the tuple. OnPR_CANDIDATE_STALE, refresh and retry. Invokemeasure 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.
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.
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.
- 2d ago Changed · +6 lines 748a9363761e
- 7d ago Changed · +1 lines · -1 tokens per session e5710eb627cd
- 12d ago First seen · 53 lines · 71 tokens per session scan A c9d31ffda9bc
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.
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.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
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.
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.
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".
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…