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 aiya000/dotfiles --skill git-commitgit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/aiya000/dotfiles/git-commit)<a href="https://agentmods.dev/skills/aiya000/dotfiles/git-commit"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/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/aiya000/dotfiles/git-commit"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 Excessive Agency · line 75 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 189 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00043 | $0.02445 |
| Opus 5.5 | $0.00017 | $0.00978 |
| Sonnet 5.5 | $0.00009 | $0.00489 |
| Haiku 4.5 | $0.00004 | $0.00245 |
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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-commit
Automatically generates a Conventional Commits compliant commit message and commits staged changes.
Important:
- This skill only commits staged changes. It does not stage any new files
- DO NOT RUN
git push
Behavior
-
Use the
git-verify-identityskill to confirm git user identity before proceeding -
Gather the current state by running:
git diff --staged— the staged changes to commitgit status— overall working tree stategit log --oneline -20— recent commits, to learn the repository's style
-
Analyze the staged changes and recent commits
-
Determine whether the changes include a breaking change (see Breaking Changes (MANDATORY) below); if so, you MUST indicate it explicitly in the message
-
Scan the staged diff for potential secrets (see Secret Scan below); ask the user before proceeding if any are found
-
Generate a commit message following:
- Conventional Commits specification (structure and basic rules)
- User's commit style patterns learned from repository history
-
Execute
git commitwith the generated message
Secret Scan
Before committing, check the staged diff for:
- API keys and tokens: strings starting with
ghp_,gho_,AKIA,sk-,xox, or matching-----BEGIN.*PRIVATE KEY - Variables with sensitive names holding a value: patterns like
API_KEY=,_SECRET=,_TOKEN=,PASSWORD= - Hardcoded absolute home paths:
/Users/<name>/or/home/<name>/(prefer~) - Personal or organizational proper nouns that could identify specific individuals or organizations
If any of the above are found, do not commit. Use AskUserQuestion to present these options:
- "Commit as-is" — proceed despite the finding
- "Fix then commit" — cancel so the user can fix the issue first
- "Cancel" — abort without further action
Only proceed if the user selects "Commit as-is", or if nothing suspicious was found.
Conventional Commits Specification Summary
Commit message structure:
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 · +26 lines cf6d47abe49c
- 1mo ago First seen · 212 lines · 43 tokens per session scan A 4944c559c844
git-commit is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 2,445 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
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.
smart-commit
Analyze staged changes and split them into multiple logical commits following Conventional Commits.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
gen-commit-msg
Generate intelligent commit messages based on staged changes following Conventional Commits format.
ship
Generate a conventional commit message from staged or unstaged changes and create an atomic commit, then optionally push and watch CI until it passes or fails. Use when the user says "write a commit", "generate a commit message", "commit this", "git add .", or "ship this". Push and CI-watch are optional and skipped if…
commit
Read this skill before making git commits and pushing.