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/skills/minor-version-update/SKILL.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/skills/caretive-ai/project-careti/minor-version-update)<a href="https://agentmods.dev/skills/caretive-ai/project-careti/minor-version-update"><img src="https://agentmods.dev/badge/skills/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/skills/caretive-ai/project-careti/minor-version-update"><img src="https://agentmods.dev/badge/skills/caretive-ai/project-careti/minor-version-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 1 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Agent Snooping · line 168 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00000 | $0.01291 |
| Opus 5 | $0.00000 | $0.00646 |
| Sonnet 5 | $0.00000 | $0.00258 |
| Haiku 4.5 | $0.00000 | $0.00129 |
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 10d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Minor Version Update Skill
Overview
Caret의 마이너 버전 업데이트(0.4.x) 시 수행해야 하는 작업들을 정의합니다.
When to Use
- 마이너 버전 업데이트 배포 시 (예: 0.4.5 → 0.4.6)
- README/CHANGELOG/docs 업데이트가 필요할 때
Step 1: Git 변경사항 분석
마지막 태그 또는 버전 이후의 변경사항을 확인합니다:
# 마지막 버전 태그 이후 커밋 확인
git log --oneline $(git describe --tags --abbrev=0)..HEAD
# 또는 특정 커밋 이후
git log --oneline <last-version-commit>..HEAD
# 변경된 파일 목록
git diff --name-only $(git describe --tags --abbrev=0)..HEAD
Step 2: 사용자 확인 (필수)
AI는 작업 전 반드시 다음을 사용자에게 확인해야 합니다:
2-1. 문서 유형 구분
| 문서 유형 | 파일 | 특징 |
|---|---|---|
| 사용자용 | README, docs.careti.ai, announcement | 사용자에게 어필, 중요 기능만 |
| 개발자용 | CHANGELOG.md | 실제 로그, 모든 변경사항 |
2-2. 확인할 질문들
-
업데이트 방식:
- 이전 버전 내용에 추가할까요? (사용자용 권장)
- 새로 덮어쓸까요? (개발자용 CHANGELOG)
-
포함할 내용:
- 버그패치/링크수정 같은 사소한 변경은 제외할까요? (사용자용 권장)
- 모든 변경사항을 포함할까요? (개발자용 CHANGELOG)
-
announcement 업데이트:
- 이번 업데이트도 announcement에 포함할까요?
- 개발자가 아닌 일반 사용자에게 중요한 변경인가요?
Step 3: 문서별 업데이트 규칙
사용자용 문서 (README, docs, announcement)
규칙:
- 버전 번호만 올리고, 이전 버전 내용에 새 내용 추가
- 버그패치/리팩터링/링크수정 등 사소한 변경은 제외
- 사용자에게 어필할 수 있는 중요 기능만 포함
예시 (0.4.5 → 0.4.6):
## 🎉 v0.4.6
- 🎁 **Free Credits Promo** — 새 기능 (0.4.6)
- 🤖 **GLM-4.7** — 기존 기능 (0.4.5)
- 🖼️ **Image Tools** — 기존 기능 (0.4.5)
...
개발자용 문서 (CHANGELOG.md)
규칙:
- 이전 버전 유지, 새 버전 위에 추가
- 모든 변경사항 포함 (버그패치, 리팩터링 등)
- 날짜와 함께 기록
예시:
## [0.4.6] 2026-01-19
### ✨ Improved
- **Dynamic branding**: 하드코딩 "Cline" → 동적 브랜드명
### Fixed
- **README links**: 다국어 README 링크 수정
---
## [0.4.5] 2026-01-18
(기존 내용 유지)
Step 4: 파일별 수정 위치
README.md
[v0.4.x Update]배너 텍스트## 🎉 v0.4.x섹션
docs.careti.ai (7개 언어)
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
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.
- 10d ago First seen · 169 lines · 0 tokens per session scan A 7f3a217c2926
minor-version-update is a skill published in the GitHub repository caretive-ai/project-careti (47 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,291 tokens. 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 skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
release-clisbot
Release clisbot safely to npm and GitHub. Use when Codex is asked to prepare, validate, bump, publish, tag, or document a clisbot beta release, next beta release, or official stable/latest release, including release notes, migration notes, GitHub release notes, npm dist-tags, and post-publish verification.