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 rules/sordi-ai/skill-everything/git-conventionsgit clone --depth 1 https://github.com/sordi-ai/skill-everythingWhat 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.00022 | $0.00531 |
| Opus 5 | $0.00011 | $0.00266 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
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 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.
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.
- 2d ago First seen · 51 lines · 22 tokens per session scan A 15d9bb3194d7
git-conventions is a cursor rule published in the GitHub repository sordi-ai/skill-everything (19 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 531 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 cursor rules, from other repositories
project-rules
Cursor rule "project-rules" from peva3/anchor, covering cursor ai rules, core directives, critical enforcements, pre-commit checklist and required folders.
git-conventions
Git commit and branching conventions.
no-auto-commit
Never commit or push without explicit user instruction.
cairn-commit-network
Commits that run cairn hooks need unsandboxed network.
commit
Commit rules — branch safety, explicit staging, 3-option commit messages, push approval.
no-cursor-attribution
Git commits must not include Cursor co-author attribution.