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/zxpmail/ReqForgeWrote 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/zxpmail/reqforge/reqforge-product-spec)<a href="https://agentmods.dev/rules/zxpmail/reqforge/reqforge-product-spec"><img src="https://agentmods.dev/badge/rules/zxpmail/reqforge/reqforge-product-spec/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/zxpmail/reqforge/reqforge-product-spec"><img src="https://agentmods.dev/badge/rules/zxpmail/reqforge/reqforge-product-spec.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.00359 |
| Opus 5.5 | $0.00000 | $0.00144 |
| Sonnet 5.5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
reqforge-product-spec 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.
What it actually says
Product Spec Builder
Full skill definition: .cursor/rules/skills/product-spec-builder/SKILL.md
First Principles
- AI-First: For any feature, first consider how it can be done with AI
- Simplicity-First: Complexity is the enemy. Question every feature: "do we really need this?"
- Online-First: WebSearch before recommending competitors, technologies, or solutions
Must Collect (Must Satisfy)
- Product positioning: what is it? What problem does it solve?
- Target users: who will use it? Why?
- Core features: what must it have? What makes the product invalid if removed?
- User flow: complete path from opening to task completion
- AI capability needs: which features need AI? What type?
- Product type: Web / Desktop / CLI / Mobile
Questioning Strategy
- Only 1-2 questions at a time, make them count
- Do not accept vague answers: "roughly", "maybe", "probably"
- Spot logical flaws and point them out directly
- When the user says "you decide", analyze and recommend then ask for confirmation
- Proactively suggest AI enhancement: "should we add a one-click AI X here?"
Output: Product-Spec.md
Use .cursor/rules/skills/product-spec-builder/templates/product-spec-template.md for format.
Final validation loop: scan for redundancy/contradiction/vagueness → auto-fix → re-scan until clean → present remaining issues for user confirmation.
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 · 34 lines · 0 tokens per session scan A eb34108c00ea
reqforge-product-spec is a cursor rule published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 359 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
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
cursor-agent-orchestration
Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.
cursor-mcp-optimization
Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.
minimax-mcp-tools
MCP and web-tool guidance: current-doc retrieval, direct-tool preference, MCP Apps structured content, and version-aware external lookups.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
30-database-postgres
PostgreSQL and persistence rules.