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 skills/adrielp/ai-engineering-harness/git_commit_helpernpx skills add adrielp/ai-engineering-harness --skill git_commit_helpergit clone --depth 1 https://github.com/adrielp/ai-engineering-harnessWhat 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.00033 | $0.01294 |
| Opus 5 | $0.00016 | $0.00647 |
| Sonnet 5 | $0.00007 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
git_commit_helper 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 2d 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.
This is a copy
89% identical to git-commit-helper — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Helper
When to Use This Skill
Activate this skill when the user:
- Explicitly asks to "commit" their changes
- Says "save my work" or "save these changes"
- Says "create a commit" or "make a commit"
- Asks you to commit after completing implementation work
- Mentions they want to save progress to git
Core Process
Step 1: Analyze Current State
Run these commands in parallel to understand the changes:
git status # See all changed files
git diff # View modifications
git diff --staged # View staged changes
git log --oneline -n 5 # Check recent commit style
Step 2: Plan Your Commits
Think about:
- What changed: Review the conversation history to understand what was accomplished
- Logical grouping: Which files belong together?
- Clear messages: Draft descriptive commit messages in imperative mood
- Why over what: Focus on the purpose of changes, not just the mechanics
Consider whether changes should be:
- One commit: If all changes are part of a single logical unit
- Multiple commits: If there are distinct, separable changes (e.g., refactoring + new feature)
Step 3: Present Your Plan
Show the user a clear plan before executing:
I plan to create [N] commit(s) with these changes:
Commit 1:
Files: [list specific files]
Message: [proposed commit message in imperative mood]
[Commit 2, 3, etc. if multiple...]
Shall I proceed?
Important:
- Be specific about which files go in each commit
- Show the complete commit message you'll use
- Wait for user confirmation
Step 4: Execute Upon Confirmation
Once the user approves:
# Add specific files (NEVER use -A or .)
git add path/to/file1.js path/to/file2.ts
# Create commit with planned message
git commit -m "Your planned message here"
# Show the result
git log --oneline -n [number of commits you created]
Never use:
git add -Agit add .git commit -a
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.
- 2d ago First seen · 201 lines · 33 tokens per session scan A 2101eae81692
git_commit_helper is a skill published in the GitHub repository adrielp/ai-engineering-harness (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,294 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to git-commit-helper, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…