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/diegomarino/awesomic-cursor-rules/git-conventionsgit clone --depth 1 https://github.com/diegomarino/awesomic-cursor-rulesWhat 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.00000 | $0.01153 |
| Opus 5 | $0.00000 | $0.00576 |
| Sonnet 5 | $0.00000 | $0.00231 |
| Haiku 4.5 | $0.00000 | $0.00115 |
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 3d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Hooks Standards
Hook Types and Purposes
Client-Side Hooks
pre-commit:
description: Runs before git commit to ensure code quality
triggers: Before commit creation
blocking: true
common_uses:
- Linting
- Code formatting
- Unit tests
- Type checking
- Style enforcement
prepare-commit-msg:
description: Modifies default commit message
triggers: After commit message creation, before editor
blocking: false
common_uses:
- Add branch name
- Insert ticket number
- Template enforcement
commit-msg:
description: Validates commit message format
triggers: After commit message creation
blocking: true
common_uses:
- Conventional commits check
- Ticket reference validation
- Length restrictions
post-commit:
description: Runs after commit is completed
triggers: After commit creation
blocking: false
common_uses:
- Notifications
- Documentation updates
- Stats collection
pre-push:
description: Runs before pushing commits
triggers: Before push operation
blocking: true
common_uses:
- Integration tests
- Build verification
- Security checks
Server-Side Hooks
pre-receive:
description: First server hook when receiving push
triggers: Before refs are updated
blocking: true
common_uses:
- Access control
- Policy enforcement
update:
description: Like pre-receive but per branch
triggers: Before each ref update
blocking: true
common_uses:
- Branch-specific rules
- Protected branch logic
post-receive:
description: After entire push process completes
triggers: After successful push
blocking: false
common_uses:
- Notifications
- CI/CD triggers
- Deployment automation
Hook Implementation Guidelines
Script Structure
#!/bin/sh
# Hook: [hook-name]
# Purpose: [brief description]
# Blocking: [yes/no]
# 1. Environment Setup
# Set any required environment variables
export CUSTOM_VAR="value"
# 2. Configuration
MAX_FILE_SIZE="10MB"
RESTRICTED_PATHS="config/*, secrets/*"
# 3. Validation Functions
validate_file_size() {
# Implementation
}
check_restricted_paths() {
# Implementation
}
# 4. Main Logic
main() {
# Core functionality
}
# 5. Execute
main "$@"
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.
- 3d ago First seen · 242 lines · 0 tokens per session scan A a6d280e5073f
git-conventions is a cursor rule published in the GitHub repository diegomarino/awesomic-cursor-rules (10 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,153 tokens. 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.
Other cursor rules, from other repositories
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
git-conventional-commits
Conventional commit messages and logical multi-commit workflow when working with Git.
dos-verify-done-claims-cursorrules-prompt-file
Gate AI done/shipped/fixed claims on ground truth from the DOS kernel (dos verify, dos commit-audit) — git ancestry and the commit's own diff, never the agent's own narration.
pause
Checkpoint the session into git so it survives a close and resumes from any device. Use on "pause", "checkpoint", "cache this session", "save my place", or "I'm stepping away" — writes a handoff, commits work in flight, and pushes.
no-cursor-commit-attribution
Never add Cursor co-author or attribution trailers to git commits or PRs.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.