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/mitas/cursor-rules/gitgit clone --depth 1 https://github.com/mitas/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.00006 | $0.00438 |
| Opus 5 | $0.00003 | $0.00219 |
| Sonnet 5 | $0.00001 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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
Git Command Usage
Context
- Git commands may invoke a pager that can cause issues in automated environments or tool calls.
- Terminal outputs from git commands can be difficult to capture when pager is active.
- Proper git command formatting improves consistency and predictability.
- The
--no-pagerflag prevents git from using the pager program for output. - This rule ensures git output is directly printed to standard output without interruption.
Critical rules
- Always use
git --no-pagerwhen executing git commands in automated environments. - Use
git --no-pager loginstead ofgit logto avoid pager prompts. - Use
git --no-pager diffinstead ofgit diffto see full output without pagination. - Use
git --no-pager showinstead ofgit showto view commits without pager interference. - Use
git --no-pager blameinstead ofgit blamefor uninterrupted blame information. - When piping git output (e.g.,
git log | grep pattern), always include the--no-pagerflag. - For git commands that produce large outputs, consider adding limits (e.g.,
git --no-pager log -n 10). - The
--no-pagerflag should appear immediately aftergitand before the subcommand. - Terminal commands involving git that would use a pager should always include the
--no-pagerflag. - When creating git aliases, incorporate the
--no-pagerflag for commands that typically use pagers.
Examples
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 · 47 lines · 6 tokens per session scan A 56f959a49767
git is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 6 tokens to every session and 438 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.