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 skills add AndrewDongminYoo/cc-agents-kit --skill semantic-commitgit clone --depth 1 https://github.com/AndrewDongminYoo/cc-agents-kitWrote 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/andrewdongminyoo/cc-agents-kit/semantic-commit)<a href="https://agentmods.dev/skills/andrewdongminyoo/cc-agents-kit/semantic-commit"><img src="https://agentmods.dev/badge/skills/andrewdongminyoo/cc-agents-kit/semantic-commit/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/andrewdongminyoo/cc-agents-kit/semantic-commit"><img src="https://agentmods.dev/badge/skills/andrewdongminyoo/cc-agents-kit/semantic-commit.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.00050 | $0.03567 |
| Opus 5.5 | $0.00020 | $0.01427 |
| Sonnet 5.5 | $0.00010 | $0.00713 |
| Haiku 4.5 | $0.00005 | $0.00357 |
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 6d 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 — 248 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.
Save the change you are about to split as one patch, so Step 4 can tell your hunks from anyone else's:
git diff HEAD --binary --no-textconv > <scratch>/planned.patch
git diff --cached --binary --no-textconv > <scratch>/staged.patch # HEAD to the index as found
git diff --binary --no-textconv > <scratch>/unstaged.patch # the index as found to the working tree
git status --porcelain --untracked-files=all # lists every untracked file, also inside new directories
git diff --no-index --binary --no-textconv /dev/null <untracked-file> >> <scratch>/planned.patch # once per untracked file; exits 1 by design
git diff HEAD compares HEAD with the working tree, so a line that was staged and later changed back in the working tree is in the index but not in planned.patch, and committing the index first leaves a later group to stage the reversal.
staged.patch and unstaged.patch record both steps from HEAD through the index to the working tree, so every line a group can stage appears in one of the three patches, and all three count as planned in Step 4.
git diff HEAD also leaves untracked files out, and plain git status --porcelain shows a new directory as one ?? dir/ line; the --no-index form records each untracked file with its content and mode.
Every patch in this skill is built with --binary --no-textconv: without --binary a changed binary file reads only Binary files differ, and a repository's textconv driver replaces the real bytes with converted text that git apply rejects.
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.
- 6d ago Changed · +49 lines 163b19819e46
- 1mo 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 (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 50 tokens to every session and 3,567 once invoked, about $0.0002 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-31.
Other skills, from other repositories
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
review
Review a change with what this repository knows about it — who depends on the file, which tests cover it, what broke here before, and what the repo has written down. Use before approving a diff, opening a PR, or when asked to review.
global-commit
Create a git commit following Conventional Commits specification.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
precommit
Pre-commit checks — lint:fix -> build -> test.
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.