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/avinashp/agentsatlas/committingnpx skills add AvinashP/AgentsAtlas --skill committinggit clone --depth 1 https://github.com/AvinashP/AgentsAtlasWrote 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/skills/avinashp/agentsatlas/committing)<a href="https://agentmods.dev/skills/avinashp/agentsatlas/committing"><img src="https://agentmods.dev/badge/skills/avinashp/agentsatlas/committing.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00879 |
| Opus 5 | $0.00012 | $0.00439 |
| Sonnet 5 | $0.00005 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
committing 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 3d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Committing Skill
Create meaningful, conventional commits that tell the story of your changes.
Workflow
1. Analyze Staged Changes
# See what's staged
git diff --staged --stat
# See detailed changes
git diff --staged
Understand the changes:
- What files changed?
- What's the nature of the change?
- Is this one logical change or multiple?
2. Determine Commit Type
| Type | When to Use |
|---|---|
feat |
New feature for users |
fix |
Bug fix for users |
docs |
Documentation only |
style |
Formatting, no code change |
refactor |
Code change, no feature/fix |
perf |
Performance improvement |
test |
Adding/updating tests |
build |
Build system, dependencies |
ci |
CI configuration |
chore |
Maintenance, tooling |
3. Extract Scope (Optional)
Scope identifies the area of the codebase:
feat(auth): add password reset flow
fix(api): handle null response
refactor(cart): extract price calculation
Common scopes:
- Component/module name:
auth,cart,user - Layer:
api,ui,db - Feature area:
checkout,search,settings
4. Write the Message
Format:
<type>(<scope>): <description>
[optional body]
[optional footer]
Description rules:
- Imperative mood: "add" not "added" or "adds"
- Lowercase first letter
- No period at end
- Max 50 characters for subject line
- Explain what and why, not how
5. Verify and Commit
# One more look
git diff --staged
# Commit
git commit -m "type(scope): description"
# Or with body
git commit -m "type(scope): description
More detailed explanation if needed.
Explain why this change was made."
Quick Reference
Good Commit Messages
feat(auth): add two-factor authentication
fix(api): prevent null pointer on empty response
refactor(user): extract validation to separate module
docs(readme): add installation instructions
test(cart): add edge cases for discount calculation
chore(deps): upgrade react to 18.2
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 173 lines · 24 tokens per session scan A f247602ef46b
committing is a skill published in the GitHub repository AvinashP/AgentsAtlas (7 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 879 once invoked, about $0.0001 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 skills, from other repositories
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
git-workflow
Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.
commit-archaeologist
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite…
pr-draft-summary
Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-agents-python. Use before the final response whenever the current task changed runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size and including…
commit-context
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
commit-history
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.