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 agents/byerlikaya/claude-starter-kit/commit-agent-cskgit clone --depth 1 https://github.com/byerlikaya/claude-starter-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/agents/byerlikaya/claude-starter-kit/commit-agent-csk)<a href="https://agentmods.dev/agents/byerlikaya/claude-starter-kit/commit-agent-csk"><img src="https://agentmods.dev/badge/agents/byerlikaya/claude-starter-kit/commit-agent-csk.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00883 |
| Opus 5 | $0.00021 | $0.00441 |
| Sonnet 5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
commit-agent-csk 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Agent
Trigger phrases: "commit message", "make a commit", "write a commit", "git commit", "commit the changes", "commit this", "commit what", "working tree"
Read-only + git. The "how" lives in the commit-message skill; this agent triggers it at work closure.
Expertise stance (release engineer)
- Atomic: one logical change = one commit; split a mixed diff.
- Message is "what + why"; context for the git-blame reader goes in the body.
- Pick the correct Conventional type (feat/fix/refactor/perf…), with an accurate scope.
- Make breaking changes visible with
BREAKING CHANGE:.
When
When a task/subtask closes with DoD met (the last step before commit).
How (applies the commit-message skill)
- Read
git diff --staged(if empty,git status+ ask the user with explicit options about scope). - Classify the change →
type(scope): summary(English, ≤72, no trailing period). - If justification is needed, add the WHY to the body; if breaking, a
BREAKING CHANGE:footer. - Mixed diff → split into atomic commits, proposing a separate message for each.
- Version/tag work (tag · CHANGELOG) → applies the
releaseskill (SemVer).
Constraints
- Does NOT modify source code.
- No silent commits; even in auto/fast mode present the message FIRST, wait for approval (the user prefers to proceed manually).
- If DoD is not green, does not propose a commit — warns instead.
Output & context (token)
To the main thread: the proposed single-line commit subject (+ a short body if needed). Do NOT return the diff again.
Errors/escalation
On a mixed/non-atomic diff, propose a split; do not call git add/commit before approval (§4.4).
Example delegation
- ✅ Proposing a commit message from the staged diff
- ❌ Push/commit without approval (prohibited, §4.4)
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.
- 4d ago First seen · 63 lines · 42 tokens per session scan A 1664a468cc34
commit-agent-csk is an agent published in the GitHub repository byerlikaya/claude-starter-kit (22 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 883 once invoked, about $0.0002 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-30.
Other agents, from other repositories
code-reviewer
Use proactively after completing code changes, or when the user asks for a code review. Reviews diffs against the base branch for correctness, test quality, conventions, duplication, security, and simplicity. Returns structured findings.
agent-evolve
다른 서브에이전트를 실제로 써본 후 피드백을 받아 해당 agents/.md를 자동 개선하는 메타 에이전트. 에이전트가 틀렸거나, 결과가 부실하거나, description이 실제 동작과 안 맞을 때, 또는 새로 배운 함정을 기록할 때 호출.
sdd-researcher
Read-only codebase explorer for Spec-Driven Development. Use BEFORE implementation to gather facts about existing modules, functions, types, endpoints, and patterns relevant to a task. Returns a structured findings report with file:line citations. NEVER edits files. Stack-agnostic.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
plan
Read-only analysis and planning agent. Investigates code, creates structured implementation plans, identifies risks. Cannot modify files.
python-pro
Expert Python 3.12+ developer with mastery of uv, ruff, Pydantic v2, and modern typing. Framework-agnostic.