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/rafaelkamimura/claude-toolsWrote 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/commands/rafaelkamimura/claude-tools/commit)<a href="https://agentmods.dev/commands/rafaelkamimura/claude-tools/commit"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/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/commands/rafaelkamimura/claude-tools/commit"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/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.00000 | $0.01486 |
| Opus 5.5 | $0.00000 | $0.00594 |
| Sonnet 5.5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
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 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Git Commit Command
Intelligent git commit system that stages only task-related changes and generates meaningful commit messages without AI tool references.
Purpose
- Stage only files related to the current task
- Generate professional commit messages
- Exclude any mention of AI/agent tools
- Maintain clean git history
Execution Steps
Step 1: Check for Task Context
Use Bash tool to find most recent task file:
- Command:
ls -t .claude/task-history/*.md 2>/dev/null | head -1 - Description: "Find most recent task history file"
If no task file exists, output: "No task history found. Proceeding with manual file selection."
If task file exists:
- Use Read tool to read the task file
- Extract: task title, objective, files mentioned, success criteria
Step 2: Analyze Git Status
Use Bash tool to check git status:
- Command:
git status --porcelain - Description: "Check git repository status"
Parse output to categorize:
- Modified files (M prefix)
- Added files (A or ?? prefix)
- Deleted files (D prefix)
- Renamed files (R prefix)
Step 3: Identify Task-Related Files
Based on task context (if available), identify files that:
- Match file patterns from task description
- Are in directories mentioned in task
- Match technology/framework patterns from task
If no task context, consider all changed files as candidates.
Step 4: Present Staging Plan
Output a categorized list of changes:
## Task: [Task Title or "Manual Commit"]
### Will stage:
- file1.js (modified) - implements feature X
- file2.test.js (added) - tests for feature X
### Possibly related (confirm):
- config.json (modified) - may contain task settings
### Will skip:
- .env (modified) - local environment
- debug.log (added) - temporary file
Then output: "Review staging plan. Adjust? (Reply with files to add/remove, or 'ok' to proceed):"
WAIT for user response.
Step 5: Stage Files
Use Bash tool to stage selected files:
- Command:
git add [space-separated file paths] - Description: "Stage task-related files"
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 · 240 lines · 0 tokens per session scan A aec4578f67c6
commit is a command published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,486 tokens. 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 commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.