production-ready-mindset

production-ready-mindset is a cursor rule for Cursor from SeanLF/weather-mcp. It costs 2,017 tokens per session, scanned A, original, MIT.

A coding rule that asks each change to be assessed as if it will be deployed to real users immediately. The assessment covers areas such as errors, logging, performance, security, testing, and deployment.

In plain words
What is it for?
Use it during code review or after implementation to check operational concerns, deployment and rollback plans, documentation, accessibility, API contracts, and effects on other teams or systems.
Why use it?
It exposes production risks that may be missed when code is judged only by whether it works in a local development environment.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it during code review or after implementation to check operational concerns, deployment and rollback plans, documentation, accessibility, API contracts, and effects on other teams or systems.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/seanlf/weather-mcp/production-ready-mindset
Install

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.

Clone the repo
git clone --depth 1 https://github.com/SeanLF/weather-mcp

Made for: Cursor.

Wrote 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.

agentmods badge for production-ready-mindset

README.md
[![agentmods](https://agentmods.dev/badge/rules/seanlf/weather-mcp/production-ready-mindset.svg)](https://agentmods.dev/rules/seanlf/weather-mcp/production-ready-mindset)
Your own site
<a href="https://agentmods.dev/rules/seanlf/weather-mcp/production-ready-mindset"><img src="https://agentmods.dev/badge/rules/seanlf/weather-mcp/production-ready-mindset.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,017 This file is loaded in full into every session.
When invoked 2,017 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02017 $0.02017
Opus 5 $0.01009 $0.01009
Sonnet 5 $0.00403 $0.00403
Haiku 4.5 $0.00202 $0.00202

Measured 7d ago against content hash aaba548b1f1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

production-ready-mindset 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 7d 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.

.cursor/rules/production-ready-mindset.mdc · 264 lines

How it starts

The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.

filters:

  • type: event pattern: "code_review|implementation_complete"
  • type: content pattern: "(?i)(ready|complete|finished|implemented)"

actions:

  • type: transform pattern: "^.*$" replacement: |

    Production Readiness Assessment

    Implementation

    {original_content}

    Production Checklist

    Category Status Notes
    Error Handling {status} {notes}
    Logging {status} {notes}
    Performance {status} {notes}
    Security {status} {notes}
    Scalability {status} {notes}
    Monitoring & Alerting {status} {notes}
    Documentation {status} {notes}
    Testing {status} {notes}
    Accessibility {status} {notes}
    Feature Flags {status} {notes}
    API Contracts {status} {notes}
    Cross-Team Impact {status} {notes}

    Deployment Considerations

    {deployment_notes}

    Rollback Plan

    {rollback_strategy}

    Cross-functional Impact

    Team/System Impact Coordination Required
    DevOps {impact} {coordination}
    Security {impact} {coordination}
    Data/Analytics {impact} {coordination}
    Frontend/UX {impact} {coordination}
    Customer Support {impact} {coordination}
  • type: validate conditions:

    • pattern: "." validationScript: | // Define production readiness criteria const criteria = [ { name: "Error Handling", check: code => /try|catch|throw|error|exception/i.test(code), message: "Implement proper error handling" }, { name: "Logging", check: code => /log.|console.|logger/i.test(code), message: "Add appropriate logging" }, { name: "Input Validation", check: code => /validate|check|if\s([^)]+)|assert/i.test(code), message: "Validate all inputs" }, { name: "Comments/Documentation", check: code => { const lineCount = code.split('\n').length; const commentCount = (code.match(///|/*|*/g) || []).length; return commentCount >= lineCount * 0.1; }, message: "Add more documentation" }, { name: "Monitoring", check: code => /metrics?|monitor|alert|gauge|counter|histogram/i.test(code), message: "Add monitoring and alerting hooks" }, { name: "Performance Measurement", check: code => /benchmark|performance|timing|duration/i.test(code), message: "Add performance measurement" }, { name: "Feature Flags", check: code => /feature[._-]?flag|toggle|config.get/i.test(code), message: "Consider feature flags for safer deployment" }, { name: "Versioning", check: code => /version|semver|compatibility/i.test(code), message: "Consider API versioning/compatibility" } ]; ];

      // Check each criterion const failedCriteria = criteria .filter(criterion => !criterion.check(code)) .map(criterion => criterion.message);

      if (failedCriteria.length > 0) { return { valid: false, message: Before production deployment: ${failedCriteria.join(', ')} }; }

Read the full file on GitHub · 264 lines

Changes

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.

  1. 7d ago First seen · 264 lines · 2,017 tokens per session scan A aaba548b1f1b

Subscribe to this mod's changes

production-ready-mindset is a cursor rule published in the GitHub repository SeanLF/weather-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 2,017 tokens to every session, about $0.0101 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.