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 commands/valsecchi75/project-scaffolder/shipgit clone --depth 1 https://github.com/valsecchi75/project-scaffolderWrote 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/valsecchi75/project-scaffolder/ship)<a href="https://agentmods.dev/commands/valsecchi75/project-scaffolder/ship"><img src="https://agentmods.dev/badge/commands/valsecchi75/project-scaffolder/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.00027 | $0.00379 |
| Opus 5 | $0.00014 | $0.00189 |
| Sonnet 5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
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 4d 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
Full release pipeline. Only proceeds if /gate is green.
Usage
/ship --patch — bug fix release (1.2.3 → 1.2.4)
/ship --minor — new feature (1.2.3 → 1.3.0)
/ship --major — breaking change (1.2.3 → 2.0.0)
Steps
- Run
/gate. If FAIL → abort immediately. - Check working tree is clean. If dirty → abort, list uncommitted files.
- Warn if on non-default branch.
- Read current version from project metadata (
pubspec.yaml,package.json, etc.). - Bump version per flag (semver).
- Generate
CHANGELOG.mdentry from commits since the last tag, grouped by type:feat:→ Addedfix:→ Fixedrefactor:→ Changeddocs:→ Docs
- Update
wiki/log.mdwith release entry. - Commit version bump + CHANGELOG.
- Create annotated git tag
v<new-version>. - Report: what shipped, version, files touched, next action (user decides when to push).
Rules
- NEVER push automatically.
- NEVER skip
/gate— release without gate is not a release. - If uncommitted changes exist: abort, list them, ask the user to handle.
- If on non-default branch: warn prominently before proceeding.
- If the previous tag doesn't exist yet: generate a "first release" changelog entry.
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.
- 4d ago First seen · 42 lines · 27 tokens per session scan A 1ccbb67337b0
ship is a command published in the GitHub repository valsecchi75/project-scaffolder (9 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 379 once invoked, about $0.0001 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.
Other commands, from other repositories
release
You are a release agent for the Gigacode project (sandbox-agent). Your job is to cut a new release by running the release script, monitoring the GitHub Actions workflow, and fixing any failures until the release succeeds.
ci
Trigger GitHub Actions CI/CD builds, sign, publish, or check CI status.
release
This document describes the standard release process for agtrace.
release
Command "release" from khuynh22/mcp-wireshark, covering how it works, what to tell the user, if no label is added and manual fallback.
release
Release a new version of notebooklm-mcp-2026 to PyPI.
release
Cut a release — derive the version, close the review, rewrite CHANGELOG, commit, push, wait for CI, tag, wait for the Release workflow and the GitHub release, then wait until the version is live on NuGet.