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/stramp/lost-mines-phandelver/git-commitsgit clone --depth 1 https://github.com/Stramp/Lost-Mines-PhandelverWhat 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.00791 | $0.00791 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
git-commits 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git and Commit Rules
Commit Format (Conventional Commits)
ALWAYS use Conventional Commits format to facilitate history, automatic changelog and tool integration.
Structure
<type>(<scope>): <short description>
[optional body]
[optional footer]
Commit Types
- feat: New feature/functionality
- fix: Bug fix
- refactor: Refactoring (no behavior change)
- docs: Documentation only
- style: Formatting, spaces, etc (doesn't affect code)
- test: Test addition or fix
- chore: Maintenance tasks (build, dependencies, etc)
- perf: Performance improvement
- ci: CI/CD changes
Scope (Optional but Recommended)
Use the affected module/area:
Characters- Characters and related componentsComponents- Generic componentsData- Data Assets and Data TablesUtils- Utilities and helpersGameplay- Game mechanicsArchitecture- Architectural changesDocs- DocumentationBuild- Build system
Correct Examples
feat(Characters): add CharacterTotalLvl to Data Asset
fix(Components): fix CharacterDataComponent search when Owner is nullptr
refactor(Utils): move FindCharacterDataComponent to ComponentHelpers
docs(Architecture): add Mermaid diagrams to ARCHITECTURE.md
test(Utils): add tests for ComponentHelpers::FindCharacterDataComponent
perf(Characters): optimize final attributes calculation
chore(Build): update project dependencies
ci(GitHub): add automatic build workflow
Incorrect Examples
❌ "fix"
❌ "update"
❌ "changes"
❌ "fixed the bug"
❌ "feat: new thing"
❌ "fix: component bug"
Message Rules
Short Description
- Maximum 50 characters (ideal)
- First letter lowercase (except proper nouns)
- No period
- Imperative verb: "add", "fix", "remove" (not "added", "fixed")
Body (Optional)
- Use to explain what and why (not how)
- Separate from title with blank line
- Maximum 72 characters per line
Footer (Optional)
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 · 139 lines · 791 tokens per session scan A 51d9652ddc6b
git-commits is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 9mo ago), licensed MIT. It adds 791 tokens to every session, about $0.0040 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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.