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/stefan-jansen/claude-code-toolkitWrote 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/stefan-jansen/claude-code-toolkit/git)<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/git"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/git/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/stefan-jansen/claude-code-toolkit/git"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/git.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.00012 | $0.00855 |
| Opus 5.5 | $0.00005 | $0.00342 |
| Sonnet 5.5 | $0.00002 | $0.00171 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
git 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Operations Hub
Consolidated command for all git-related operations. Combines commit, PR, and issue workflows into a single interface.
Input: $ARGUMENTS
Usage
Commit Operations
/git commit "feat: Add user authentication"
/git commit # Interactive commit message
Pull Request Operations
/git pr # Create PR from current branch
/git pr --draft # Create draft PR
Issue Operations
/git issue "#123" # Start work on GitHub issue
/git issue "Fix login bug" # Work on issue by title
Phase 1: Parse Operation Type
Based on the arguments provided: $ARGUMENTS
I'll determine which git operation to perform:
- If arguments start with "commit": Handle git commit workflow
- If arguments start with "pr": Handle pull request creation
- If arguments start with "issue": Handle GitHub issue workflow
- If no arguments: Show usage help
Phase 2: Execute Git Commit Workflow
When handling commit operations:
Pre-Commit Validation
- Check git status to see what files are staged/modified
- Ensure we're in a git repository
- Validate that there are changes to commit
Quality Gates
- Run available tests (if any exist)
- Check for linting issues (if tools available)
- Verify no secrets or sensitive data being committed
Commit Creation
- Stage appropriate files if needed
- Generate conventional commit message if not provided
- Execute git commit with proper formatting
- Include Claude Code attribution
Phase 3: Execute Pull Request Workflow
When handling PR operations:
Pre-PR Validation
- Ensure we're on a feature branch (not main/master)
- Check that commits exist beyond main branch
- Verify branch is pushed to remote
PR Creation
- Use GitHub CLI (gh) if available
- Generate meaningful PR title and description
- Include summary of changes made
- Link to relevant issues if applicable
- Set appropriate labels and reviewers
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 · 149 lines · 12 tokens per session scan A a06c5a44ec31
git is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (90 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 855 once invoked, about $0.0000 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 commands, from other repositories
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
catchup
Restore context after /clear by summarizing recent work and project state.
commit
Generate a conventional commit message for staged changes.
refactor-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.