velocity.report: Skill for Claude Code

.claude/skills/release-prep/SKILL.md

release-prep is a skill for Claude Code from banshee-data/velocity.report. It costs 42 tokens per session (1,565 once invoked), scanned A, original, Apache-2.0.

A release-readiness checklist for a point release or deployment image. It combines formatting, linting, tests, builds, documentation checks, agent consistency checks, and changelog review into a go/no-go report.

In plain words
What is it for?
Use it before tagging a release, building a deployment disk image, or after a large feature reaches the main branch.
Why use it?
It provides one final check for common release blockers instead of requiring each quality and documentation check to be remembered separately.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is banshee-data/velocity.report's own configuration. It tells Claude Code how to work on velocity.report itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything velocity.report configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/check-relative-links.py --report 2>&1.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/banshee-data/velocity.report/main/.claude/skills/release-prep/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/banshee-data/velocity.report

Made for: Claude Code.

Wrote 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.

agentmods badge for release-prep

README.md
[![agentmods](https://agentmods.dev/badge/skills/banshee-data/velocity.report/release-prep/github.svg)](https://agentmods.dev/skills/banshee-data/velocity.report/release-prep)
Your own site
<a href="https://agentmods.dev/skills/banshee-data/velocity.report/release-prep"><img src="https://agentmods.dev/badge/skills/banshee-data/velocity.report/release-prep/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.

agentmods 80×15 button for release-prep

Your own site · 80×15
<a href="https://agentmods.dev/skills/banshee-data/velocity.report/release-prep"><img src="https://agentmods.dev/badge/skills/banshee-data/velocity.report/release-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,565 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01565
Opus 5.5 $0.00017 $0.00626
Sonnet 5.5 $0.00008 $0.00313
Haiku 4.5 $0.00004 $0.00156

Measured 1mo ago against content hash 5670ffd7d391, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-prep 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.

.claude/skills/release-prep/SKILL.md · 219 lines

How it starts

The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: release-prep

Run the full release readiness workflow for a point release. This skill orchestrates the quality gate, agent/skill consistency checks, documentation preparedness, and changelog verification in a single pass.

Usage

/release-prep
/release-prep --scope go
/release-prep --skip-docs

When to run

  • Before tagging a point release.
  • Before building a disk image for deployment.
  • After a large feature branch lands on main.
  • When you want a single "are we ready?" answer.

Relationship to other skills

This skill orchestrates checks that overlap with other skills. It does not replace them: it calls them or runs their core checks in sequence:

Skill What release-prep uses from it
ship-change Format → lint → test → build gate
docs-release-prep Link check, length audit, plan graduation, open questions
weekly-retro Agent drift check

If you have already run /docs-release-prep and /ship-change recently, /release-prep will re-verify rather than redo heavy work.

Procedure

1. Format

make format

If any files change, stage them and note it in the report.

2. Lint

make lint

All subsystems must pass. If lint fails, stop and fix before proceeding.

3. Test

make test

All test suites must pass. If scoping to a single subsystem:

make test-go       # Go only
make test-python   # Python only
make test-web      # Web only

4. Build

Verify all build targets succeed:

make build-radar-local   # Go server (requires libpcap)
make build-web           # Svelte frontend
make build-ctl           # velocity-ctl

If build-radar-local fails due to missing pcap, use make build-radar-linux.

5. Agent drift check

make check-agent-drift

Read the full file on GitHub · 219 lines

Changes

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.

  1. 1mo ago First seen · 219 lines · 42 tokens per session scan A 5670ffd7d391

Subscribe to this mod's changes

release-prep is a skill published in the GitHub repository banshee-data/velocity.report (11 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 1,565 once invoked, about $0.0002 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.

Related

release-prep compared with skills from other repositories

release-prep next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-prepbanshee-data/velocity.reportSkill11todayApache-2.0A42Claude Code
analyzing-network-traffic-for-incidentsmukul975/Anthropic-Cybersecurity-SkillsSkill36k2mo agoApache-2.0A91Claude Code
analyzing-network-packets-with-scapymukul975/Anthropic-Cybersecurity-SkillsSkill36k2mo agoApache-2.0A75Claude Code
analyzing-network-traffic-with-wiresharkmukul975/Anthropic-Cybersecurity-SkillsSkill36k2mo agoApache-2.0B49Claude Code
whitebox-toolsznlgis/opengis-skillsSkill7610d agoMITA119Claude Code, Codex
performing-network-packet-capture-analysisxalgorix/xalgorixSkill1.3kyesterdayApache-2.0C62Claude Code, Codex
pdalznlgis/opengis-skillsSkill7610d agoMITB90Claude Code, Codex