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 skills/andrewdongminyoo/cc-agents-kit/semantic-commitnpx skills add AndrewDongminYoo/cc-agents-kit --skill semantic-commitgit clone --depth 1 https://github.com/AndrewDongminYoo/cc-agents-kitWhat 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.00050 | $0.02204 |
| Opus 5 | $0.00025 | $0.01102 |
| Sonnet 5 | $0.00010 | $0.00441 |
| Haiku 4.5 | $0.00005 | $0.00220 |
Grade A, and why
semantic-commit 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 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.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Commit
Split work-in-progress changes into clean, reviewable conventional commits, verifying before each commit.
Applicability
Use when:
- Multiple unrelated changes are unstaged/staged together
- User asks for "semantic commits", "logical commits", or "커밋 분리"
- After a multi-item implementation session before pushing
Skip when:
- There is only one logical change (just commit it directly)
- User explicitly asks for a single combined commit
Steps
1. Understand the Full Diff
Run in parallel:
git status
git diff HEAD
git diff --cached
Read each changed file if the diff alone is insufficient to determine intent. Treat the existing index as owned work. Do not reset, unstage, or replace it without explicit approval.
2. Group by Concern
Assign each changed file to a group:
| Type | When |
|---|---|
feat(scope) |
New user-facing behavior |
fix(scope) |
Bug correction |
perf(scope) |
Performance improvement, no behavior change |
refactor(scope) |
Code restructure, no behavior change |
test(scope) |
Test additions or changes only |
build(scope) |
Build system, deps, bundler, packaging |
ci(scope) |
CI/CD config and pipelines |
chore(scope) |
Tooling, version bump, misc maintenance |
docs(scope) |
Documentation only |
style(scope) |
Formatting, import order, no logic change |
Rules:
- One file → one group by default. If a file genuinely spans two concerns, split it at hunk level (see Hunk-Level Splitting) and list it in both groups, marking which part goes where.
- Test files travel with their production file when both change together.
- Never mix
featandfixin the same commit. - Pick
scopefrom the affected module/package/feature area (see Scopes below).
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 · 199 lines · 50 tokens per session scan A 2fa8375c791f
semantic-commit is a skill published in the GitHub repository AndrewDongminYoo/cc-agents-kit (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,204 once invoked, about $0.0003 per session on Opus 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-31.
Other skills, from other repositories
conventional-commit
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
aish-add-skills
Create new skills from documents, tutorials, or examples. Use when user wants to create a skill from learning materials or existing content.
diagnose_system_lag
Local Linux lag and performance diagnosis. Run read-only probes based on the user's symptoms to find CPU, memory, disk, or local network bottlenecks, then give safe advice. Never auto-remediate. Also matches Chinese requests such as 系统卡顿、机器好慢、内存不足、突然重启、OOM、磁盘很慢.
devops-docker-patterns
Docker containerization expert specializing in multi-stage builds, image optimization, Docker Compose patterns, and production container security. Use for Dockerfile optimization, compose configurations, and container best practices.
devops-platform-engineering
Platform engineering expert specializing in internal developer platforms, self-service infrastructure, Backstage service catalogs, GitOps with ArgoCD, and golden path templates. Use for building developer portals and platform-as-a-product.
dns-diagnose
Local DNS resolution troubleshooting with dig/resolvectl/whois. Investigate NXDOMAIN, wrong answers, records not taking effect, and resolver failures. Read-only; do not change DNS config. Also matches Chinese requests such as DNS 解析失败、域名解析不了、NXDOMAIN、解析不到.