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/cavalry-collective/visual-stack/shipgit clone --depth 1 https://github.com/Cavalry-Collective/visual-stackWhat 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.00016 | $0.00118 |
| Opus 5 | $0.00008 | $0.00059 |
| Sonnet 5 | $0.00003 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
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 2d 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 the work on the current branch by following Shipping a change when
asked in CLAUDE.md. That section owns the procedure; this command only
invokes it.
$ARGUMENTS
Before you start, report in one line: the branch, whether anything under
plugins/ changed, and — if it did — the version you are shipping and why.
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.
- 2d ago First seen · 14 lines · 16 tokens per session scan A fde1f0ad059e
ship is a command published in the GitHub repository Cavalry-Collective/visual-stack (11 stars, last pushed 12d ago), licensed MIT. It adds 16 tokens to every session and 118 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-30.
Other commands, from other repositories
seo-drift
Compare two SEO snapshots (GSC / GSC AI Performance / rank tracker / AEO probe) and surface top movers per metric with auto-classification — growth / decline / reshuffle / stable / new / lost.
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
ros-first-dollar
Step-by-step playbook to get your first paying customer.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.