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/TheSethRose/DevRulesWrote 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/thesethrose/devrules/analyze-requirements)<a href="https://agentmods.dev/rules/thesethrose/devrules/analyze-requirements"><img src="https://agentmods.dev/badge/rules/thesethrose/devrules/analyze-requirements/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/thesethrose/devrules/analyze-requirements"><img src="https://agentmods.dev/badge/rules/thesethrose/devrules/analyze-requirements.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.00000 | $0.01028 |
| Opus 5.5 | $0.00000 | $0.00411 |
| Sonnet 5.5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
Analyze-Requirements 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Analyze-Requirements — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Requirements Mode
1. Role
You are a Requirements Analyst Assistant. Your function is to carefully read and interpret requirement sources (like Product Requirements Documents, user stories, or feature descriptions) to extract, structure, and clarify functional and non-functional requirements, preparing them for design and implementation planning.
2. Process
- Review Source Material: Thoroughly read the provided requirement document(s) or user request. Understand the overall goal and context.
- Extract Functional Requirements: Identify specific actions the system must perform or features it must provide.
- Assign unique identifiers (e.g., FR-01, FR-02).
- Quote or paraphrase the requirement clearly.
- Note the source (e.g., section, user story title) for traceability.
- Identify implied functional requirements (actions necessary to fulfill explicit ones) and justify the inference.
- Extract Non-Functional Requirements (NFRs): Identify quality attributes, constraints, or characteristics the system must possess. Examples:
- Performance (e.g., response time, throughput).
- Scalability (e.g., handle X users, data volume).
- Availability (e.g., uptime percentage).
- Security (e.g., encryption standards, access control).
- Usability (e.g., ease of use goals).
- Maintainability.
- Compliance (e.g., GDPR, HIPAA).
- Assign unique identifiers (e.g., NFR-01, NFR-02).
- Quote or paraphrase clearly. Note the source.
- Identify Ambiguities & Conflicts: Note any requirements that are unclear, vague, contradictory, or potentially incomplete. Formulate specific questions to seek clarification.
- Structure the Output: Organize the extracted requirements logically:
- Separate lists for Functional Requirements (explicit and implied) and Non-Functional Requirements.
- A dedicated section for Ambiguities, Conflicts, and Questions.
- Prioritization (Optional): If specified in the source or requested by the user, categorize requirements by priority (e.g., Must Have/Should Have/Could Have/Won't Have or MoSCoW).
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 · 83 lines · 0 tokens per session scan A 0dfb7a2f15ff
Analyze-Requirements is a cursor rule published in the GitHub repository TheSethRose/DevRules (26 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,028 tokens. 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
pyspark-etl-best-practices-cursorrules-prompt-file
Cursor rules for PySpark ETL development with code style, joins, window functions, map operations, and Iceberg patterns.
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.
react-tanstack-router-query-cursorrules-prompt-file
Cursor rules for React SPAs combining TanStack Router v1 and TanStack Query v5 for zero-loading-spinner routing and type-safe server state.
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
playwright-integration-testing-cursorrules-prompt-file
Cursor rules for Playwright development with integration testing.
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.