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/SeanLF/weather-mcpWrote 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/seanlf/weather-mcp/frequent-commit-strategy)<a href="https://agentmods.dev/rules/seanlf/weather-mcp/frequent-commit-strategy"><img src="https://agentmods.dev/badge/rules/seanlf/weather-mcp/frequent-commit-strategy/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/seanlf/weather-mcp/frequent-commit-strategy"><img src="https://agentmods.dev/badge/rules/seanlf/weather-mcp/frequent-commit-strategy.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.00891 | $0.00891 |
| Opus 5.5 | $0.00356 | $0.00356 |
| Sonnet 5.5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
frequent-commit-strategy 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 2mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
filters:
- type: event pattern: "implementation_plan"
- type: content pattern: "(?i)(implement|develop|create|build)"
actions:
-
type: transform pattern: "^.*$" replacement: |
Implementation Plan
Conventional Commit Sequence
{original_content}
Commit Structure
-
feat: add initial project structure
- Tests: Basic smoke tests
- Testable state: Can verify structure is correct
- Format:
feat(module): add initial project structure
-
feat: implement core business logic
- Tests: Unit tests for core algorithms
- Testable state: Core functions work in isolation
- Format:
feat(core): implement [feature] business logic
-
feat: integrate component connections
- Tests: Integration tests for component interaction
- Testable state: Components work together
- Format:
feat(integration): connect [componentA] with [componentB]
-
fix: add comprehensive error handling
- Tests: Error condition tests
- Testable state: System handles failures gracefully
- Format:
fix(error-handling): add validation for [scenario]
-
chore: finalize implementation
- Tests: Performance tests, documentation validation
- Testable state: Ready for production
- Format:
chore(release): finalize documentation and optimization
-
-
type: suggest message: | For effective implementation planning:
- Break work into small, testable commits
- Use conventional commit format:
type(scope): description - Choose the right type: feat, fix, docs, style, refactor, perf, test, chore
- Define a testable state for each commit
- Write tests before or alongside code
examples:
-
input: | Implement a new user authentication system. output: |
Implementation Plan
Conventional Commit Sequence
- feat(user): add user model with authentication fields
- feat(auth): implement password hashing and validation
- feat(auth): create authentication service with login/logout
- feat(session): add session management functionality
- feat(middleware): implement authentication middleware
- feat(api): create login/logout endpoints
- fix(auth): add comprehensive error handling
- feat(security): implement rate limiting protection
- docs(auth): add documentation and integration examples
Commit Structure
-
feat(user): add user model with authentication fields
- Tests: Schema validation tests
- Testable state: Can create users with auth fields
- Format:
feat(user): add user model with authentication fields
-
feat(auth): implement password utilities
- Tests: Hash generation and verification tests
- Testable state: Can hash and verify passwords
- Format:
feat(auth): implement password hashing and validation
-
feat(auth): create authentication service
- Tests: Authentication flow tests with mocks
- Testable state: Service correctly authenticates valid credentials
- Format:
feat(auth): create login/logout authentication service
-
feat(session): add session management
- Tests: Session creation, validation, expiration tests
- Testable state: Sessions work properly with timeouts
- Format:
feat(session): add user session handling with timeouts
-
feat(middleware): implement auth middleware
- Tests: Middleware correctly authenticates/rejects requests
- Testable state: Protected routes require authentication
- Format:
feat(middleware): implement route authentication
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.
- 2mo ago First seen · 113 lines · 891 tokens per session scan A 2db2efdce73a
frequent-commit-strategy is a cursor rule published in the GitHub repository SeanLF/weather-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 891 tokens to every session, about $0.0036 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-31.
Other cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
commits
Conventional Commits standards for clear, semantic commit messages.
no-ai-contributors
Never add AI tools as git authors or project contributors.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
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.