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.
git 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/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/agents/byerlikaya/claude-starter-kit/commit-agent-csk"><img src="https://agentmods.dev/badge/agents/byerlikaya/claude-starter-kit/commit-agent-csk.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.00042 | $0.01657 |
| Opus 5.5 | $0.00017 | $0.00663 |
| Sonnet 5.5 | $0.00008 | $0.00331 |
| Haiku 4.5 | $0.00004 | $0.00166 |
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 26d 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 — 95 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). - Shape the message the skill's way — Conventional Commits
type(scope): summaryunless./CLAUDE.mddeclares a## Conventionsformat, which wins. Language likewise: the project's, never a fixed one. Any literal the request hands you (ticket id,#time 1d, a required prefix) is copied EXACTLY; if a literal fights the format, say so and ask rather than adjusting it. - 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).
Writing the message on Windows
git commit -m with a multi-line message and PowerShell here-strings do not survive each other: measured on
PowerShell 5.1, git commit -F - @'…'@ hands the text to git as an ARGUMENT, git reads it as a pathspec
("did not match any file(s)"), and a git add earlier in the same line leaves the tree staged but uncommitted.
Write the message to a UTF-8 file WITHOUT a BOM and use git commit -F <file>; measured on the same machine,
that path commits cleanly with the subject and body intact.
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.
- 26d ago Changed · +1 lines 7beaaaea2b01
- 27d ago Changed · +12 lines 3036ab0ac9ce
- 1mo ago Changed · +19 lines 323d5435ad1b
- 1mo 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 (24 stars, last pushed 24d ago), licensed MIT. It adds 42 tokens to every session and 1,657 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-30.
Other agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
git-ops
Lightweight git operations agent for commits, pushes, status checks, and branch management. Uses Haiku for speed and cost efficiency.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
ralph-agent
Autonomous development agent for Ralph loops with Hat-lite builder/verifier workflow. Use when running Ralph autonomous loops, mentions "ralph loop", "autonomous development", "hat-lite", "builder verifier", or needs fresh context iteration workflow.
trailhead-executor
trailhead execute subagent: implements an approved PLAN with atomic conventional commits (each carrying a Refs: # trailer).
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early unless the brief reserves commit authority to the…