What is phoenix-ship?

A final verification step for software work. It checks that the task's acceptance test passes and that the recorded evidence showing this result has not been altered.

Use it immediately before merging code or telling someone a task is complete, including when using the /phoenix-ship command.

It prevents an agent from claiming work is finished when the result has not been proved. If the evidence is missing or the check fails, it does not report success.

phoenix-ship — Skill for Claude Code and Codex by All-The-Vibes

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 All-The-Vibes/ATV-Phoenix --skill phoenix-ship

Clone the repo

git clone --depth 1 https://github.com/All-The-Vibes/ATV-Phoenix

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-ship/github.svg)](https://agentmods.dev/skills/all-the-vibes/atv-phoenix/phoenix-ship)

Your own site

<a href="https://agentmods.dev/skills/all-the-vibes/atv-phoenix/phoenix-ship"><img src="https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/all-the-vibes/atv-phoenix/phoenix-ship"><img src="https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 936 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.

Model	Per session	Once invoked
Fable 5.1	$0.00084	$0.00936
Opus 5	$0.00042	$0.00468
Sonnet 5	$0.00017	$0.00187
Haiku 4.5	$0.00008	$0.00094

Measured 11d ago against content hash 4c9e37a34dd3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

phoenix-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 11d 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.

skills/phoenix-ship/SKILL.md · 77 lines

How it starts

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

phoenix-ship — declare done only on green evidence

Overview

This is the last line of defense against shipping silently-broken work. "Done" is not a feeling or a diff that looks right — it is a green phoenix_sense on the acceptance check plus an intact trace that proves the green is real. Phoenix exists to prevent exactly one failure: an agent confidently saying "done" on work that doesn't actually work. This skill is where that promise is kept.

When to use

The final step of any task, right before you tell the user it's complete or merge.
Whenever you're about to type "done", "fixed", "ready", or "shipped".

The ship gate

  About to say "done"
       │
       ▼
  1. phoenix_sense(acceptance_check)   ──► must be ok:true
       │                                       │ red?
       ▼                                       ▼
  2. phoenix_verify_trace              ──► STOP. Not done. → phoenix-debug
       │  ok + intact chain?
       ▼
  3. Report WITH evidence (check + trace head hash)
       │
       ▼
       DONE (provably)

1. Final acceptance sense

phoenix_sense(acceptance_check) from the Intent Contract (phoenix-think). Green is mandatory. Not "the test I added" — the acceptance check that represents the user's actual definition of success.

2. Verify the trace

phoenix_verify_trace → ok:true with an intact hash chain. This proves the green you're about to report is genuine and wasn't reached by skipping or editing a gate. A broken chain means you are not done, no matter how the code looks.

3. Report with the evidence attached

State the check that passed and the trace head hash, so the claim is auditable:

"Done — pytest -q exits 0 (acceptance check); trace verified, 14 rows, head 9885e6df…."

That one line is the difference between a trustworthy completion and a hopeful one.

The rule that is the whole point

Never type "done" without a green phoenix_sense. If the check is red or the trace is broken, you are not done — say exactly what is failing and route to phoenix-debug. "I'm not sure it passed" is an acceptable, honest status; a fabricated completion is the cardinal failure this entire harness exists to prevent.

Read the full file on GitHub · 77 lines

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.

11d ago First seen · 77 lines · 84 tokens per session scan A 4c9e37a34dd3

Subscribe to this mod's changes

phoenix-ship is a skill published in the GitHub repository All-The-Vibes/ATV-Phoenix (5 stars, last pushed 6d ago), licensed MIT. It adds 84 tokens to every session and 936 once invoked, about $0.0004 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-31.

Testing agentic-ai ai-agents developer-tools github-copilot llm-tools mcp

semgrep-rule-variant-creator

Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.

waybarrios/opencode-power-pack · 50 tokens

build-status-cache

Skip Phase 7 rebuild when no code changed since Phase 5 build passed. Compares git diff hash against stored hash from last successful build validation. Triggers on: entering Phase 7, checking build status, before final build validation. Returns BUILDCACHEHIT to skip or BUILDCACHEMISS to re-run build-validator.

closedloop-ai/claude-plugins · 69 tokens

implementation-standards

Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.

attilaszasz/sdd-pilot · 44 tokens

terraform-test

WORKFLOW SKILL — Write and run Terraform tests (.tftest.hcl). WHEN: "create terraform test", "write tftest", ".tftest.hcl", "mock provider", "test module", "test assertion". USE FOR: test files, run blocks, assertions, mock providers, plan-mode unit tests, apply-mode integration tests, test troubleshooting. DO NOT USE…

jonathan-vella/apex-accelerator · 101 tokens

hotfix

Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…

pe-menezes/vibeflow · 102 tokens

clarification-strategies

Reference material with ambiguity-audit patterns and critique strategies for requirements. Loaded on demand by clarify-spec; not directly invokable.

attilaszasz/sdd-pilot · 33 tokens