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/eddiebelaval/squireWrote 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/eddiebelaval/squire/ship)<a href="https://agentmods.dev/commands/eddiebelaval/squire/ship"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/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/commands/eddiebelaval/squire/ship"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/ship.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.00000 | $0.00391 |
| Opus 5 | $0.00000 | $0.00196 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
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 5d 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.
What it actually says
/ship - Complete Feature & Create PR
You are helping ship a completed feature. Follow these steps:
-
Verify Everything Works
- Run all tests and ensure they pass
- Check build succeeds in production mode
- Verify no TypeScript/linting errors
-
Create Summary
- List all files changed
- Summarize what was built in plain English
- Note any important decisions made
-
Commit Changes (if uncommitted)
- Stage all relevant files
- Create a meaningful commit message
- Follow format: "feat: [description]"
-
Triad Check (if project has VISION.md + SPEC.md)
- Scan the diff for new routes, pages, components, API endpoints
- Cross-reference with SPEC.md capabilities
- If new capabilities not in SPEC: use AskUserQuestion to confirm adding them
- If changes touch a VISION pillar: ask if pillar status should change
- Update SPEC.md and/or VISION.md before creating PR
- Reference:
~/.claude/skills/triad-derive/AUTOMATION.md
-
Push & Create PR
- Push branch to remote
- Create PR with clear description
- Include test plan and screenshots if applicable
-
Final Report
- Provide PR URL
- Summarize what's ready to review
- Note any follow-up items
-
Monitor Deploy (if Vercel project)
- After PR is created or push lands, suggest:
/loop 30s /deploy-watch - Or set up a Cron watch:
CronCreatewith/deploy-watchevery 2 min for background monitoring
- After PR is created or push lands, suggest:
Important: Only proceed if all checks pass. If anything fails, fix it first before creating the PR.
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.
- 5d ago First seen · 43 lines · 0 tokens per session scan A 0adec103aa8f
ship is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 391 tokens. 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-09-03.
Other commands, from other repositories
create-feature
Full-stack feature development with comprehensive scaffolding, testing, and documentation. Creates feature branch, implements core functionality, adds tests, and updates documentation in a single workflow.
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
bucle
Lanzar bucle autónomo para ejecutar historias del PRD.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
execute-prp
Implement features from PRP specifications with comprehensive validation and testing.
quality-gate
Run technical quality checks before commits or PRs — build, types, lint, test, security, diff review.