A set of Git rules requiring commits to use Conventional Commits, a standard format such as "fix(Components): ..." that labels the kind of change and its area.

It guides commit types, optional scopes, and commit messages for features, fixes, refactoring, documentation, tests, maintenance, and other changes.

It makes project history easier to read and supports tools that generate changelogs or process commits automatically.

git-commits — Cursor rule for Cursor by Stramp/Lost-Mines-Phandelver

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Stramp/Lost-Mines-Phandelver

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/git-commits/github.svg)](https://agentmods.dev/rules/stramp/lost-mines-phandelver/git-commits)

Your own site

<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/git-commits"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/git-commits/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/git-commits"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/git-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 791 This file is loaded in full into every session.

When invoked 791 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00791	$0.00791
Opus 5.5	$0.00316	$0.00316
Sonnet 5.5	$0.00158	$0.00158
Haiku 4.5	$0.00079	$0.00079

Measured 1mo ago against content hash 51d9652ddc6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-commits 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.

.cursor/rules/git-commits.mdc · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git and Commit Rules

Commit Format (Conventional Commits)

ALWAYS use Conventional Commits format to facilitate history, automatic changelog and tool integration.

Structure

<type>(<scope>): <short description>

[optional body]

[optional footer]

Commit Types

feat: New feature/functionality
fix: Bug fix
refactor: Refactoring (no behavior change)
docs: Documentation only
style: Formatting, spaces, etc (doesn't affect code)
test: Test addition or fix
chore: Maintenance tasks (build, dependencies, etc)
perf: Performance improvement
ci: CI/CD changes

Scope (Optional but Recommended)

Use the affected module/area:

Characters - Characters and related components
Components - Generic components
Data - Data Assets and Data Tables
Utils - Utilities and helpers
Gameplay - Game mechanics
Architecture - Architectural changes
Docs - Documentation
Build - Build system

Correct Examples

feat(Characters): add CharacterTotalLvl to Data Asset
fix(Components): fix CharacterDataComponent search when Owner is nullptr
refactor(Utils): move FindCharacterDataComponent to ComponentHelpers
docs(Architecture): add Mermaid diagrams to ARCHITECTURE.md
test(Utils): add tests for ComponentHelpers::FindCharacterDataComponent
perf(Characters): optimize final attributes calculation
chore(Build): update project dependencies
ci(GitHub): add automatic build workflow

Incorrect Examples

❌ "fix"
❌ "update"
❌ "changes"
❌ "fixed the bug"
❌ "feat: new thing"
❌ "fix: component bug"

Message Rules

Short Description

Maximum 50 characters (ideal)
First letter lowercase (except proper nouns)
No period
Imperative verb: "add", "fix", "remove" (not "added", "fixed")

Body (Optional)

Use to explain what and why (not how)
Separate from title with blank line
Maximum 72 characters per line

Footer (Optional)

Read the full file on GitHub · 139 lines

Changes

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 · 139 lines · 791 tokens per session scan A 51d9652ddc6b

Subscribe to this mod's changes

git-commits is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 10mo ago), licensed MIT. It adds 791 tokens to every session, about $0.0032 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-31.

Commits Git and workflow

git-commits