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/elvatis/elvatis-mcp/shipgit clone --depth 1 https://github.com/elvatis/elvatis-mcpWrote 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/elvatis/elvatis-mcp/ship)<a href="https://agentmods.dev/commands/elvatis/elvatis-mcp/ship"><img src="https://agentmods.dev/badge/commands/elvatis/elvatis-mcp/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.00000 | $0.00183 |
| Opus 5 | $0.00000 | $0.00092 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
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 3d 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
Pre-publish checklist for v0.1.0:
-
npm run buildpasses clean - Claude Desktop smoke test passed (at least
home_lighttested live) - Version consistent in package.json + README.md
- DASHBOARD.md updated (tested tools marked ✅)
- LOG.md updated with session summary
Then:
git add -A && git commit -m "release: v0.1.0"
git tag v0.1.0 && git push origin main --tags
gh release create v0.1.0 --title "v0.1.0 - Initial release" --notes "First public release. 12 tools: Home Assistant (6), Memory (3), OpenClaw Cron (3)."
npm publish --access public
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.
- 3d ago First seen · 18 lines · 0 tokens per session scan A 782d81b5535b
ship is a command published in the GitHub repository elvatis/elvatis-mcp (0 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 183 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-08-31.
Other commands, from other repositories
release
Create a release — stable or beta. Usage: /release [beta].
release
Before publishing, run the compatibility bootstrap.
release
Walk the llmwiki release process step by step.
ship
Ship is the operational release-prep flow for a connected project repo.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.
release
Cut a domux release — tag HEAD, push, watch the GH Action.