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 johnqtcg/awesome-skills --skill git-commitgit clone --depth 1 https://github.com/johnqtcg/awesome-skillsWrote 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/johnqtcg/awesome-skills/git-commit)<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/git-commit"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/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/johnqtcg/awesome-skills/git-commit"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 5 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 5 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 5 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00052 | $0.03967 |
| Opus 5.5 | $0.00021 | $0.01587 |
| Sonnet 5.5 | $0.00010 | $0.00793 |
| Haiku 4.5 | $0.00005 | $0.00397 |
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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit (Safety Enhanced, Angular Convention)
Create a commit from the current working tree with safety gates first, then generate a concise Angular-style message in English.
Maintaining this skill (not needed to run it): references/design-evidence.md records the measured evidence behind every contract below and the verified environment matrix; scripts/run_cross_env_probe.sh, scripts/run_portability_matrix.sh and scripts/eval/ re-derive it.
Hard Rules
- Never commit with unresolved conflicts.
- Never commit secrets, credentials, keys, or
.envsensitive values. - Subject line must fit the repo's limit — default
<= 50 charstotal (includingtype(scope):). A commitlint/CONTRIBUTINGlimit discovered in §5 replaces that default; the §6 guard enforces whichever applies. There is no separate absolute 50. - Do not use
--amendunless explicitly requested. If already pushed, warn about force push. - If any safety gate fails, stop and report clearly.
- One commit = one logical change. Do not mix unrelated fixes, features, or formatting.
Workflow
Bundled scripts are always invoked as bash "<path-to-skill>/scripts/<name>.sh" — <path-to-skill> is the absolute skill directory (where this SKILL.md was loaded from), never a path relative to the repository. Keep the working directory at the target repo root; the scripts read the repo through git.
1. Preflight
git rev-parse --is-inside-work-tree # must print "true"
git -c core.quotePath=false status --short # quotePath=false: see the raw path
BRANCH=$(git rev-parse --abbrev-ref HEAD) # "HEAD" means detached (allowed)
# In-progress operation? Worktree-safe: resolve real paths, never read .git/ directly.
for state in rebase-merge rebase-apply MERGE_HEAD CHERRY_PICK_HEAD REVERT_HEAD; do
[ -e "$(git rev-parse --git-path "$state")" ] && echo "IN_PROGRESS $state"
done
# Unresolved conflicts: this diff exits 0 regardless, so act on OUTPUT, not exit code.
git -c core.quotePath=false diff --name-only --diff-filter=U
STOP (hard block — report which one and what to resolve) if any of these hold:
--is-inside-work-treedid not printtrue;- any
IN_PROGRESS <state>line printed (rebase / merge / cherry-pick / revert in progress); - the conflict diff printed any path (unresolved merge conflicts).
What ships with it
37 files 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.
- references/design-evidence.md 8.3 KB
- references/quality-gate-go.md 1.5 KB
- references/quality-gate-java.md 2.7 KB
- references/quality-gate-node.md 2.1 KB
- references/quality-gate-python.md 1.7 KB
- references/quality-gate-rust.md 1.6 KB
- scripts/detect-ecosystems.sh 3.9 KB runs code
- scripts/eval/README.md 5.5 KB
- scripts/eval/run_eval.sh 8.2 KB runs code
- scripts/eval/scenarios/01_ambiguous_bulk.sh 527 B runs code
- scripts/eval/scenarios/02_explicit_bulk_authorization.sh 660 B runs code
- scripts/eval/scenarios/03_mixed_intent.sh 731 B runs code
- scripts/eval/scenarios/04_pre_staged_surprise.sh 247 B runs code
- scripts/eval/scenarios/05_scanner_cannot_complete.sh 600 B runs code
- scripts/eval/scenarios/06_downgraded_finding_in_test.sh 447 B runs code
- scripts/eval/scenarios/07_uncommitted_allowlist.sh 677 B runs code
- scripts/eval/scenarios/08_two_canonical_scopes.sh 1.1 KB runs code
- scripts/eval/scenarios/09_hook_rejects.sh 755 B runs code
- scripts/eval/scenarios/10_subject_length_limit.sh 878 B runs code
- scripts/resolve-scope.sh 5.5 KB runs code
- scripts/run_cross_env_probe.sh 9.2 KB runs code
- scripts/run_portability_matrix.sh 7.6 KB runs code
- scripts/run_regression.sh 800 B runs code
- scripts/run-gate.sh 9.9 KB runs code
- scripts/secret-scan.sh 13 KB runs code
- scripts/stash-guard.sh 5.0 KB runs code
- scripts/tests/golden/001_canonical_scope_from_history.json 744 B
- scripts/tests/golden/002_bootstrap_scope_for_new_repo.json 684 B
- scripts/tests/golden/003_mixed_roots_omit_scope.json 646 B
- scripts/tests/golden/004_subject_guard_blocks_long_line.json 649 B
- scripts/tests/golden/005_env_timeout_override.json 578 B
- scripts/tests/golden/006_makefile_timeout_override.json 688 B
- scripts/tests/golden/007_mature_repo_without_match_omits_scope.json 1003 B
- scripts/tests/golden/008_two_canonical_scopes_omit_scope.json 1.1 KB
- scripts/tests/test_git_integration.py 91 KB runs code
- scripts/tests/test_golden_scenarios.py 9.3 KB runs code
- scripts/tests/test_skill_contract.py 28 KB runs code
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 Changed · +4 lines 845d812d9d52
- 1mo ago First seen · 196 lines · 52 tokens per session scan A 72c30961f447
git-commit is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed 8d ago), licensed MIT. It adds 52 tokens to every session and 3,967 once invoked, about $0.0002 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 skills, from other repositories
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
inbox-triage
Daily GitHub notification inbox triage - surfaces aging vuln PR replies, security advisories, review requests, and mentions that need action.
install-skill
Install a community skill pack into this fork from a GitHub repo and ship it as an auto-merged PR.
repo-stats-autoupdate
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.