Borrowing it
Nothing to install: this file belongs to banshee-data/velocity.report. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/banshee-data/velocity.report/main/.claude/skills/ship-change/SKILL.mdgit clone --depth 1 https://github.com/banshee-data/velocity.reportWrote 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/banshee-data/velocity.report/ship-change)<a href="https://agentmods.dev/skills/banshee-data/velocity.report/ship-change"><img src="https://agentmods.dev/badge/skills/banshee-data/velocity.report/ship-change/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/banshee-data/velocity.report/ship-change"><img src="https://agentmods.dev/badge/skills/banshee-data/velocity.report/ship-change.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00885 |
| Opus 5.5 | $0.00012 | $0.00354 |
| Sonnet 5.5 | $0.00006 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
ship-change 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: ship-change
Run the complete quality gate, verify the change is ready to ship, and produce a properly formatted commit.
Usage
/ship-change
/ship-change "add Kalman covariance inflation during coasting"
Procedure
1. Understand what changed
git status
git diff --stat
git diff
Identify which subsystem(s) are affected: Go ([go]), Python ([py]), Web ([js]), Swift ([mac]), docs ([docs]), SQL ([sql]), Makefile ([make]), config ([cfg]).
2. Format
Run the formatter(s) matching the changed subsystem(s):
# Go changes
make format-go
# Web changes
make format-web
# All
make format
3. Lint
make lint
If lint fails, fix the issues before proceeding. Do not skip lint.
4. Test
Run the tests for the affected subsystem(s):
# Go
make test-go
# Web
make test-web
# All
make test
If tests fail, stop. Fix the failures before proceeding.
For a single Go package under test:
go test ./internal/path/to/package/... -v
5. Build verification
Verify the build still compiles:
# Go (local dev, requires libpcap)
make build-radar-local
# If pcap unavailable
make build-radar-linux
For web changes:
make build-web
6. Review the change summary
Produce a one-paragraph summary of what changed and why. Answer:
- What problem does this solve?
- What is the scope of the change (files, components)?
- Are there any known limitations or follow-up items?
7. Compose commit message
Format: [prefix(es)] Description of change
Prefixes based on what changed:
[go]: Go code[py]: Python code[js]: JavaScript/TypeScript[mac]: Swift/macOS[docs]: Markdown documentation[sql]: Database migrations[make]: Makefile[cfg]: Configuration files[ai]: AI-authored edits (always include alongside language tag)
Rules:
- One description line (imperative mood, lowercase after prefix)
- Optional body paragraph if context is non-obvious
- AI edits: always
[ai][go],[ai][py], etc.
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.
- 1mo ago First seen · 157 lines · 31 tokens per session scan A 748a00e0aa3b
ship-change is a skill published in the GitHub repository banshee-data/velocity.report (11 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 885 once invoked, about $0.0001 per session on Opus 5.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-09-25.
ship-change compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ship-changebanshee-data/velocity.report | Skill | 11 | today | Apache-2.0 | A | 31 | Claude Code |
| create-prprisma/orm | Skill | 48k | yesterday | Apache-2.0 | A | 48 | Claude Code, Codex |
| engineer-bot-opsmakecindy/cindy | Skill | 9.3k | yesterday | Apache-2.0 | A | 57 | Claude Code, Codex |
| mcore-split-prNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 25 | Claude Code |
| git-commit-writermergisi/awesome-openclaw-agents | Skill | 4.1k | 2d ago | MIT | A | 53 | Claude Code, Codex |
| strict-tdda5c-ai/babysitter | Skill | 1.9k | 5d ago | MIT | A | 34 | Claude Code |
| gsd-audit-fixcoco-research/coco | Skill | 785 | yesterday | Apache-2.0 | A | 60 | Claude Code |