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/vasilyu1983/ai-agents-public/dev-git-commit-messagenpx skills add vasilyu1983/AI-Agents-public --skill dev-git-commit-messagegit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWhat 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.00038 | $0.03196 |
| Opus 5 | $0.00019 | $0.01598 |
| Sonnet 5 | $0.00008 | $0.00639 |
| Haiku 4.5 | $0.00004 | $0.00320 |
Grade A, and why
dev-git-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 2d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Message Generator
Generate or validate Conventional Commits for the staged surface.
Default posture: subject line first; body only when risk, rationale, or breaking-change detail is needed; standard types only unless the repo already defines custom ones; never claim behavior not visible in the diff.
Quick Reference
| Need | Default | Reference |
|---|---|---|
| Pick a type | feat/fix/perf/refactor/docs/test/build/ci/chore/style/revert |
Type Selection table below |
| Format a subject | type(scope): imperative summary, ≤72 chars (50 ideal), no trailing period |
Pre-Commit Message Checklist below |
| Mark a breaking change | ! after type/scope, or a BREAKING CHANGE: footer |
Breaking Change Format table below |
| Decide on a body | Only for risk, non-obvious rationale, or breaking-change detail | Body Required? table below |
| Handle AI-authored commits | No tool attribution ever; Assisted-by: trailer only if the repo opts in |
AI-Authored Commits below |
| Pick a release/changelog tool | release-please for reviewed PR releases; semantic-release for full automation; changesets for monorepos | references/changelog-generation-guide.md |
| Scope a monorepo commit | package/app/service directory name, one level deep, stable over time | references/monorepo-commit-conventions.md |
| Validate a message locally | python scripts/commit_validator.py validate --message "..." |
Scripts section below |
Decision Tables
Mode Selection
| Trigger | Mode | Action |
|---|---|---|
| User provides staged diff or asks to commit | Generate | Inspect staged surface, produce primary + alternatives |
| User provides an existing message string | Validate | Check rules, return PASS/WARN/FAIL + exact rewrite |
| Staged diff mixes unrelated areas | Split | Recommend split commits before generating |
| No staged changes | Stop | Report "no staged changes" |
What ships with it
14 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.
- agents/openai.yaml 300 B
- assets/template-commit-message.md 1.9 KB
- assets/template-security-commits.md 3.3 KB
- config.yaml 5.4 KB
- data/sample-commit-history.json 3.0 KB
- data/sources.json 6.5 KB
- learnings.consolidated.md 598 B
- learnings.md 380 B
- references/changelog-generation-guide.md 16 KB
- references/commit-message-antipatterns.md 8.3 KB
- references/conventional-commits-guide.md 8.4 KB
- references/monorepo-commit-conventions.md 11 KB
- scripts/commit_validator.py 22 KB runs code
- scripts/README.md 3.6 KB
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.
- 2d ago First seen · 266 lines · 38 tokens per session scan A edb7f3a50187
dev-git-commit-message is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (82 stars, last pushed 11d ago), licensed MIT. It adds 38 tokens to every session and 3,196 once invoked, about $0.0002 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-30.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
evolve
Start or monitor an evolutionary development loop.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.