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.
git clone --depth 1 https://github.com/jentic/jentic-oneWrote 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/rules/jentic/jentic-one/git-conventions)<a href="https://agentmods.dev/rules/jentic/jentic-one/git-conventions"><img src="https://agentmods.dev/badge/rules/jentic/jentic-one/git-conventions/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/rules/jentic/jentic-one/git-conventions"><img src="https://agentmods.dev/badge/rules/jentic/jentic-one/git-conventions.svg" alt="Reviewed on agentmods" width="80" 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.01117 | $0.01117 |
| Opus 5.5 | $0.00447 | $0.00447 |
| Sonnet 5.5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00112 | $0.00112 |
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 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Conventions
Conventional Commits are enforced repo-wide by the commit-msg hook
(uv run cz check, pure Python — no Node). The allowed types and the schema
regex live in pyproject.toml ([tool.commitizen.customize]) and are guarded
by tests/arch/test_commit_convention.py. This document is the human-readable
source of truth those reference; keep all three in sync.
Commit Types — Use the Correct Type
Reserve fix exclusively for real bug fixes — something was broken in production (on main), now it works. Misusing fix pollutes the auto-generated changelog.
fix in feature branches
If you created the code and the bug in the same feature branch, it's not a fix. You're refactoring your own unshipped work:
# ❌ WRONG — AppLink was created in this branch, not shipped yet
fix(ui): harden AppLink against XSS and correct prop spread order
# ✅ CORRECT — refactoring new code before it ships
refactor(ui): harden AppLink against XSS and correct prop spread order
# ❌ WRONG — our own new password toggle broke the e2e locator
fix(e2e): use getByRole for password field to avoid toggle collision
# ✅ CORRECT — adjusting tests for our own new feature
test(e2e): use getByRole for password field to avoid toggle collision
Rule of thumb: if the bug doesn't exist on main, it's not a fix.
# ❌ WRONG — not a bug fix, and scope should be the file or area
fix(ci): fix CI concurrency and duplicate Docker builds on main
# ✅ CORRECT — use the type that matches the change
ci(release.yaml): fix CI concurrency and duplicate Docker builds on main
Type reference
| Type | Use for |
|---|---|
feat |
New user-facing feature |
fix |
Bug fix (something was broken, now it works) |
test |
Adding or updating tests |
ci |
CI/CD pipeline changes |
chore |
Dependency updates, tooling, configs |
docs |
Documentation only |
style |
Formatting, whitespace (no logic change) |
refactor |
Code restructuring (no behavior change) |
perf |
Performance improvement |
build |
Build system or external deps (Docker, pkg) |
revert |
Reverting a previous commit |
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 · 133 lines · 1,117 tokens per session scan A 231b27738201
git-conventions is a cursor rule published in the GitHub repository jentic/jentic-one (186 stars, last pushed today), licensed Apache-2.0. It adds 1,117 tokens to every session, about $0.0045 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 cursor rules, from other repositories
caliber-pre-commit
Run Caliber sync before git commits to keep agent configs up to date.
git
Git identity and commits — canonical text is root AGENTS.md.
no-git-commit-by-agent
Keep git commits user-owned.
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.