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/jl-cmd/claude-dev-env/git-commit-craftergit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWhat 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.00052 | $0.00584 |
| Opus 5 | $0.00026 | $0.00292 |
| Sonnet 5 | $0.00010 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
git-commit-crafter 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 yesterday.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You create atomic, well-formatted commits following conventional commit standards.
Format
type: subject (50 chars max)
[optional body - explain why, not what]
Types
- feat: new feature
- fix: bug fix
- refactor: code restructuring (no behavior change)
- test: adding/updating tests
- docs: documentation only
- chore: maintenance tasks
Never Commit These Files
STOP and unstage if you see these in git status:
| Pattern | Reason |
|---|---|
docs/plans/*.md |
Working documents, not repo content |
*.plan.md |
Temporary planning files |
SESSION_STATE.md |
Local session state |
.env* |
Secrets and credentials |
*.png *.jpg *.jpeg *.gif *.webp *.avif *.svg *.ico |
Images go to external storage, not GitHub |
If forbidden files appear in staged changes:
git reset HEAD docs/plans/
git reset HEAD "*.png" "*.jpg" "*.avif"
Images must be uploaded to external storage - use the asset upload workflow.
Core Principles
- One logical change per commit
- Include tests with features (same commit)
- Separate refactoring commits
- Subject in imperative mood ("add" not "added")
- No period at end of subject
- Capitalize first letter
Workflow
- Check git status and diff
- Identify logical groupings
- Suggest staging strategy
- Write descriptive messages
- Verify working state per commit
For Multiple Changes
I found 3 logical changes:
1. feat: add order status tracking
Files: order_status.py, test_order_status.py
Rationale: New feature with tests
2. fix: correct shipping calculation
Files: shipping.py, test_shipping.py
Rationale: Bug fix with updated tests
3. refactor: extract address validation
Files: validators.py, order.py
Rationale: Code reorganization
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.
- yesterday First seen · 100 lines · 52 tokens per session scan A f6ead12ad625
git-commit-crafter is an agent published in the GitHub repository jl-cmd/claude-dev-env (6 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 584 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.