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 agentmods add skills/floomhq/moto/shipnpx skills add floomhq/moto --skill shipgit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/ship)<a href="https://agentmods.dev/skills/floomhq/moto/ship"><img src="https://agentmods.dev/badge/skills/floomhq/moto/ship.svg" alt="Measured on agentmods" 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 | $0.00067 | $0.00545 |
| Opus 5 | $0.00034 | $0.00272 |
| Sonnet 5 | $0.00013 | $0.00109 |
| Haiku 4.5 | $0.00007 | $0.00055 |
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 Skill
Step 1: QA check
Before shipping, analyze the diff and verify:
- Which files changed and why
- Whether tests exist for the changes
- Whether the change is complete (no TODOs, no debug code, no console.logs)
- Whether env vars or config need updating
Run:
git diff main...HEAD
Step 2: Sync with main
git fetch origin
git rebase origin/main
If conflicts arise, resolve them before continuing.
Step 3: Run tests on the merged code
# Run whatever test suite exists
npm test # or pytest, cargo test, go test, etc.
npm run build # Verify build passes
npm run lint # Verify linting passes
Do NOT ship if tests fail.
Step 4: Pre-landing review
Check the final diff one more time:
git diff origin/main...HEAD
Look for:
- Accidental debug code or console.logs
- Hardcoded values that should be env vars
- Missing error handling
- Breaking changes to public APIs
- Security issues (XSS, injection, exposed secrets)
Step 5: Push
git push origin HEAD
If the branch doesn't exist remotely yet:
git push -u origin HEAD
Step 6: Create PR
gh pr create --title "<title>" --body "<body>"
PR title format: <type>: <description> (e.g., fix: correct auth token expiry, feat: add dark mode)
PR body should include:
- What changed and why
- How to test
- Any breaking changes
- Screenshots for UI changes
Step 7: Verify
After creating the PR:
- Check CI is running (not failing)
- Verify the PR description is accurate
- Return the PR URL to the user
Rules
- NEVER push directly to main/master without a PR (unless repo has no branch protection and user explicitly asks)
- NEVER push with failing tests
- NEVER skip the pre-landing review
- Always create PRs as draft if the work is not complete
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 · 96 lines · 67 tokens per session scan A 07cdc901ac29
ship is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 545 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
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
performance
CLI performance optimization - startup time, memory usage, token savings benchmarking.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
orchestrator-lanes
Claude Code dev-orchestrator only. File-based multi-lane PM playbook (score, DAG, run-controller, L0/L1/L2, ship). Use when this session IS that agent, or user says info / справка / lane-stack:orchestrator-lanes info. SKIP: Grok, Codex, Kimi, Qwen, AGY, Cursor writer CLIs and any default coding agent — do not load, do…