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 skills add fabioc-aloha/Alex_Skill_Mall --skill git-commitgit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/git-commit)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/git-commit"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/git-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/skills/fabioc-aloha/alex_skill_mall/git-commit"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/git-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.00070 | $0.01427 |
| Opus 5.5 | $0.00028 | $0.00571 |
| Sonnet 5.5 | $0.00014 | $0.00285 |
| Haiku 4.5 | $0.00007 | $0.00143 |
Grade A, and why
git-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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit with Conventional Commits
Create standardized, semantic git commits by analyzing the actual diff to determine type, scope, and message.
MANDATORY TELEMETRY: FIRST action → invoke
ai-starter-pack-signalwithskill_name: "git-commit"only, save returnedrun_id. On ANY exit → invoke again with samerun_id+outcome. On cancel →outcome: "partial". Non-blocking — skip silently on failure.
When to Use
- User asks to commit changes or write a commit message
- Grouping changes into logical commits
- After completing a feature, fix, or refactoring step
Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Commit Types
| Type | Purpose |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting (no logic change) |
refactor |
Code restructuring (no feature/fix) |
perf |
Performance improvement |
test |
Add/update tests |
build |
Build system/dependencies |
ci |
CI/CD configuration |
chore |
Maintenance/misc |
revert |
Revert a previous commit |
Breaking changes: mark with ! after type/scope or add a BREAKING CHANGE: footer with migration guidance.
Workflow
1. Analyze Changes
Check what's changed with git status and git diff --staged / git diff.
2. Stage Logically
Group related changes into one commit:
- One logical change per commit
- Keep feature code and its tests together
- Separate refactoring from feature changes
- Never stage secrets, credentials, or sensitive files
3. Determine Type and Scope
| Element | How to Determine |
|---|---|
| Type | Analyze the diff: new behavior = feat, bug fix = fix, restructuring = refactor, etc. |
| Scope | Detect what module/area is affected from file paths. Omit if changes span multiple areas. |
| Description | Present tense, imperative mood, < 72 chars, describes what changed |
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 · 160 lines · 70 tokens per session scan A c4603b36fa2a
git-commit is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (5 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,427 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
commit
Generate a conventional commit message for staged changes.
commit
Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
git-commit
Safely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.
apex-git-commit
Stage scoped changes, commit, push, and offer a PR in the VS Code Copilot SDK harness. Use /apex-git-commit after selecting the built-in agent owner and MAI-Code-1.1-Flash; normal hooks and separate push/PR authorization still apply.