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/mohamedsaleh14/contextgit/cursorrulesgit clone --depth 1 https://github.com/Mohamedsaleh14/ContextGitWhat 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.00421 | $0.00421 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
cursorrules 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 2d 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.
What it actually says
Cursor Rules for ContextGit
This Project Uses contextgit for Requirements Traceability
This repository is managed with contextgit. The AI assistant MUST follow these workflows:
When Making Changes to Requirements or Documentation
-
BEFORE editing any file in
docs/:- Run
contextgit relevant-for-file <path>to understand related requirements - Run
contextgit extract <ID>to get precise context for specific requirements
- Run
-
AFTER editing any file in
docs/:- Run
contextgit scan docs/ --recursiveto update the index - Run
contextgit status --staleto check for broken links - If stale links found, update affected downstream items
- Run
When Adding New Requirements
- Generate a new ID:
contextgit next-id <type>- Types:
business,system,architecture,code,test,decision
- Types:
- Add YAML frontmatter to the Markdown file with the generated ID
- Run
contextgit scan docs/ --recursiveto register it
When a Requirement Changes
- After editing, run
contextgit scan docs/ --recursive - Check for stale downstream items:
contextgit status --stale --format json - Update downstream items if needed
- Mark as synchronized:
contextgit confirm <ID>
JSON Output for Parsing
Always use --format json when the output needs to be parsed:
contextgit show SR-010 --format json
contextgit status --stale --format json
contextgit extract SR-010 --format json
Detection
This is a contextgit project if .contextgit/config.yaml exists.
Project Info
- Tool: contextgit v1.0.1
- Purpose: Requirements traceability for LLM-assisted development
- Index file:
.contextgit/requirements_index.yaml - Config file:
.contextgit/config.yaml
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.
- 2d ago First seen · 53 lines · 421 tokens per session scan A b75567c78f34
cursorrules is a cursor rule published in the GitHub repository Mohamedsaleh14/ContextGit (10 stars, last pushed 9mo ago), licensed MIT. It adds 421 tokens to every session, about $0.0021 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
verify-ai-readiness
Holistic assessment of the AI knowledge layer on a 5-level maturity scale; flags agent-blocking gaps.
03-skill-testcases
SKILL: Generate Test Scenarios Matrix from API spec (use for /api-isolated-tests).
karpathy-guardrails
Karpathy coding guardrails — think first, simplicity, surgical changes, goal-driven.
ai-dev-os-review
Performs a comprehensive self-review before creating a PR. Combines guideline compliance checking (L3) with design-level review (L2) and philosophical alignment (L1). Unlike @ai-dev-os-check which only checks rules, this also evaluates architecture decisions and code design quality.
cursorrules
ALWAYS start your session by reading AGENTS.md and .memory/wiki/hot.md to get project context before suggesting code or answering questions.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.