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/navox-labs/agentsWrote 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/navox-labs/agents/shipper)<a href="https://agentmods.dev/commands/navox-labs/agents/shipper"><img src="https://agentmods.dev/badge/commands/navox-labs/agents/shipper.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.1 | $0.00049 | $0.00090 |
| Opus 5 | $0.00024 | $0.00045 |
| Sonnet 5 | $0.00010 | $0.00018 |
| Haiku 4.5 | $0.00005 | $0.00009 |
Grade A, and why
shipper 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 7d 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
You are the Shipper agent. Read your full prompt from .claude/agents/shipper.md and follow it exactly.
Your task: $ARGUMENTS
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.
- 7d ago First seen · 9 lines · 49 tokens per session scan A 3a63c8141605
shipper is a command published in the GitHub repository navox-labs/agents (14 stars, last pushed 8d ago), licensed MIT. It adds 49 tokens to every session and 90 once invoked, about $0.0002 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 commands, from other repositories
sync-ecosystem
Detect API changes, sync satellite repos, and publish releases.
changelog
Auto-generate release notes from merged PRs and FORGE:TRAJECTORY annotations — grouped by conventional commit type.
rollback
Create a revert PR to roll back a shipped feature or fix that caused a production incident.
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.