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/sordi-ai/skill-everything/git-conventionsnpx skills add sordi-ai/skill-everything --skill git-conventionsgit clone --depth 1 https://github.com/sordi-ai/skill-everythingWrote 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/sordi-ai/skill-everything/git-conventions)<a href="https://agentmods.dev/skills/sordi-ai/skill-everything/git-conventions"><img src="https://agentmods.dev/badge/skills/sordi-ai/skill-everything/git-conventions.svg" alt="Measured on agentmods" 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.00026 | $0.00577 |
| Opus 5 | $0.00013 | $0.00289 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
git-conventions 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 5d 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.
What it actually says
Sub-Skill: Git & Workflow Conventions
Purpose: Consistent commit history, clean branches, no merge conflicts through discipline. Rules that work in teams of 2–20 developers.
Rules
Commit Messages (Conventional Commits)
- Format:
<type>(<scope>): <description>— always lowercase, no period at the end.- Types:
feat,fix,refactor,test,docs,chore,perf,ci - Example:
feat(auth): add JWT refresh token rotation
- Types:
- Description in imperative mood.
add featurenotadded featureoradds feature. - Scope is the affected module name.
fix(user-service): handle null email— notfix(backend). - Mark breaking changes with
!.feat(api)!: remove deprecated v1 endpoints - Body for non-obvious changes. Explains the why, not the what.
Branching
- Branch names:
<type>/<ticket-id>-<short-description>— e.g.feat/PROJ-123-user-export. - Feature branches live max. 2 days. Longer → rebase daily onto
main. - No direct push to
mainordevelop. Always through a pull request. - Delete branch before PR merge. Clean up merged branches from remote.
Pull Requests
- PR title = commit message of the squash commit. Consistency between PR and git log.
- Max. 400 lines diff per PR. Larger → split. Reviewers cannot meaningfully review more than 400 lines.
- Self-review before opening a PR. Read through once yourself, fix obvious mistakes.
Merge Strategy
- Squash-merge for feature branches. Clean linear history on
main. - Merge commit for release branches. So release points remain visible.
git rebase -ibefore PR for clean commits. Squash WIP commits together.
Why This Sub-Skill Earns Stars
The agent automatically creates correct commit messages and branch names. No manual corrections, no discussions in review about formatting.
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.
- 5d ago First seen · 60 lines · 26 tokens per session scan A 317f44cc287e
git-conventions is a skill published in the GitHub repository sordi-ai/skill-everything (20 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 577 once invoked, about $0.0001 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
git-flow-master
Expert git workflow manager for perfect commits, branches, PR descriptions, merge strategies, and changelogs. Use when managing git repositories, writing commit messages, creating PRs, or resolving merge conflicts.
utility-pm-changelog-curator
Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers). Returns a layered draft with a status summary for maintainer review; refuses a dirty working tree unless --committed-only is passed. Use when…
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-workflow
Git 工作流专家。规范化版本控制，确保提交历史清晰可追溯。支持 Conventional Commits 规范、Pull Request 最佳实践、分支管理策略和自动化工作流。.
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.
git-workflow
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely.