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.
git clone --depth 1 https://github.com/danielraffel/SwiftCatalystWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/danielraffel/swiftcatalyst/git-commits)<a href="https://agentmods.dev/rules/danielraffel/swiftcatalyst/git-commits"><img src="https://agentmods.dev/badge/rules/danielraffel/swiftcatalyst/git-commits/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/danielraffel/swiftcatalyst/git-commits"><img src="https://agentmods.dev/badge/rules/danielraffel/swiftcatalyst/git-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.04534 | $0.04534 |
| Opus 5.5 | $0.01814 | $0.01814 |
| Sonnet 5.5 | $0.00907 | $0.00907 |
| Haiku 4.5 | $0.00453 | $0.00453 |
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 1mo 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Conventional Commits for Swift Projects
This rule establishes a framework for automatically generating Git commits in the conventional commits format for Swift projects, including all configuration files and asset types.
Conventional Commits Format
All commits should follow the conventional commits format:
<type>(<scope>): <description>
Where:
- type: Indicates the kind of change being made
- scope: Optional field indicating the section of the codebase affected
- description: Brief description of the change in imperative mood
Swift-Specific Types and Scopes
Commit Types
- feat: A new feature or functionality
- fix: A bug fix
- refactor: Code change that neither fixes a bug nor adds a feature
- docs: Documentation only changes
- style: Changes that do not affect code logic (whitespace, formatting, etc.)
- test: Adding or correcting tests
- perf: Performance improvements
- chore: Changes to build process or auxiliary tools
- ui: UI/UX improvements (specific to Swift UI components)
- config: Changes to configuration files
- build: Changes to Xcode build settings, project files, or build scripts
- i18n: Internationalization and localization changes
- assets: Adding or updating media and other resource files
Scope Conventions for Swift Projects
- app: App-level changes (e.g., AppDelegate, SceneDelegate)
- view: View layer changes (UIView, SwiftUI View components)
- controller: View controller changes
- presenter: Presenter layer (VIPER/MVP)
- interactor: Interactor layer (VIPER)
- entity: Model/entity changes
- router: Navigation/routing logic
- networking: API/networking code
- persistence: CoreData or other persistence mechanisms
- utils: Utility functions
- extensions: Swift extensions
- config: Configuration changes
- project: Xcode project settings
- assets: Images, colors, and other resources
- i18n: Localization files
- deps: Dependencies and packages
- media: Audio, video, and other media files
- fonts: Typography assets
- docs: Documentation files
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.
- 1mo ago First seen · 414 lines · 4,534 tokens per session scan A aeec0c8087fc
git-commits is a cursor rule published in the GitHub repository danielraffel/SwiftCatalyst (14 stars, last pushed 1y ago), licensed MIT. It adds 4,534 tokens to every session, about $0.0181 per session on Opus 5.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-30.
Other cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.