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/gokulkrishh/.cursor/gitgit clone --depth 1 https://github.com/gokulkrishh/.cursorWhat 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.00005 | $0.00370 |
| Opus 5 | $0.00003 | $0.00185 |
| Sonnet 5 | $0.00001 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
git 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 yesterday.
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
Use conventional commit format for clear and consistent commit messages.
Format
<type>: <description>
Common Types
feat: New Features
feat: add user authentication
feat: implement dark mode toggle
feat: add payment processing
fix: Bug Fixes
fix: sidebar click issue
fix: login form validation
fix: memory leak in component
chore: Maintenance
chore: upgrade packages
chore: update dependencies
chore: configure build settings
refactor: Code Restructuring
refactor: sidebar for application
refactor: user validation logic
refactor: database queries
docs: Documentation
docs: update README
docs: add API documentation
docs: fix installation guide
style: Code Formatting
style: fix indentation
style: resolve linting errors
style: format with prettier
test: Testing
test: add user login tests
test: fix failing unit tests
test: add integration tests
Examples
feat: add shopping cart functionality
fix: resolve checkout button not working
chore: update React to version 18
refactor: extract reusable components
docs: add component usage examples
style: fix TypeScript linting warnings
test: add form validation tests
Rules
- Use present tense ("add" not "added")
- Keep descriptions under 50 characters
- Start with lowercase after colon
- No period at the end
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.
- yesterday First seen · 91 lines · 5 tokens per session scan A 189657b535eb
git is a cursor rule published in the GitHub repository gokulkrishh/.cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 5 tokens to every session and 370 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.