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/business-value-prioritization)<a href="https://agentmods.dev/rules/seanlf/weather-mcp/business-value-prioritization"><img src="https://agentmods.dev/badge/rules/seanlf/weather-mcp/business-value-prioritization/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/business-value-prioritization"><img src="https://agentmods.dev/badge/rules/seanlf/weather-mcp/business-value-prioritization.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.00719 | $0.00719 |
| Opus 5 | $0.00360 | $0.00360 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
business-value-prioritization 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 9d 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
filters:
- type: event pattern: "solution_design"
- type: content pattern: "(?i)(architecture|design|approach|solution)"
actions:
-
type: transform pattern: "^.*$" replacement: |
Solution Evaluation
Business Impact Assessment
Metric Impact Time to market {impact_assessment} User experience {impact_assessment} Maintenance cost {impact_assessment} Scalability needs {impact_assessment} Revenue potential {impact_assessment} Implementation Complexity
Factor Rating Justification Development effort {rating} {justification} Operational complexity {rating} {justification} Team familiarity {rating} {justification} Risk level {rating} {justification} Recommendation
{original_content}
Value Proposition
{business_value_explanation}
-
type: suggest message: | When evaluating solution approaches:
- Clearly assess business impact first
- Evaluate implementation complexity honestly
- Choose approaches familiar to the team when possible
- Prefer proven technologies for critical systems
- Consider maintenance cost as part of the equation
examples:
-
input: | We should use microservices architecture for our new e-commerce platform. output: |
Solution Evaluation
Business Impact Assessment
Metric Impact Time to market NEGATIVE - Longer initial development time User experience NEUTRAL - No direct impact if properly implemented Maintenance cost MIXED - Easier to update components, harder to debug cross-service issues Scalability needs POSITIVE - Can scale individual components based on demand Revenue potential NEUTRAL - No direct revenue impact Implementation Complexity
Factor Rating Justification Development effort HIGH Requires service boundaries, API design, deployment pipelines Operational complexity HIGH Distributed systems introduce monitoring and debugging complexity Team familiarity LOW Team has limited microservice experience Risk level HIGH First microservice implementation has significant learning curve Recommendation
Instead of a full microservices architecture, I recommend a modular monolith approach with:
- Clear domain boundaries within a single application
- Internal API interfaces between modules
- Shared database with schema ownership per module
- Preparation for future service extraction as needs arise
Value Proposition
This approach delivers:
- Faster time to market (40-50% faster development)
- Familiar deployment model for the team
- Groundwork for future microservice migration if needed
- Lower operational complexity during critical launch phase
metadata: priority: high version: 1.0
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.
- 9d ago First seen · 104 lines · 719 tokens per session scan A 9c0c2b244290
business-value-prioritization is a cursor rule published in the GitHub repository SeanLF/weather-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 719 tokens to every session, about $0.0036 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.