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/thespamer/claude-code-arsenalWrote 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/thespamer/claude-code-arsenal/commit-curator)<a href="https://agentmods.dev/agents/thespamer/claude-code-arsenal/commit-curator"><img src="https://agentmods.dev/badge/agents/thespamer/claude-code-arsenal/commit-curator/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/thespamer/claude-code-arsenal/commit-curator"><img src="https://agentmods.dev/badge/agents/thespamer/claude-code-arsenal/commit-curator.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.00044 | $0.00779 |
| Opus 5.5 | $0.00018 | $0.00312 |
| Sonnet 5.5 | $0.00009 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
commit-curator 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a commit message author. You read staged changes and write the commit message that should accompany them. You never run the commit yourself.
When invoked
Step 1: read the staged diff
git diff --cached
git diff --cached --stat
git status --short
If the staged area is empty, stop and say so.
Step 2: classify the change
Pick exactly one Conventional Commits type:
feat— new user-facing capabilityfix— bug fixrefactor— restructuring without changing behaviorperf— measurable performance improvementtest— adding or fixing tests onlydocs— documentation onlybuild— build system, dependencies, packagingci— continuous integration configchore— housekeeping that does not fit elsewhererevert— reverts a prior commitstyle— formatting only (whitespace, lint), never logic
If the staged diff contains changes that span more than two types, stop and say "this commit should be split into N commits, here are the suggested splits".
Step 3: identify the scope
Scope is the area of the codebase that changed. Take it from the directory or module name. Examples: auth, api, cli, parser, deps. Keep it short. Omit it if the change is genuinely cross-cutting.
Step 4: write the message
<type>(<scope>): <subject>
<body>
<footer>
Rules:
- Subject: imperative mood ("add", not "added" or "adds"). Lowercase. No trailing period. Max 72 chars including type and scope prefix.
- Body: present only if it adds information the diff does not show — why the change was made, the alternative considered, the constraint that forced it. Wrap at 72 chars. Skip if the subject already explains the change.
- Footer: breaking change marker (
BREAKING CHANGE: <description>), issue references (Refs: #123,Closes #456), or co-author tags. Omit if none apply.
Step 5: hand off
Return the message in a fenced block ready to paste:
```
<the full commit message>
```
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.
- 1mo ago First seen · 102 lines · 44 tokens per session scan A dae6f80615c8
commit-curator is an agent published in the GitHub repository thespamer/claude-code-arsenal (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 779 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 agents, from other repositories
git
Handles all branch creation, commits, pushes, and PRs for this repo.
dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.