Borrowing it
Nothing to install: this file belongs to caretive-ai/project-careti. 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/caretive-ai/project-careti/main/.agents/commands/minor-version-update.mdgit clone --depth 1 https://github.com/caretive-ai/project-caretiWrote 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/commands/caretive-ai/project-careti/minor-version-update)<a href="https://agentmods.dev/commands/caretive-ai/project-careti/minor-version-update"><img src="https://agentmods.dev/badge/commands/caretive-ai/project-careti/minor-version-update/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/commands/caretive-ai/project-careti/minor-version-update"><img src="https://agentmods.dev/badge/commands/caretive-ai/project-careti/minor-version-update.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.00012 | $0.00668 |
| Opus 5.5 | $0.00005 | $0.00267 |
| Sonnet 5.5 | $0.00002 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
minor-version-update 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 2mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Minor Version Update
Update documentation and changelogs for Caret minor version releases.
When to Use
- Minor version update deployment (e.g., 0.4.5 → 0.4.6)
- README/CHANGELOG/docs updates needed
Workflow
Step 1: Analyze Git Changes
# Check commits since last version tag
git log --oneline $(git describe --tags --abbrev=0)..HEAD
# List changed files
git diff --name-only $(git describe --tags --abbrev=0)..HEAD
Step 2: User Confirmation (Required)
AI must confirm with user before proceeding:
| Document Type | Files | Characteristics |
|---|---|---|
| User-facing | README, docs.careti.ai, announcement | Appeal to users, key features only |
| Developer | CHANGELOG.md | Actual log, all changes |
Questions to ask:
- Add to previous version content OR overwrite?
- Exclude minor changes (bugfixes, link updates)?
- Include in announcement?
Step 3: Update Rules by Document Type
User-facing (README, docs, announcement):
- Increment version, add to previous content
- Exclude minor changes (bugfixes, refactoring)
- Include only impactful features
Developer (CHANGELOG.md):
- Keep previous versions, add new on top
- Include all changes
- Record with date
Step 4: Files to Update
README.md:
[v0.4.x Update]banner text## 🎉 v0.4.xsection
docs.careti.ai (7 languages):
docs-ko/getting-started/what-is-careti.mdx
docs-en/getting-started/what-is-careti.mdx
docs-ja/getting-started/what-is-careti.mdx
docs-zh/getting-started/what-is-careti.mdx
docs-fr/getting-started/what-is-careti.mdx
docs-de/getting-started/what-is-careti.mdx
docs-ru/getting-started/what-is-careti.mdx
announcement (optional):
webview-ui/src/caret/locale/*/announcement.json
Step 5: Version Header Translations
| Language | Header |
|---|---|
| ko | ## 🎉 v0.4.y 업데이트 |
| en | ## 🎉 v0.4.y Update |
| ja | ## 🎉 v0.4.y アップデート |
| zh | ## 🎉 v0.4.y 更新 |
| fr | ## 🎉 Mise à jour v0.4.y |
| de | ## 🎉 v0.4.y Update |
| ru | ## 🎉 Обновление v0.4.y |
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.
- 2mo ago First seen · 87 lines · 12 tokens per session scan A 3c7de875c946
minor-version-update is a command published in the GitHub repository caretive-ai/project-careti (47 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 668 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
release
A command for creating a release of the Claude Code Starter framework. A release is a prepared version of software that can be shared or deployed.
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.