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/astrogirlnim/skyfimcp/create-feature-prdgit clone --depth 1 https://github.com/astrogirlnim/SkyFiMCPWrote 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/astrogirlnim/skyfimcp/create-feature-prd)<a href="https://agentmods.dev/rules/astrogirlnim/skyfimcp/create-feature-prd"><img src="https://agentmods.dev/badge/rules/astrogirlnim/skyfimcp/create-feature-prd.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 | $0.00000 | $0.00939 |
| Opus 5 | $0.00000 | $0.00469 |
| Sonnet 5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
create-feature-prd 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 4d 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.
This is a copy
89% identical to create_prd — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule: Generating a Product Requirements Document (PRD)
// Description: Guide for generating a detailed Product Requirements Document (PRD) based on user prompts // Recommended Globs: /tasks//.md, **/prd-.md
Goal
To guide an AI assistant in creating a detailed Product Requirements Document (PRD) in Markdown format, based on an initial user prompt. The PRD should be clear, actionable, and suitable for a junior developer to understand and implement the feature.
Process
- Receive Initial Prompt: The user provides a brief description or request for a new feature or functionality.
- Ask Clarifying Questions: Before writing the PRD, the AI must ask clarifying questions to gather sufficient detail. The goal is to understand the "what" and "why" of the feature, not necessarily the "how" (which the developer will figure out).
- Generate PRD: Based on the initial prompt and the user's answers to the clarifying questions, generate a PRD using the structure outlined below.
- Save PRD: Save the generated document as
prd-[feature-name].mdinside the/tasksdirectory.
Clarifying Questions (Examples)
The AI should adapt its questions based on the prompt, but here are some common areas to explore:
- Problem/Goal: "What problem does this feature solve for the user?" or "What is the main goal we want to achieve with this feature?"
- Target User: "Who is the primary user of this feature?"
- Core Functionality: "Can you describe the key actions a user should be able to perform with this feature?"
- User Stories: "Could you provide a few user stories? (e.g., As a [type of user], I want to [perform an action] so that [benefit].)"
- Acceptance Criteria: "How will we know when this feature is successfully implemented? What are the key success criteria?"
- Scope/Boundaries: "Are there any specific things this feature should not do (non-goals)?"
- Data Requirements: "What kind of data does this feature need to display or manipulate?"
- Design/UI: "Are there any existing design mockups or UI guidelines to follow?" or "Can you describe the desired look and feel?"
- Edge Cases: "Are there any potential edge cases or error conditions we should consider?"
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.
- 4d ago First seen · 64 lines · 939 tokens per session scan A 0c913f077f90
create-feature-prd is a cursor rule published in the GitHub repository astrogirlnim/SkyFiMCP (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 939 tokens. A static security scan graded it A with 0 findings. It is 89% identical to create_prd, differing in 14 lines, and is treated as a copy.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).