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 anchildress1/awesome-github-copilot --skill generate-commit-messagegit clone --depth 1 https://github.com/anchildress1/awesome-github-copilotWrote 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/anchildress1/awesome-github-copilot/generate-commit-message)<a href="https://agentmods.dev/skills/anchildress1/awesome-github-copilot/generate-commit-message"><img src="https://agentmods.dev/badge/skills/anchildress1/awesome-github-copilot/generate-commit-message/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/anchildress1/awesome-github-copilot/generate-commit-message"><img src="https://agentmods.dev/badge/skills/anchildress1/awesome-github-copilot/generate-commit-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 195 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00158 | $0.01940 |
| Opus 5.5 | $0.00063 | $0.00776 |
| Sonnet 5.5 | $0.00032 | $0.00388 |
| Haiku 4.5 | $0.00016 | $0.00194 |
Grade A, and why
generate-commit-message 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce exactly one Conventional Commits v1.0.0 message from the diff, then commit it signed. The commit is the deliverable — no draft file, no staging, no push.
Boundaries
The only repo-mutating command permitted is git commit -S. Everything else is off-limits:
| Never | Why |
|---|---|
git add / stage anything |
Commit scope is the user's decision, already expressed by what's staged |
git push, rebase, reset, commit --amend |
History mutation isn't this skill's job |
--no-verify, --no-gpg-sign |
Hooks and signing must run |
| Edit source, docs, or config | No formatters, lint fixes, refactors, or test runs |
Commit on main/master |
Unless the user directed it this turn |
| Omit the AI-attribution trailer | A message without it is a failed message |
Abort conditions
Stop and report; do not work around:
- No staged diff →
nothing staged. Do not stage on the user's behalf. - On
main/masterwithout explicit authorization this turn. - Diff changed between derivation and commit (see step 5).
1. Resolve scope
Precedence, first match wins. Jira key regex [A-Z][A-Z0-9]+-\d+, matched case-insensitively,
emitted uppercase:
- User-provided key (request or
argument-hint) - Branch name —
git --no-pager rev-parse --abbrev-ref HEAD - None — omit the scope
Never invent a keyword scope (core, api, docs) when no issue key exists. An absent scope is
correct; a made-up one is noise. The diff informs type and subject, never scope.
2. Acquire diff
git --no-pager diff --cached
Empty → abort. There is no working-tree fallback: git commit records the index, so a message
derived from unstaged edits would describe changes the commit doesn't contain — and the commit
would fail anyway with nothing staged.
Derive everything from hunks only: chat history, prior commits, and memory are not evidence of what this diff changes.
3. Pick type
First match wins:
| Signal | Type |
|---|---|
| Public API removed, signature changed, config key dropped | breaking — add ! and/or BREAKING CHANGE: |
| New user-visible capability | feat |
| Defect repair, no new surface | fix |
| Faster, same behavior | perf |
| Restructure, same behavior | refactor |
| Whitespace, formatting, semicolons | style |
| Tests only | test |
| Docs, comments, JSDoc/KDoc only | docs |
.github/workflows, .circleci, CI config |
ci |
| Build system, deps, packaging | build |
| Reverts a prior commit | revert |
| Maintenance, no production impact | chore |
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 · 201 lines · 158 tokens per session scan A 4cfed2f942c0
generate-commit-message is a skill published in the GitHub repository anchildress1/awesome-github-copilot (66 stars, last pushed 1mo ago), licensed MIT. It adds 158 tokens to every session and 1,940 once invoked, about $0.0006 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
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
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.
git-commit
Create well-structured git commits using the Conventional Commits specification. Use when asked to "commit changes", "create a git commit", "stage and commit", "write a commit message", or "/commit". Analyzes diffs to auto-detect type and scope, generates semantic commit messages, and supports intelligent file staging.
pr-fallback
WHAT — When the repo has no GitHub PR template, structure the pull-request body using the default in references/pr-body-default.md. Pair with output-handshake and github-cli-workflow. Does not open the PR; HOW stays in the forge skill.
commit-code
Analyze code changes to prepare conventional commit message and commit to a new branch.
git-workflow-and-versioning
Use when managing branches, commits, versioning, and release workflows for Android projects, or when cutting a release, choosing a version bump, tagging, or writing a changelog. Covers trunk-based development, atomic commits, versionCode/versionName derived from tags, semver for library modules, changelogs and Play…