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/jayminwest/kotadb/releasegit clone --depth 1 https://github.com/jayminwest/kotadbWhat 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.00000 | $0.02318 |
| Opus 5 | $0.00000 | $0.01159 |
| Sonnet 5 | $0.00000 | $0.00464 |
| Haiku 4.5 | $0.00000 | $0.00232 |
Grade A, and why
release scanned grade A 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -f http://localhost:3000/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release
Template Category: Action
Create a production release by merging develop → main with automated versioning, validation, and GitHub release creation.
Pre-Release Validation
Before creating a release, the command performs comprehensive checks:
- Clean Working Tree: Ensure no uncommitted changes (
git status --shortmust be empty) - CI Status: Verify all GitHub Actions are passing on
developbranch - Migration Sync: Run
bun run test:validate-migrationsto check drift - Type Checking: Execute
bunx tsc --noEmitfor type safety - SQLite Schema Validation: Verify database schema is correct
- Health Checks: Verify API endpoints are responding correctly
Version Bumping
Prompt user for version bump type:
- major: Breaking changes (1.0.0 → 2.0.0)
- minor: New features, backward compatible (1.0.0 → 1.1.0)
- patch: Bug fixes, backward compatible (1.0.0 → 1.0.1)
Updates:
app/package.jsonversion field- Creates version bump commit:
chore: bump version to X.Y.Z
Release Process
Step 1: Prepare Release Branch
git checkout develop
git pull --rebase origin develop
git checkout -b release/vX.Y.Z
Step 2: Update Version
cd app
# Update package.json version
bun run version <major|minor|patch>
# Commit version change
git add package.json
git commit -m "chore: bump version to X.Y.Z"
Step 3: Generate Changelog
Extract commits from develop since last release:
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
Group by type:
- Features: commits starting with
feat: - Bug Fixes: commits starting with
fix: - Chore: commits starting with
chore: - Documentation: commits starting with
docs: - Performance: commits starting with
perf: - Refactor: commits starting with
refactor:
Format as markdown for release notes.
Step 4: Create Release PR
git push -u origin release/vX.Y.Z
gh pr create \
--base main \
--head release/vX.Y.Z \
--title "Release vX.Y.Z" \
--body "$(cat <<'EOF'
## Release vX.Y.Z
### Summary
Brief description of release highlights
### Changelog
<Generated changelog from commits>
### Pre-Release Checklist
- [x] All CI checks passing on develop
- [x] Clean working tree verified
- [x] Migration sync validated
- [x] Type checking passed
- [x] SQLite schema validated
- [x] Health checks passed locally
### Deployment Plan
1. Merge this PR to main
2. Create GitHub release for distribution
3. Monitor logs for errors
4. Verify local health checks pass
### Rollback Plan
If issues arise:
1. Revert merge commit on main
2. Redeploy previous version
3. Create hotfix branch from main for urgent fixes
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
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.
- 3d ago First seen · 353 lines · 0 tokens per session scan A c6db35909581
release is a command published in the GitHub repository jayminwest/kotadb (102 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,318 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
release
Release a new version: bump version, update changelog, tag, push, and create a GitHub release.
release
Review and publish the Release Please release PR, then verify every registry.
release
Cut a Uni-CLI release from a clean main.
bump
Perform a full version bump: sync main, write changelog, refresh top-level docs, bump version, and push.
ship-ticket
Ship an ALREADY-BUILT ticket — code review → PR → merge → learnings → install-local. Skips the build (you built it in SpecKit Companion). The tail of /fix-tickets, no rebuild.
generate-changelog
Génération Automatique du Changelog.