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/seanlf/weather-mcp/explicit-requirement-extractiongit 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/explicit-requirement-extraction)<a href="https://agentmods.dev/rules/seanlf/weather-mcp/explicit-requirement-extraction"><img src="https://agentmods.dev/badge/rules/seanlf/weather-mcp/explicit-requirement-extraction.svg" alt="Measured on agentmods" 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.00591 | $0.00591 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
explicit-requirement-extraction 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 5d 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: "requirements_analysis"
- type: content pattern: "(?i)(implement|create|build|develop|add)"
actions:
-
type: transform pattern: "^.*$" replacement: |
Requirements Analysis
Explicit Requirements
{explicit_requirements_list}
Implicit Requirements
{inferred_requirements_list}
Clarification Needed
{questions_about_ambiguous_requirements}
Assumptions
{list_of_assumptions_being_made}
Constraints
{technical_business_constraints}
Proposed Solution
{original_content}
-
type: suggest message: | Before implementation, always:
- Explicitly list stated requirements
- Identify unstated but necessary requirements
- List assumptions you're making
- Identify constraints that affect the solution
- Ask clarifying questions for ambiguities
examples:
-
input: | Add a feature to export reports to PDF. output: |
Requirements Analysis
Explicit Requirements
- Export reports to PDF format
Implicit Requirements
- Maintain report formatting and styling in PDF
- Support all existing report types
- Handle various data volumes (small to large reports)
- Provide progress indication for large exports
- Error handling for failed exports
Clarification Needed
- Should PDF exports include interactive elements?
- Are there specific compliance requirements (accessibility, etc.)?
- Should exports be synchronous or asynchronous for large reports?
- Are there specific naming conventions for exported files?
- Should we include company branding/watermarks?
Assumptions
- Users have permissions to view all data they can export
- PDF generation will be server-side
- Existing authentication will be used for export authorization
- Standard paper sizes (A4, Letter) will be supported
Constraints
- Must work within existing UI design patterns
- Server memory limitations for large report generation
- Must maintain application responsiveness during export
Proposed Solution
Based on these requirements and assumptions, I recommend implementing a PDF export feature using a server-side PDF generation library...
metadata: priority: critical 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.
- 5d ago First seen · 94 lines · 591 tokens per session scan A 8535d9671ce0
explicit-requirement-extraction is a cursor rule published in the GitHub repository SeanLF/weather-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 591 tokens to every session, about $0.0030 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-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.