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/nicepkg/vsync/prepare-releasegit clone --depth 1 https://github.com/nicepkg/vsyncWhat 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.00013 | $0.02284 |
| Opus 5 | $0.00006 | $0.01142 |
| Sonnet 5 | $0.00003 | $0.00457 |
| Haiku 4.5 | $0.00001 | $0.00228 |
Grade C, and why
prepare-release scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf dist/ build/ How it starts
The opening of the file, as written. The whole thing — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Preparation
Prepare and validate release: $ARGUMENTS
Current Release Context
- Current version: !
git describe --tags --abbrev=0 2>/dev/null || echo "No previous releases" - Package version: @package.json or @setup.py or @pyproject.toml or @go.mod (if exists)
- Unreleased changes: !
git log $(git describe --tags --abbrev=0)..HEAD --oneline 2>/dev/null | wc -l || echo "All commits" - Branch status: !
git status --porcelain | wc -l || echo "0"uncommitted changes - Build status: !
pnpm test 2>/dev/null || python -m pytest 2>/dev/null || go test ./... 2>/dev/null || echo "Test framework detection needed"
Task
Systematic release preparation: $ARGUMENTS
-
Release Planning and Validation
- Determine release version number (semantic versioning)
- Review and validate all features included in release
- Check that all planned issues and features are complete
- Verify release criteria and acceptance requirements
-
Pre-Release Checklist
- Ensure all tests are passing (unit, integration, E2E)
- Verify code coverage meets project standards
- Complete security vulnerability scanning
- Perform performance testing and validation
- Review and approve all pending pull requests
-
Version Management
# Check current version git describe --tags --abbrev=0 # Determine next version (semantic versioning) # MAJOR.MINOR.PATCH # MAJOR: Breaking changes # MINOR: New features (backward compatible) # PATCH: Bug fixes (backward compatible) # Example version updates # 1.2.3 -> 1.2.4 (patch) # 1.2.3 -> 1.3.0 (minor) # 1.2.3 -> 2.0.0 (major) -
Code Freeze and Branch Management
# Create release branch from main git checkout main git pull origin main git checkout -b release/v1.2.3 # Alternative: Use main branch directly for smaller releases # Ensure no new features are merged during release process -
Version Number Updates
- Update package.json, setup.py, or equivalent version files
- Update version in application configuration
- Update version in documentation and README
- Update API version if applicable
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 · 373 lines · 0 tokens per session scan C 9b36ddd9b553
prepare-release is a command published in the GitHub repository nicepkg/vsync (57 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 2,284 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
init-project
Configure the baseline for this specific project. Invokes the scout skill, then claude-automation-recommender, populates .claude/project.json, pre-creates lazy directories, re-renders swarm-worker.md from its template with any stack-specific skills appended, appends a §16 addendum to docs/init/seed.md, runs…
sql_schema
Command "sql_schema" from agentis-tools/ctx, covering ctx sql — public schema (v1), stability contract, views, v1.symbols — one row per symbol and v1.edges — one row per relationship.
coograph-review
Review the changes in scope for spec compliance, convention violations, logic bugs, and architectural issues. You review — you do not author. Never edit files.
coograph-verify
Verify that the described work is complete and correct. Provide evidence for every claim. You verify — you do not implement or fix style.
hotspots
Rank files and symbols by churn x complexity to find refactoring hotspots.
approve-direction
Record human approval of a workflow's direction (the intake + its acceptance criteria + the CO-A evidence). The Direction Approval Guard hook blocks Claude from ever writing approval tokens; this command is the only sanctioned path. Must be user-invoked. Replaces the retired /approve-spec gate (D3/CO-E gate-collapse)…