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.
git clone --depth 1 https://github.com/yves-s/just-shipWrote 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/commands/yves-s/just-ship/just-ship-review)<a href="https://agentmods.dev/commands/yves-s/just-ship/just-ship-review"><img src="https://agentmods.dev/badge/commands/yves-s/just-ship/just-ship-review/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/commands/yves-s/just-ship/just-ship-review"><img src="https://agentmods.dev/badge/commands/yves-s/just-ship/just-ship-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00026 | $0.02291 |
| Opus 5 | $0.00013 | $0.01145 |
| Sonnet 5 | $0.00005 | $0.00458 |
| Haiku 4.5 | $0.00003 | $0.00229 |
Grade B, and why
just-ship-review scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
OLD_PID=$(cat .claude/.dev-server-pid) The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 256 lines · 26 tokens per session scan B 6db6efaa8d76
just-ship-review is a command published in the GitHub repository yves-s/just-ship (24 stars, last pushed 4mo ago), with no licence file. It adds 26 tokens to every session and 2,291 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
CLAUDE
When debugging TUI commands like wt switch (interactive picker), use the tmux-cli skill (preferred) or MCP's node-terminal tools to test interactively.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
pr-dance
Loop a PR through CI and bot review until merge-ready. Use when user says '/pr-dance', 'do the PR dance', or finishing-a-development-branch dispatches option 3.
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.
merge-work-packets
Verify all tracks complete, invoke merging-worktrees, run QA gates, report final integration status.